Updates to Leo-to-HTML and Leo-to-RTF Plugins
da...@cvisual.com
I have updates to the Leo-to-HTML and Leo-to-RTF Plugins.
Leo-to-HTML now performs HTML entity encoding, includes a DocType, and
conforms to the key xHTML standards.
Leo-to-RTF trims all headlines and body text and doesn't include empty
body text items in the export.
Both also have improved reporting to the Leo log window.
Do you want me to post the updated files to the Wiki or what is the
current procedure?
Also, I have a better version of Paste As Headlines in the pipeline,
so I should be able to send that over next week.
I still use Leo every day and consider it one of the most important
applications in my toolbox. Thanks for all the hard work!
Dan
Edward K. Ream
> Do you want me to post the updated files to the Wiki?
The easiest way would be to use bzr. Using the Wiki creates more work
for me, but it's ok if there is no alternative.
Either way, please post a notice here. Thanks.
Edward
da...@cvisual.com
OK. I'll try to download and install bzr this week. I've read about
it, but have never used it (I use SVN).
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.
One other question: Is the Plug-in Manager ever coming back? I really
think it is essential to convince end users to adopt Leo.
Dan
On Oct 22, 6:00 am, "Edward K. Ream" <edream...@gmail.com> wrote:
> On Wed, Oct 22, 2008 at 2:27 AM, d...@cvisual.com
Edward K. Ream
> 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