On 2011-03-26, at 06:50, Laszlo Developer wrote: > Thanks a lot for your detailed answer. Presentation Types certainly > are a powerful feature. Do you have any idea when the public API may > be available?
What makes a public API in an open source project is an interesting question. Some API's become public (or private) due to contractual obligations. Some become public because a community member steps forward and creates and maintains the API. Some become public because the developer of another feature sees it as "the right thing to do". In the case of the presentation type system, we are pretty sure that it is "the right thing to do", but we also do not want to commit to supporting an API that has not be fully thought out and tested. (As has occurred in the past, when we were forced to support legacy API's that just made no sense, such as <state> having both a method and an attribute named `apply`!) The presentation type substrate may evolve and the API's may change (but hopefully only for the better), as we utilize the system more fully in support of full CSS-ability of LZX. There are some open questions to be resolved, as you have alluded to in your emails. Maybe if you could explain your requirements for a public API we could work toward resolving those questions and specifying the public API more rapidly?
