> -----Original Message-----
> From: Joshua Haberman [mailto:[EMAIL PROTECTED]]
> Paul Davis <[EMAIL PROTECTED]> wrote:
> > >Has anybody actually tried to get gtk+ and qt working in the same
> > >application?
> >
> > its been done.
> >
> > it was ugly as sin.
>
> This is a strong counterexample to the oft-repeated maxim
> that "choice is
> the strength of OSS."
??? this is a property/feature of X.
and btw I think you would run into same kind of problems in ms windows
(remember, lot of toolkits available for X are available for ms windows,
there are also different ms windows specific toolkits - can you combine them
easily in one program?)
> But I guess the fact that 10 random linux audio applications
> are written to 10
> different APIs that can't interoperate is another.
what do you mean? _one_ program will probably use different APIs,
depending what it needs to interface to (e.g. there would be linux (or
posix) API (system calls), standard library API (most of the programming
languages have some standard library), one (or more) sound API, some UI
API...
just because applications use same API does not mean that applications
will be able to interoperate. they have to be designed to interoperate
(first part of that would be to define what it actually means in context of
given applications)
> In my opinion, this is why the deskop projects (KDE and Gnome) are so
> important. They give consistency of behavior and
> interoperability between
> applications.
IMO in a wrong way - instead of providing protocols to communicate they
lock you in specific implementation. and they are quite messy. it looks like
it's getting better, somewhat...
...
> Think about the difference between writing a game for Win32
> vs. Linux. With
> Win32 you keep your Direct* reference handy and away you go;
> it's an entire
> platform. With Linux you have to make umpteen decisions
you also have openGL. probably other ones (macromedia for kiddie games?)
> about what system to
> use for graphics, sound, networking, timers, etc. People often make
> less-than-optimal decisions due simply to lack of knowledge. What the
it's in process of development. confusion is expected. in graphics area it
is fairly stabilized, as far as networking etc. goes there shouldn't be any
confusion. sound is a big mess (remember oss is considered not good, alsa
just recently stabilized API, it's still not 1.0)
the problem is not that there are many choices, the problem is that there
are not good enough choices in some areas (but that's changing rapidly)
erik
