> I want to demonstrate, in the clearest way possible, > that the qt plugin doesn't need Leo's core to change...
It was a laudable goal, but I'm going to abandon it, at least partially. I plan to move all gui-specific code to tkinter and swing plugins as part of the present branch. The reason for this odd-looking choice is that the details of text widget wrappers are now fresh in my mind, and I'd like to clean up the arguments passed to the ctors of those wrappers. The present ctor args are a real mess. But this means that the core *is* going to change significantly, at least as regards the text wrapper classes. And while I am at it, I'll probably clean up the wrapper-related code in a few other ways. In short, merging the qt branch into Leo's core is going to take a bit more work, but the benefits will be substantially simpler code. 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 -~----------~----~----~----~------~----~------~--~---
