Hi, On Mon, Aug 15, 2011 at 2:11 PM, Thiago H. de Paula Figueiredo < [email protected]> wrote:
> On Sat, 13 Aug 2011 01:39:36 -0300, Robert Zeigler < > [email protected]> wrote: > > I disagree with your assessment of mixins. Mixins are primarily tied to >> the component lifecycle, not to specific component implementations. There >> are certainly some mixins that can't be universally applied (eg: they may >> assume that the component is a ClientElement which may or may not be true), >> but the way you go about implementing them doesn't ordinarily depend on the >> internal structure of the component. Perhaps the closest >> framework-supported exception to that is the @BindParameter, but even there >> you're working with published (ie /public/) information about components, >> rather than private/internal information. >> > > I couldn't have said it better myself, Robert. :) > > -1 to EmbeddedMixin. If you want to modify the output of GridCells inside a > Grid, you can still add the mixin to Grid itself. I don't. I just want to read the gridCell's propertyValue, propertyName and the current row object. > Not much of a difference. By the way, couldn't we provide some better way > to find elements when writing code that uses MarkupWriter and Element? Does > tapestry-xpath provide that? It would definetely simplify a lot some DOM > rewriting code I've written. > True that. Haven't used it so I can't comment on it. Cheers, Dragan Sahpaski > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@tapestry.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
