GSoC 2019 : Week 0-Community Bonding.

The corresponding blog post represents what all works I have done during the community bonding period of GSoC 2019. For the last week, I have been trying to lay some clear foundations on how the code is structured and also how the files are managed in the software regarding the palette. I also made an effort to make sample TreeView and TreeWidget which may provide a future reference for constructing the Palette.

Works Planned to do:

1. Understand how model-view programming is implemented.
2. Make a sample TreeWidget.
3. Understand the structure of the code in the palette.

Work Done:

Made a sample TreeWidget consisting of the first 2 palette items [1]. The QTreeWidget class provides a tree view that uses a predefined tree model. This helped me to get familiar with the building of the hierarchical structure.

Thereby to make sure the data of the palette available in variable other regions of the software and to represent the model in different views a Model/View architectural approach is taken. A QTreeView implements a hierarchical structure of items from a model and takes full advantage of the flexible approach provided by Qt's model/view architecture. An additional benefit of the model/view architecture is that if we decide to change how the underlying data set is stored, we just need to change the model; the views will continue to behave correctly.
Right now I am currently working with the TreeView to understand more about Model/View programming. Meanwhile, I learned more from the existing QTreeWidget in the New Wizard Dialogue Box ( Template Browser ) and also went through the files corresponding to the program that helps to populate each palette with the palette item.

References:

Link [1] : QTreeWidget