Jean-Marc,
On 12-Feb-99 Jean-Marc Lasgouttes wrote:
>>>>>> "Roland" == Roland Krause <[EMAIL PROTECTED]> writes:
>
> Roland> All Wxwin ports are native, so speed is not an issue, afaict.
> Roland> Code bloat is something you will get anyway, either it's your
> Roland> own code that is becoming bloatet, which means the maintenance
> Roland> problem is on you, or it is the toolkit code thats bloatet,
> Roland> then the problem is on the toolkit developers.
>
> Another point is that what KDE and/or Gnome need is not a Qt/Gtk
> application, but a full blown K/G application. And they want to be
> able to use whichever nifty widget their library provides. I'm not
> sure WxWindows provides that.
>
That is a quite dangerous path to walk on.
I can not use any KDE application on my SGI because, although I have KDE
compiled and installed, it is extremely slow and hogs an extreme amount of
memory. I didnt even bother trying Gnome, because of the immaturity of the
code.
O.t.h. I looked closer at the KDE enhancements to Qt at the KDE developers
site and I can not see such a huge difference. E.g. Instead of QtApp class
KDE uses a KApp class, allowing for a lot of nifty things, like easy storage
and parsing of the configuration filed and such.... KDE has a lot of
improvements
over plain vanilla Qt but things are changing fast and development of Qt goes
relatively fast too.
Personally I do not believe in a multi toolkit approach anymore. This has
nothing to do with LyX, so consider it somewhat off-topic, but from my
experience :
Toolkits are not really exchangable, because, as the state of LyX/KLyX
clearly shows, it is the programmers that have to relearn a different toolkit
and that is the difficulty. it cant be done on the fly no matter how
sofisticated
your interface is. Redoing a thing that already works is something nobody
really volunteers to do. And the question is always, why do it in the first
place ?
Shure XForms is bad, ugly, buggy , non-free, etc. but the reason it was chosen
in
the first place was, that it gets the job done.
There is from my past experience, coming from Aegis on Apollo Domain computers,
only one reason that has ever forced me to switch toolkits, which was that the
old toolkit did not exist on the new platform.
Sometimes I think if just everybody would have followed Matthias and switched
to
Qt/KLyX in the first place, the whole LyX project could be a lot further.
Please do not misunderstand this as critique at you guys, I truly admire your
work, it is just that I think when I read the toolkit discussions, why not
picking one good toolkit, switching to it with full force and be done with it.
Anyway, didnt wanna bother you but its Friday...
Roland
> However, the core LyX developpers will probably not do all these
> ports. This means that the choice of toolkit will also depend from the
> people willing to do it.
>
> And last, there a re plan for a curses frontend. I doubt that
> wxwindows provides this one.
>
> JMarc
Roland Krause
Visiting Research Associate - Center for Computational Mechanics
Washington University, Saint Louis
Roland Krause <[EMAIL PROTECTED]>
