The following appears in the node ' To do-->Strategy for merging' in leoPlugins.leo in the qt branch:
QQQ What is really different: - The plugin files themselves. - The stylesheet node in leoSettings.leo. - The top-level tree.select code. - Two or three lines of code in the core. Strategy: 1. Move the above items into the core. 2. Run all unit tests w/o plugins enabled. QQQ What is unsaid is that I want to demonstrate, in the clearest way possible, that the qt plugin doesn't need Leo's core to change, except for tiny changes. The proposed changes to the baseTextWidget class might complicate this plan, as would changes to the unit tests. Still, I am seriously considering "merging" by copying and pasting just a few nodes. Unit tests make this practical. Whether it is actually wise remains to be seen. It's an amusing goal... 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 -~----------~----~----~----~------~----~------~--~---
