It was clever to use the leoBridge module as the foundation of the qt demo. This gives access to g and c in a nullGui environment. Adding gui stuff 'by hand' completes the prototype.
Much more work is required to create a proper qt gui, namely, creating qt-specific subclass of all the gui bases. My plans: 1. Move the gtk code out of leoPy.leo into an experimental (abandoned) gtk_gui plugin. I have no plans at present to test the newly repacked gtk code in any way. 2. Create a qt_gui plugin. It will take a few days to repackage what Ville has already done, but that can't be helped--it is the only way to fully connect Leo's core with the gui code. We can then continue to improve the plugin. 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 -~----------~----~----~----~------~----~------~--~---
