+1 (non-binding) And thank you! (For the great framework.)
- Ville Howard Lewis Ship wrote: > > I'm working on the last major feature I'd like to see in 5.1: > template inheritance (*). > > With that, I'm ready to switch from implementing features to fixing bugs. > > I think it would be approrpriate to release 5.1.0.1, fix a bunch of > bugs, then see about getting a beta release out. > > Outside of Spring Web Flow and Portlet support (things I'd like to > work on in 5.2), the only other major feature I see people clammoring > for is dynamic updates on Selects, something I'm still noodling on. > There's probably a few other minor features that would be nice to > haves, but you have to draw the line somewhere! > > > (*) This is an idea I picked up from wicket, though I'm extending it > quite a bit. Parent component templates will be able to define > <t:extension-point>s, and child component template will be able to > provide <t:replace> elements that replace them (a unique id ties the > two together). This can be used an an alternative to using a layout > component, where each page will <t:replace> the default page content > inherited from the base class. I generally think that for pages, a > layout component is better, but for complex components (such as the > Grid), this will be a great new feature for allowing changes to a > container template without cutting and pasting the whole thing. > > -- > Howard M. Lewis Ship > > Creator Apache Tapestry and Apache HiveMind > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/-DISCUSS--Ready-for-5.1.0.1--Winding-down-5.1--tp22418935p22428316.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
