On Mon, Aug 15, 2011 at 6:59 PM, Howard Lewis Ship <[email protected]> wrote:
> 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 > customizability. > Maybe too often people use it and try to fit it in every scenario. But IMO that's not bad, BTW creating a grid component at least as good as the current one is not a trivial task. Also wanting t5 components to be "infinitely" extensible so you can model every scenario leads to better innovation and more generic components don't you agree? I'm quite aware of the dangers of having something like EmbeddedMixin in the framework. But someone who wants to access inner components, should be extensively warned of possible future incompatibility issues, but maybe its acceptable risk. BTW I don't think components have changed that much right? Before doing this EmbeddedMixin I was thinking of triggering events for all the render phases of a component so that components and mixins can use them. Eample: Outer component handles setupRenderFromGridCell() or afterRenderFromGridRows() for example. Mixins do similar things. The difference is that you know exactly on which component you apply a mixin. In this case you don't you just assume existence of some embedded component etc, and thats a pretty safe trade over IMO. Cheers, Dragan Sahpaski > > 2011/8/15 Denis Stepanov <[email protected]>: > > 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 > http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
