On Sun, Oct 26, 2008 at 7:50 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Also, I finally had time to get back to the MS Project & Open > Workbench exporter and that is at nearly beta level. I integrated it > to use the Cleo time estimates if available, so that is pretty cool. I > just downloaded OpenProj (an open source mirror of MS Project) that > works pretty well. I think Leo + OpenProj are a winning team. Cool. OpenProj looks very interesting. > One other question: Is the Plug-in Manager ever coming back? Yes, if you can believe the to-do list :-) The plugins manager plugin used to update an external file: pluginsManager.txt. Now, it would have to update an @enabled-plugins node "somewhere", either in an open .leo file, or myLeoSettings.leo or leoSettings.leo. That's the essential project, but there are other tasks: - The code is in need of a rewrite. - There are several items on the to-do list relating to leoPlugins.leo, and those items should be done first, or concurrently. - The gui code uses Pmw extensively. It's not clear that Pmw will be ported to Python 3k and that question is becoming mooted by the impending migration to Qt. > I really think it is essential to convince end users to adopt Leo. It wouldn't hurt, but Leo will never be dead easy to learn :-) 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 -~----------~----~----~----~------~----~------~--~---
