Finally, qt is changed from optional to required. It is kind of weird
to require qt libraries for a, say, gtk frontend. If this is not a
concern, then, my question is: where should we draw the line?

As someone mentioned in a previous note, we have been/are reinventing
every wheels. I was not exactly exaggerating when I said that half of
the lyx code can be removed if we focus on qt/win only. If qt/unicode
can be in support, why not qt/process, qt/clipboard, qt/filesystem, or
qt/everything?

I guess, before forking 1.6.0, we need to do a survey regarding the
future of lyx. The major features we/users want, and how to achieve
them. I would not be surprised if we conclude that lyx should become a
qt-application so that we can focus on more important things.

Bo

Reply via email to