tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Lewis Ship <hls...@gmail.com>
Subject Re: EmbeddedComponent Mixin: -1
Date Mon, 15 Aug 2011 16:59:39 GMT
Actually, I'd rather ensure that it's easier to re-use the Grid
component's constituent parts in new forms than to try and make Grid
all things to all people.  Grid is (supposed to be) scaffolding, like
BeanEditForm, but too often, people make it a major part of the
application, and then are disappointed that there are limits to its

2011/8/15 Denis Stepanov <denis.stepanov@gmail.com>:
> It would be better to have core components more flexible to external changes.
> I'm looking into ContextMenuGridCell and I would rather see extended PropertyOverrides
and extension points concept.
> For example a Grid would provide default extending point for a row:
>> <tr t:point="loopRow" ..>..<
> then PropertyOverrides could provide block/Renderable for "beforeLoopRow" and/or "afterLoopRow".
> I'm not sure if it's possible to bind a propertyOverrides from a mixin… anyway I think
that concept is pretty clear.
> Also EmbeddedMixin would be useless if there wasn't a GridRows component.
> Denis

Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message