On 09/15/2009 08:21 AM, Abdelrazak Younes wrote:
Alex Fernandez wrote:
So everything that is needed is a bridge that can be used to call the
local library. Attached is this file elyxerbridge.py, which should be
added to directory $s/scripts/; it simply gathers command line
parameters and calls elyxerconv with it. The detection method needs a
little change, which is commented below.
I won't enter the debate between you and Richard but please calm down.
Technically speaking, I will just say that either this bridge is
bundled with the Windows installer
I don't myself see why this isn't a perfectly adequate solution, since
(so far as I can tell) this is entirely a Windows problem. Maybe it's
not adequate, but if so I'd like to know why not.
or the full elyxer is bundled with LyX together with the other python
scripts. It makes absolutely no sense to me to put a bridge in LyX for
a tool that is only used together with LyX. And if elyxer is
integrated in LyX, you will of course have to promise to maintain it
Alex.
We've had that discussion before, and can have it again. But I will say
again the one thing I've said before: Alex's promising to maintain it
isn't really good enough. If it's part of LyX, then WE have to maintain
it, since Alex may or may not be around to do so, no matter what he
promises. Moreover, I'd at least want a commitment that it be kept up to
date not just in branch but also in trunk, so that we aren't waiting
around for an elyxer that works with 2.0/1.7, or else wondering whether
to include it. And that to me draws attention to a real technical
problem with how elyxer works: It is tied to our file format in a way
that seems to me to make it hard to maintain.
I say all this despite the fact that elyxer is, in other respects, an
impressive achievement.
Richard
