Hi Recently I had to a similar requirement. I created a new component, embedded a grid in it. It took filter block as a parameter.
I extended GridDataSource to include filtering based on a filter object and this object was the bean for the filter block form Hope it helps regards taha On Wed, Dec 15, 2010 at 9:39 PM, Michael Gentry <mgen...@masslight.net>wrote: > I'm not a Grid expert, but I really doubt you can intermix the two. > > mrg > > > On Wed, Dec 15, 2010 at 10:09 AM, Wechsung, Wulf <wulf.wechs...@sap.com> > wrote: > > Hello Michael, > > > > Great link, thanks a lot! Skimming over the documentation it should be > possible to integrate this with Grid, perhaps even as a mixin. > > > > Kind Regards, Wulf > > > > -----Ursprüngliche Nachricht----- > > Von: Michael Gentry [mailto:mgen...@masslight.net] > > Gesendet: Mittwoch, 15. Dezember 2010 15:00 > > An: Tapestry users > > Betreff: Re: Advanced Grid > > > > If using a Grid isn't a requirement, take a look at this > JavaScript/JQuery > > table component (there are many examples, but this one does per-column > > filtering): > > > > http://www.datatables.net/examples/api/multi_filter.html > > > > mrg > > > > > > On Wed, Dec 15, 2010 at 8:43 AM, Wechsung, Wulf <wulf.wechs...@sap.com > >wrote: > > > >> Hello Tapestry Users, > >> > >> I'm writing to you because I would like to add a filter functionality to > >> the Grid component. In short, this filter consists of a text field per > >> column in the header row. Text entered there should filter out all rows > that > >> don't match the text. To make clearer what I mean, I've attached a > >> (hopefully small enough) picture of my current prototype implemented by > >> giving a header block as param to the Grid component: > >> > >> Functionally, if the user enters i.e. *100* under "Size Header" the > Grid > >> should update and contain only the two matching rows. > >> > >> My question is this: > >> Does anyone have any advice on what the smoothest way to add this (and > >> maybe get the changes back into tapestry later, if my employer allows > it) > >> would be? My current plan is to simply copy the current Grid > implementation > >> and modify it to support the filter feature, creating a completely new > >> component. Did I miss something obvious in tapestry that would allow me > to > >> this more easily? The route I took with the prototype doesn't get me > father > >> as I currently don't see how to supply the grid with these blocks both > >> dynamically and generically. > >> > >> Thanks for the time you took to read this and thanks in advance for any > >> response you send my way. > >> Also thanks to HLS and all tapesty developer and testers for making a > this > >> framework. > >> > >> Kind Regards, > >> *Wulf Wechsung * > >> > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > >> For additional commands, e-mail: users-h...@tapestry.apache.org > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
