> ...
>  
> There *do* exist independent tools for "kicking out" Qt and GTK UI's; 
> they don't interoperate, and since the models are fairly different, it 
> seems not too likely that this will be created. 

All this talk about GTK, QT, windows, gnome, etc... has me wondering,
has no one heard of wxWindows?  This is a package that is currently
being actively improved, is very useable as it is right now and runs
on Unix/Linux, Windows, Mac and possibly other platforms.  Check out
www.wxwindows.org for the details.  Wx uses the underlying windowing
system (I've been using gtk under both KDE and Gnome and msw in windows 9x
and NT).  Yes it's a lowest common denominator (no fancy high level
features, such as gnome print) but that's the trade-off.  Either you
code those high-level features for every possible high-level environment
or you use those from wx, and you'd be surprised at the amount of classes
available.  Some pretty high level abstractions exist.

Some major projects are being developed with wx and they can
be compiled with no changes on all the platforms mentioned.   I would
see this as a much better state of affairs than we have now.  Yes,
if you're running Red Hat, you're ok, since most development seems to
be going in the gnome direction,  if you're running KDE you're behind,
motif/lesstif appears to be falling behind too.  All this would be
solved by a common code base.

The only problems I can see is the expressed (anti)preference against C++
(and wxWindows is written in C++), and the possible need to adapt some
gnucash-specific controls/widgets (the register?) to wxWindows.  I'm
sure the wxWindows people would love to add a neat new class.

On the plus side, all the divergent effort directed at different UI
interfaces could be directed to one common code base.

> Of course, most of the GnuCash UI effort, of late, has gone into GTK, 
> which is not a terrible thing in light of the fact that GLADE exists, 
> and seems to work fairly well. 

There are at least two GUI generators for wx, not very powerful or complete
yet, but it's a start.

How a C++ toolkit would interface with all the scheme, perl, etc...
that's already part of gnucash and how much would have to be
rewritten remain good questions.  At least I wanted to make sure that
the important people here (those doing the work, for which I'm very
grateful, even though I haven't been able to run the qt version yet)
know of this option.


--
Gnucash Developer's List 
To unsubscribe send empty email to: [EMAIL PROTECTED]

Reply via email to