> Patrik Stridvall wrote:
> >
> > In what way does
> > in itself hurt Linux if Win32 becomes the dominant GUI API instead
> > of Qt or GTK+ or whatever?
>
> For starters, Microsoft has total control over the Win32 API, and can
> make it as Windows-friendly and Linux-hostile as they want
> to.
What says that people wanting to support both Linux and Window will
use these API:s?
> If Win32
> doesn't support an important feature (e.g. interfacing with
> the GNOME or
> KDE panel), we have absolutely no leverage to get the API changed to
> improve support for that feature.
So add it to WineLib as an extension or bypass WineLib and talk directly
to X Windows. Sure you will have to add #ifdef:s or something to the code,
but then Windows doesn't have a GNOME or KDE panel either so that shouldn't
suprise you very much. In fact GNOME doesn't have KDE panel and nor
does KDE has a GNOME panel so you have to handle that somehow regardless.
You are aware of the fact that extentions to WineLib that makes sense
on Windows as well could be implemented using Win32 API:s and installed
on Windows as a DLL (WINE.DLL or something). Of course users of these
features will have to distribute this DLL with their application,
but then many applications already use 3rd party DLL:s so this is
not anything strange for companies writing applications for Windows.
Beside the same thing could be said about Troll Tech for Qt or the core
team (or whatever they have) for GTK+. They will not add special support
for everything under the sun either.
In short, nothing prevents you from writing your own extensions.
> OTOH, GTK+ and Qt are
> better aligned
> with the X11 API, and it's in their best interests to encourage native
> support of such features.
Agreed, but we are talking abut the future of Linux, _not_ the
future of X Windows. If someting better comes along like Berlin
Linux will use that instead. There is nothing that says that
the future Windows System will not be well aligned for both
Windows and X Windows. In fact I am pretty sure it will.
> IOW, the Win32 feature set does not map one-to-one to the X11 feature
> set, so the Linux side will inevitably be short-changed.
So implement all X11 widgets as a Windows DLL as Windows custom controls
and use them in your Win32 application. Use them on both Windows
and Linux, use #ifdef:s to select what to use. It is your choice.
I think it is a big mistake to see it as a battle between Win32
and X Window, lets face it both suck big time and something
new like Berlin would be very much desirable IMHO.
The only thing that is important to the user is that the desktop
enviroment is consistent and easy to learn, but you really think
the user will notice an inefficient drawing of an Win32 control
on X Windows. How much time does it take to draw a dialog on
a modern computer? 1 ms? More, less?
