[haiku-development] Re: Using the Haiku layout manager in app not part of Haiku
- From: "Bruno Albuquerque" <bga@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 12 Apr 2009 09:12:45
On Sat, 11 Apr 2009 16:27:54 -0400, Ryan Leavengood said:
> > It will definitely change when we break binary compatibility.
> > Anyway, it's
> > experimental API, that is there won't compatiblity support until it
> > is
> > declared final. Hence an application written against the current
> > layout API
> > might break earlier or later.
>
> Do you have any idea when it will be declared final? Not allowing
> that
> to be used safely by application developers outside of the Haiku code
> base kind of removes a lot of the benefit. I would not have spent any
> time promoting it or writing articles about it if I had understood
> just how fragile it was.
Thsi is an open-source project. Although I unbderstand rewritting code
to fit API changes is not fun, this has no near the impact of writting
software for closed-source systems/APIs where even knowing what is
happening is difficult until something is released and you notice your
program breaks. If it was me deciding to use it I would simply do it
and fix things later when needed. This is a way better procedure in a
open-source project then doing nothing and waiting for things to happen.
This is just my opinion anyway.
> >> But I still plan to use it in any software I write.
> >
> > You do that on your own risk.
>
> That is unfortunate. How can someone write software for Haiku that is
> font sensitive and has localization support (once the Locale Kit is
> done) without using this API?
Simple answer, use the API. :) It will probably change, yes, but so
what?
> I suppose many of us will just have to take the risk.
And I see no reason not to. Even if you wrote something not using the
API you would probably want to make use of it when it is considered
final (is any API really final anyway?). And this means rewritting the
code to use it. :P
-Bruno
Other related posts:
