On Oct 16, 3:36 pm, "Edward K. Ream" <[EMAIL PROTECTED]> wrote: > I have been thinking that plugins that require a particular gui should > reside in leo\plugins\tkinter or leo\plugins\qt, etc and that gui > plugins should be treated differently because they should be loaded > first.
I expect that some GUI-related plugins would support both tkinter and Qt, as the Qt GUI will gain popularity. Because of this splitting plugins/ into plugins/tkinter and plugins/qt might be a premature decision at this moment. What about the plugins that would support both tkinter and Qt go then? One conclusion is still certain at this point. Leo would need a straight API function that would return the GUI that is currently used. So cross-GUI plugins (and even simple user scripts would be able to call this and make a decision about which part of their body to activate). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
