[haiku-development] Re: Haiku, Qt and apps, oh my!

On Sun, Mar 29, 2009 at 4:49 PM, Niels Reedijk <niels.reedijk@xxxxxxxxx> wrote:

> This option is to use the Qt API as the core Haiku API. This means
> side-tracking the BeOS API as a legacy API, and rewriting the kernel
> and the app_server in such a way that it supports Qt as a native API.
>
> Now if this idea is ever viable for discussion (which I doubt it will
> when I view this thread), it will obviously invoke a lot of emotional
> responses. Many of the arguments will boil down to taste, for example
> in this thread Axel severely disliking Qt's use of moc and signals and
> slots. Or about doing away with BeOS concepts such as messages (at
> least in the GUI programming).

a problem is that the Haiku version of qt will be a second class
citizen but would now be so fundamental to the OS. Got a problem with
qt? You have to deal with trolltech. They know their qt inside and
out. But why would they care about the haiku implementation when it
represents a tiny percentage of their users?

Other related posts: