Jean-Marc Lasgouttes wrote:
"Edwin" == Leuven, E <[EMAIL PROTECTED]> writes:

What bothers me is rather the following: for some weeks we had people
clamoring "what? we are in 2006 and we still have xforms? Do you know
all the things we could be doing if we did not have it? how can LyX
continue to live in this conditions?" and so on.

Well, for one it helped me to have to care (only) about 3 frontends when I did some GUI API cleanup. I could undertand qt3 and a bit of gtk but xforms was really difficult for me. So yes, it was worth it. I grant you that I did not bring new feature on the table but the cleanup was worth it IMHO.

Of course the fact that it is not portable is the one important reason why xforms was rightly removed.


Then xforms got removed.

May it rest in peace ;-)


Then we had maybe one rejoicing message, but no patch leveraging this
huge freedom we've been giving to ourselves by removing this
abomination (Michael removed the xforms-only stuff, but that is the
least we could do).

And we did not have to bother with it for the unicode transition (and my cleanup work). You must understand that more platforms means more compilation, the more test you have to do.


And then the _next_ day (or even the same days), it was "what? we are
in 2006 and we still have qt3? Etc etc".

It is way too much posturing in my taste. I can tell you that in 10
years with LyX (yes I am this old) I have seen a pretty long list of
things we _have_ to do (switch to java?) to have the slightest chance
to go forward. I think there were at least 5 single _most_ important
problems with LyX in the last month alone.

Another typical trait of French people is exaggeration ;-)


This notion that change is always progress is pure bullshit. Having
the lyx core do something useful is more IMO important (but less sexy
admittedly) than this GUI obsession.

I think you got it wrong JMarc. The goal is not be exited about the wonderful world of Qt4 but to lessen the maintainance work. When a new feature appears in the core, it is less work to reflect this new feature in two frontends rather than 4.

Besides, I think cleanups of the core is more important than new core feature right now.

Abdel.

Reply via email to