Thanks the response! Since I wanted the mixin to work seamless I went with copying the Grid, extending it to implement ClientElement and delegating the new getClientId() to the "Any table" component. Hopefully Howard will consider changing the official Grid in a similar manner.
Kind Regards, Wulf -----Original Message----- From: Igor Drobiazko [mailto:igor.drobia...@gmail.com] Sent: Mittwoch, 19. Januar 2011 17:35 To: Tapestry users Subject: Re: Grid and clientId Just provide a value for the informal parameter id. <t:grid id="foo"></t:grid> On Mon, Jan 17, 2011 at 5:53 PM, Wechsung, Wulf <wulf.wechs...@sap.com>wrote: > Hello fellow tapestriants, > > I'm trying to do a mixin for grids. As usual, the mixin does some > javascript which I output in the @AfterRender of the mixin. Naturally, in > the javascript I would like to reference the client-side representation of > the element that is being "mixed into" (the grid's table). As per copy pasta > from t5.corelib.mixins.Autocomplete I would like to @InjectContainer Grid > grid and then simply do grid.getClientId(). Unfortunately Grid does not > implement t5.ClientElement. > > Is this a bug? > > How can I : > - make the Grid allocate an id for the table > - render it out, > - access the allocated id > > Ideally all this would be triggered by the mixin so that the mixin could > take any plain old grid. > > Thanks and kind Regards, > Wulf > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Best regards, Igor Drobiazko http://tapestry5.de --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org