Hi Richard,

On Sat, May 2, 2009 at 1:19 AM, rgheck <rgh...@bobjweil.com> wrote:
>> Have you considered that Alex might help you with your HTML project since
>> he knows HTML as well as you and might have more LyX-HTML experience due to
>> his eLyXer.
>>
> Yes. I suggested we should work together. He refused.

Said in this way it may look a bit harsh. The reality is that, even
though it would be great, I don't think the project of producing
native HTML output is viable. Not in a "haha you will never catch me"
way, but rather in a "it will get _very_ boring before it is useful"
fashion. My opinion is that, even to get to the point where eLyXer
stands _now_, a lot of manpower will have to be devoted. To get much
farther, to the point where it can really leap ahead eLyXer, will be
_very_ complex. You could devote a whole 3.0 dev cycle to it and still
be short of the richness of e.g. the TeX output.

I am not sure that this new project will even be started: Richard
proposed to help me with it, not the other way around; and only after
his exams were finished. Not a very solid promise, if I have to judge
by my own University years :P So if I have to choose between being a
principal developer of said project and continuing to improve eLyXer,
where there are a lot of interested users and I have lots of fun, the
answer is clear. And of course I will not commit to both things since
it would be suicide.

That said, there are a few ways in which we could colaborate if the
project ever catches wind. First as a checkpoint: eLyXer already
produces acceptable HTML for a wide variety of LyX documents, so this
new native HTML output can try to mimic it first. Second is via the
CSS: the new HTML code can use the eLyXer CSS, which already encodes
(and encapsulates) a lot of presentation logic for LyX layouts. And
third of course the usual colaboration way of having people to ask
things. All of them can of course work both ways.

Thanks,

Alex.

Reply via email to