Re: Developer's path to Windows/*NIX multi-platform?

> integration. Ideally, we will have a GTK theme and a QT theme
> that just calls the respective toolkit's theming code, so a
> Wine app will look native both in GNOME and in KDE. I 100% agree
> that native integration is paramount, and this is why we will
> have it.

This sounds very good. Maybe someday.
> Since you've mentioned the toolkits, a small comment on that.
> Of the two only QT is a serious option for cross-platform development.
> It's a good option, but it's not perfect because your application 
> will not be native in GNOME,

Well not to start a KDE vs Gnome debate, but Gnome is way behind KDE 
development... it doesn't even support Superkaramba (last I checked). Gnome 
users typically do not prefer KDE or Qt, and part of that stems from that 
KDE was developed using Qt and it's integration is woven throughout.
> you will not be using the native toolkits
> in Windows, you have to pay a lot of licensing fees, etc.

You only pay licensing if your Qt app is commercial. The free version is 
perfect for opensource (ie GPL software) hence why it's included in almost 
all linux distros and you can D/L the same version for winders.

Maybe
> wxWindows is a better option...

It requires too many code changes (at least in Python) for easy 
cross-compiling. In Qt you simply generate a .pro file for the platform.

Shaun
> -- 
> Dimi.

Developer's path to Windows/*NIX multi-platform?

[Mike Hearn]

On Fri, 02 Apr 2004 14:54:30 +0000, [e-mail] wrote:
> Well not to start a KDE vs Gnome debate, but Gnome is way behind KDE 
> development...

hehe, hint, that's not a good way to "not start a KDE vs GNOME debate"
> it doesn't even support Superkaramba (last I checked).

SuperKaramba is KDE specific by the way it's coded. There is an equivalent
in the form of GDesklets, and works much the same way.
> You only pay licensing if your Qt app is commercial.

... or runs on Windows ...
> The free version is  perfect for opensource (ie GPL software) hence

... unless you want a non-X11 port ...
> It requires too many code changes (at least in Python) for easy 
> cross-compiling. In Qt you simply generate a .pro file for the platform.

Since when does Python require cross compiling?

I think I was just trolled....