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

On 2009-03-30 at 08:19:13 [+0200], André Braga <meianoite@xxxxxxxxx> wrote:
> Em 29/03/2009, às 17:49, Niels Reedijk <niels.reedijk@xxxxxxxxx>
> escreveu:
> > I think this discussion is missing a third option. [...] 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.
> 
> There is a fourth option that I'm truly surprised no one brought up yet.
> 
> Much of this discussion have centered around the relevance of Haiku as
> a platform as it competes with Windows, Mac OS, and X11-based OSs in
> general.
> 
> Well, the 4th option would then be fixing the shortcomings of the Be
> API for R2 (that's a given), and model additional APIs and kits after
> the good stuff found on Qt. And then surpass it. Not in featur...itis,
> but in *brilliance*.
> 
> It would then be quite possible to, instead of porting Qt, have
> wrappers mapping popular Qt classes into HR2 ones, which essentially
> has the effect of removing Qt's platform abstraction layer as much as
> possible. The rest of Qt which wouldn't make sense to have a
> correspondence in the native API could be ported with considerable
> ease, then.

Qt is a complete toolkit with most classes depending on other classes. You 
can't just take out a single class and use/wrap it. As for the "abstraction 
layer" several people have mentioned: The Qt API *is* the abstraction 
layer. Just as the kits of the Be API are an abstraction layer.

CU, Ingo

Other related posts: