Hi, On 2010-03-03 at 09:07:53 [+0100], Niels Reedijk <niels.reedijk@xxxxxxxxx> wrote: > > 2. Providing non-public API's in R1. Eg, Layout Kit, Locale Kit. > > My opinion is that if they make it in the beta cycle, they should not > be private anymore. Especially the Layout API (not Kit IMO) is a very > nice and important addition, and I imagine the Locale Kit also having > fans. IMHO pulling those out of Haiku is no viable option anyway, it's just a question whether the public headers are included. > I guess the Layout API is very far in the game (and I guess we might > even declare that public soon), the Locale Kit needs much more work. I find the layout API nice as is, especially with the builders. I believe what's missing is integration with the archiving feature in general, or at least testing. I don't know what currently happens when you archive a BView hierarchy that is layout managed, and unarchive it again. Second, the Layout API needs to be made FBC save. That is, adding a whole bunch of padding virtuals and padding data to each class as needed. Ingo may come up with more TODOs, but those two are the absolute essentials which need to be done independent of any discussion about the actual API. Note that no work needs to be done on those builders, since that is template code which gets compiled into each application, and is therefore noncritical. Best regards, -Stephan