Le dimanche 6 août 2006 17:07, Michaël Larouche a écrit : > Le August 6, 2006 07:54, Olivier Goffart a écrit : > > I'm not saying that we should not use the Model/View stuff. > > But I still doesn't see the need of it. > > > > No need to rush on that technology because it's new fashion in Qt. > > > > We could simply use a QTreeWidget with LVI like this is done. > > It seems it covers all our need, and is much simpler. > > Yes I agree that Interview is a big beast and the learning curve is high. > I still didn't catch the whole concept of this new framework. > > One thing for sure, it will save us maintainability in lorg term and will > give us more power and flexibility.
For sure ? It seems more complex. And more complex = harder to maintain. From the Qt documentation: (QTreeWidget) |The QTreeWidget class provides a tree view that uses a predefined tree model. |The QTreeWidget class is a convenience class that provides a standard tree |widget with a classic item-based interface similar to that used by the |QListView class in Qt 3. [...] |Developers who do not need the flexibility of the Model/View framework can |use this class to create simple hierarchical lists very easily. A more |flexible approach involves combining a QTreeView with a standard item model. |This allows the storage of data to be separated from its representation. What is this flexibility that we need ? Note that our storage data is already separated from it's representation in the Kopete::ContactList
pgpr1Frac7GGD.pgp
Description: PGP signature
_______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
