On 09/19/2009 05:58 PM, Alex Fernandez wrote:
Since our last discussion I've had some time to work on LyX - eLyXer
integration. In particular I've tried the excellent suggestions from
Guenther Milde, and surprise, it works. This time around it looks for
eLyXer installed as a Python module (called "elyxer", not
"elyxerconv"); if not found it searches for the usual elyxer.py,
elyxer executables. Hopefully this solves all reasonable issues and
concerns of LyX developers and integrators. It does not interfere with
Jürgen's new mechanism for preview and conversion (which frankly I
don't like much), it does not change how LyX recognizes HTML
converters (which I don't like much either), and it should apply
cleanly against trunk (on the lib directory). It does not work with
the current version of eLyXer (0.30), but it will against the next
(0.31), so it can wait until 0.31 is published; but I wanted to get
early feedback.
This is a great deal better than the previous effort. But surely it
would not take much effort to write a short "checkModule()" routine that
would work essentially like checkProg() does, and then to use that. This
would keep the code here cleaner---in particular, it would remove the
try-except block from the flow of the code---and therefore make it
easier for those of us who maintain it to maintain it. (I guess this is
a comment on your second question.)
Richard
PS The only thing I can see that is wrong with Jurgen's new
"mechanism"---and no matter what, it is a HUGE improvement over the
current situation---is that we need a way to allow the user to choose
more than one of the several options. If that were in place, I can't
imagine what else one would want. Help with this is, of course,
appreciated. No one really has time for endless complaints that come
with no concrete suggestions.
