>From another thread: QQQ The success with Qt has encouraged me to rethink the wx plugin. A few hours work should show whether a stateless approach will fix the pain with the wx tree. I'm not going to spend a huge amount of time on this detour, but I can't let this opportunity go by... QQQ
This morning I realized that the leoQtTree class could be modified to become a base class for native tree widgets. I've begun the work of separating widget-dependent methods from widget- independent methods. It turns out that most of the drawing code is widget-independent, and the widget-dependent code is short and simple. It may even turn out that most of the event handler code can be made widget-independent. If so, it may take only a few hours of work to test the wx gui. This work will be done in the trunk. I'll add a baseNativeTreeWidget class to leoFrame.py. This will have no effect on Leo's core. I'll then create a wxWidgets plugin that will be a subclass of baseNativeTreeWidget. Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
