Alex Fernandez wrote: > But there is an additional consequence not usually considered by LyX > developers: since "eLyXer state" is independent of "LyX state", and > much simpler, eLyXer enables new uses for "LyX format" (i.e. .lyx > files) for people that won't or can't install LyX. Examples: remote > servers, low-powered machines, odd unsupported platforms for LyX, not > for Python: > http://www.python.org/download/other/ > And also command line pipes, background operations... so being kept as > a standalone is also an important goal for eLyXer, and one that > potentially extends the uses of LyX at the same time.
at least by me this was considered and in fact was starting point of some doubting. project, which you may not be aware of (http://www.netmeister.org/apps/lyx2html/), was triggering in me the feeling that history is repeating again. one can see that this package is still lurking in distro repos as a zombie not touched for last 10 years. thats one of reasons i was from the begining so troublesome when it comes to the question of inclusion. now this is nothing against you personally - its true for all devs here - when one is looks on the lyx project from a wider time range developers come and leave and you will have hard time to find most of devs which were 10 years before on this list. but the popularity reached a certain threshold so its quite probable other new people will contine and will have to handle the code we leave... from this point of view its no more question of "what is easier to do" but rather "is the code written in easy maintainable way?" thats why even if lyx internal html export wouldn't have all whistle and bells compared to elyxer once lyx 1.7 comes out i would still consider it more promising start from the long term view. we would have another discussion if there was no work on internal support but once you provocated Richard to start it, we are on a different grounds. where we have utterly failed was to pick up your enthusiasm and convince you to cooperate on this project, even worse to make you feel to be attacked by us. this way only Richard is envolved on internal html export and aparently without much sparse time to continue on the half-work-done... pavel
