Re: [linux-audio-dev] Anyone planned a GTK2-based Multitracker?

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] Anyone planned a GTK2-based Multitracker?
From: Jan Depner (eviltwin69_AT_cableone.net)
Date: Sat Apr 10 2004 - 01:22:47 EEST


This is from someone who uses both (including commercial Qt licenses at
work). I prefer Qt because it is more mature and documented better but
there's nothing wrong with GTK++. It shouldn't be a religious issue.
Try 'em both and pick the one you like the best and that fits your
background/style/objective the best.

Jan

On Fri, 2004-04-09 at 15:52, Samuel Abels wrote:
> On Fri, 2004-04-09 at 22:18, Arnold Krille wrote:
> > > As nice as Ardour may be, I personaly still prefer the interfaces of
> > > modern UI toolkits, in combination with a nice Object Oriented language
> > > (aka C++ :) ).
> >
> > If you want to write C++, why do you want GTK??? Use a C++-toolkit like Qt.
>
> Despite the fact that this is often discussed as a matter of religion, I
> prefer gtkmm because it fits better into the GNOME environment.
>
> Also, this is from the gtkmm-documentation:
>
> http://www.murrayc.com/murray/talks/2002/GUADEC3/notes/html/index.html#id2759245
>
> "QT originates from a time when C++ was not standardised or well
> supported by compilers. Its design today is still based upon the choices
> available at that time, so it does not play well with more up-to-date
> code. Development of QT is still effectively closed - There is still no
> public development mailing list, and TrollTech have the normal corporate
> conservatism. As an open-source project, its design would have been
> improved through public debate, and it would have been possible to
> jettison the baggage.
>
> QT duplicates a lot of stuff that is now in the standard library, such
> as containers and type information. Most significantly, they modified
> the C++ language to provide signals, so that it's difficult to use QT
> classes with non-QT classes. gtkmm was able to use standard C++ to
> provide signals without changing the C++ language. And we use of
> Standard C++ Library containers such as std::string, std::list,
> std::vector and their iterators. We even provide STL-style interfaces to
> other things such as container children, allowing you to use iterators
> and push_back(), etc with these."
>
> So, in essence, gtkmm does it in a more C++ way. :-) (But please let us
> not make this a flame; may everyone be free to choose whatever toolkit
> he likes best. ;) )
>
> -Samuel
> --
> ------------------------------------------------------
> | Samuel Abels | http://www.debain.org |
> | spam ad debain dod org | knipknap ad jabber dod org |
> ------------------------------------------------------


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Sat Apr 10 2004 - 01:16:44 EEST