Unfortunately my freetime has disappeared for a prolonged period, however, I thought I would dump the stuff I *would* do if I had some (I know this is not immensely helpful):
* Plugin system cleanup (easy) - Remove the weird way leo loads plugins (forcing a reload), change it to use __import__ bulitin. - This would "normalize" the way plugins work, increasing performance and making Leo more predictable. - Also allow specfying enabled-plugins in multiple places, so that users plugin set doesn't override one in leoSettings.leo * SQLite .leo file format (medium) - Able to attach huge binary data to .leo file without increasing load time (images, etc). This would be done by lazy loading of bodies - for certain node types body is not fetched unless leo requests it. The data would still be contained in self-contained form in the leo file. - Able to open multiple "views" on the same leo file (in separate leo processes), and actually be able to save without clobbering the edits done in other leo instances (tentative) If the previous is too "hard core", an alternative: * zip .leo file format (easy/mediem) - I mean zip support in proper sense - storing multiple files in the zip file, instead of merely compressing .leo file - Ability to store large binary files in zip and reference them from .leo. Attach files from file system by drag-and-drop, and be able to pop them open from the outline. Note that both the alternative file formats would essentially be binary files, and be handled as such in version control. This may or may not be a problem - I'm thinking of both as "fat" word documents, instead of something you'd use for programming. -- Ville M. Vainio http://tinyurl.com/vainio -- 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.
