On Wed, Nov 26, 2008 at 1:47 PM, leo_hag <[EMAIL PROTECTED]> wrote: >> Of course code does speak louder than words, and you seem to be doing >> great, but just out of curiosity - what does your tree widget do that >> QTreeWidget doesn't? > > Its not what it can do but how easy it is to do it. There is more > code to interfaceto QTree than there is in the entire custom widget > and the interface code is more complicated and convoluted, I wouldn't > want to maintain or modify that code!. I had difficulty understanding > it, thats why I started looking at the gtkDemo.
The complicated code is needed to interface fully with core, not because of the QTreeWidget - though I'm not sure at this point to what extent it could be simplified. See qleolite for how trivial it could be: http://bazaar.launchpad.net/~leo-editor-team/leo-editor/qleolite/files > I stress that the widget IS wired in and working in the qt plugin > already (in the hag branch). Where as the current tree is not > working. Whether it complies to the full leo interface is up to edward to decide, I guess - but if you solved problems that QTreeWidget had, certainly the same solutions could be applied to QTreeWidget? The only shortcoming I see QTreeWidget having, api-wise, is the lack of direct support for multiple icons... -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
