On Wed, 28 Nov 2001, Rainer Dorsch wrote:

> Hello,

Hello.

[...]
> therefore I am looking forward to see a GTK- or QT-version of lyx. I am very
> happy about the GUI-I, but at the same time, it is progressing very slowly. To
> my understanding
>
> - currently a large part is ported to GUI-I
> - some parts are still xforms hardcoded, prohibiting to do something else than
> xforms
> - hard coding another GUI is not that difficult (at least I think to remember
> that kLyX was build within a few days)

...by people who live and breathe Qt/KDE.  See further below.

> Therefore I am wondering, why not the few hard coded xforms parts are ported
> to QT or GTK (I don't mind which one, both are probably ways better than
> xforms) and the GUI-I QT or GTK is used for the rest.

As GUII progresses people want to switch from hard-coded xforms to
hard-coded Qt (GTK would be a waste of time at the moment because its
dialogs don't even compile because that frontend has been unmaintained
for some months).  This gets more tempting as time goes by, however,
we have working xforms code so switching to GUII xforms is actually
fairly simple since we reuse a large part of the code -- just move it
around and separate it out with some signals.

What will anyone gain by switching to a different toolkit for the
hard-coded sections of code?

I'll tell you:  bugs, and a broken lyx until the new hard-coding
works.  Then you still have to do the GUII work.  After Matthias
Ettrich complained about the progress of the GUII work I suggested he
get a group together to rapidly port LyX to Qt in much the same
fashion as you are suggesting.  Given that Matthias is both the
founder of the LyX project and KDE and works for Trolltech he
shouldn't have had any problem getting a competent team together to do
such a port.  His response?  Silence for the last twelve months.
However, Kalle Dalheimer has been involved from time to time porting
some of the Qt2 dialogs.  Volunteers work on what they can when they
can -- progress has actually been exceptionally fast in the last 12
months IMO.

GUII porters have, however, reduced their work on the frontend to try
to help fix bugs in the core and in particular in the insets
hierarchy.  In addition the goal for 1.2.0 was to get all the dialogs
GUII for the xforms port -- as you will see from the GUII status page
this has been achieved.

I personally want to get 1.2.0 out ASAP but we have several major bugs
to fix and they take priority over GUII and other new features IMHO.


If you can provide us with bug reports (preferably including
backtraces of crashes) we will do our best to fix them.  Please
remember to include full details in such reports including the version
numbers of LyX, C++ library, C library, compiler, xforms, Xpm and OS.

Allan. (ARRae)

Reply via email to