Re: eLyXer: LyX to HTML converter

[Alex Fernandez]

>> Nope, and it is a very good idea. However I would like to build a
>> standalone tool that does not require other libraries to work, i.e. to
>> minimize dependencies -- not because users will not have lyx2lyx
>> installed but because of runtime problems.
>
> I am not sure I follow you, why would you have runtime problems if lyx2lyx
> is installed? In case that was not clear, lyx2lyx is pure python, just as
> your eLyXer. Or are you talking about the python modules that lyx2lyx
> requires?

Sorry for not being specific, I meant runtime dependencies. My python
knowledge is not very deep and I'm not so sure that I would know how
to locate the libraries (not on my system but in general). Also I
don't know enough about the libraries so it would probably take me
more to learn those than to roll my own quick&dirty solution.

> I am afraid that locking you tool to a specific lyx format is not a good
> long term option.

That is right, in the long term it probably pays to use the LyX
libraries, at least to ease maintenance. On the other hand a
standalone tool is always easier to build and deploy, and probably
consumes less resources, so one has to balance the advantages of both
options. For me it makes sense to parse the commands independently,
and if (as Richard Heck says below) LyX ever moves to an XML format
then rethink the whole thing. But I'm the newbie here...

Alex.