Lars Gullik Bjønnes wrote:
Michael Gerz <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes schrieb:
| > I don't want one man that is unwilling to work on qt3 decide what
| > happens with it. Get consensus, then let's ditch it. Not before.
| >
| OK, then let's revert the question: Who wants to keep qt3?
Or. Who is unconfortable wrt removing qt3 from the repository?
Removing it is no problem for me, compiling qt4 works for me,
and I have the impression that the scrolling performance
problems (compared to qt3) were fixed.
Now, I don't do much work where this matter. But I am also
a user. If dropping qt3 can speed up the more active developers
and make their life easier, then I am all for it. A working lyx
with unicode will happen faster. Fixing stuff will happen faster.
Stuff that is "supported internally but have no GUI at all"
won't happen that much if there is only one "main frontend"
where changes are made.
GUI independence is nice, but don't mean we have to drag lots
of GUIs around. It means that the switch is easier when the
next great GUI (qt5 or something else entirely) comes around.
Now, supporting two frontends "by force" might make sense
if we had a big userbase unable to use qt4. Currently
this is not so. "Old linux distros" aren't really an excuse,
the effort is then better spent on an installer that can pull in
qt4, similiar to how the windows installer can install latex.
And if lyx 1.5 takes some time then everybody will have
a qt4 option anyway.
Helge Hafting
