Nice! Do you have the example running somewhere so the curious don't need to spend time setting it up?
Cheers, =David On Jun 14, 2010, at 3:37 PM, Ernesto Reinaldo Barreiro wrote: > Hi, > > I have started [1] sometime ago. This Wicket-jqgrid integration > already supports many of jqgrid's options and is capable of rendering > of Wicket components as grid cells. I'm planning to maintain this > project and I'm also willing to let other people to join in if they > think (and prove) they can make significant contributions to the > project. The project also contains integrations with other jquery > plug-ins as well as a prototype of another grid based on jquery (I'm > actively improving this component right now as I'm planning to use it > for some projects). There is a small demo project [3] you can use to > see components in action. Project is fully mavenized so it is very > easy to start using it. > > Best, > > Ernesto > > References, > > [1] > -http://code.google.com/p/wiquery-plugins/source/browse/#svn/trunk/wiquery-plugins/jqgrid > [2] > -http://code.google.com/p/wiquery-plugins/source/browse/#svn/trunk/wiquery-plugins/antila-grid > [3] - > http://code.google.com/p/wiquery-plugins/source/browse/#svn/trunk/wiquery-plugins/example-war > > On Mon, Jun 14, 2010 at 8:05 AM, David Leangen <[email protected]> wrote: >> >> I don't think the project is very active. Started with a bang, but there >> hasn't been much action lately, or so it seems. >> >> >> On Jun 13, 2010, at 7:42 AM, Thies Edeling wrote: >> >>> Is this project still alive? The URL below now prompts for a >>> username/password. Thx! >>> >>> On Wed, Mar 10, 2010 at 1:10 AM, Cemal Bayramoglu < >>> [email protected]> wrote: >>> >>>> http://labs.jweekend.com/public/grid/GridRowExpanderPage >>>> >>>> On 3 March 2010 18:20, John Armstrong <[email protected]> wrote: >>>>> Hi Richard, >>>>> >>>>> See here: http://www.extjs.com/examples/explorer.html#gridplugins >>>>> >>>>> <http://www.extjs.com/examples/explorer.html#gridplugins>In this case >>>> its a >>>>> grid rather then a tree that expands and allows arbitrary components to >>>> be >>>>> inserted beneath the row. >>>>> >>>>> Similar to a tree but very grid specific. >>>>> >>>>> Very excited about your work, so many hoops too jump through with GWT.. >>>>> J >>>>> >>>>> On Wed, Mar 3, 2010 at 10:17 AM, Richard Wilkinson < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> John - im not to sure what you mean by row expanders, is that similar >>>>>> to what is provided on the tree grid? >>>>>> >>>>>> Ernesto - see comments inline: >>>>>> >>>>>> >>>>>> On 3 March 2010 12:59, Ernesto Reinaldo Barreiro <[email protected]> >>>>>> wrote: >>>>>>> Hi Cemal, >>>>>>> >>>>>>> Other things that might be useful: >>>>>>> >>>>>>> -Offer (pluggable) support for grid events at client and server side >>>>>> (e.g. >>>>>>> been notified when user navigates between pages, sorts a columns, >>>> etc). >>>>>> By >>>>>>> pluggable I mean they can be enable if you need them so that no >>>>>> unnecessary >>>>>>> server round trips are made. >>>>>> >>>>>> The gird always has to make a request to the server when the user >>>>>> navigates between pages, or changes the sorting, since this requires >>>>>> updated data. However these events are handled internally to the grid >>>>>> code and are not accessible to the developer. If required we could >>>>>> make these events accessible to the developer, either through adding a >>>>>> behaviour, or overriding a method. Other things such as selection >>>>>> notification events, or editing, can optionally be listened to by the >>>>>> developer, but these do not make a round trip to the server unless >>>>>> they are explicitly added. >>>>>> >>>>>>> -Show an example of how the grid interacts with a normal wicket form. >>>>>> E.g. >>>>>>> have a form the is submitted via Wicket AJAX and get the grid >>>> refreshed >>>>>>> either via Wicket AJAX (i.e. the whole grid component is reloaded) or >>>>>>> triggering a reload event on the grid (I see the master detail example >>>> is >>>>>>> built using this last approach?) . >>>>>> >>>>>> yes, this page (http://labs.jweekend.com/public/gridjpa/ProjectEditPage >>>> ) >>>>>> uses a wicket form (not automatically generated though) to edit a row >>>>>> in one grid, which then triggers a data refresh in both grids, but >>>>>> does not do a wicket ajax component replace. However ajax component >>>>>> replace is supported as there is an AjaxRequestTarget, but I feel that >>>>>> forcing the grid to reload is cleaner. >>>>>> >>>>>>> -All the examples seem to use JSON for data transfer? Is XML >>>> supported? >>>>>> >>>>>> The grid uses JSON, however this is all internal and transparent to >>>>>> the developer using the grid, so I dont see how supporting XML would >>>>>> be a benefit. It is not possible to construct JSON or XML and feed >>>>>> this into the grid manually, i.e. by telling the grid which url to >>>>>> use. >>>>>> >>>>>> The intended use is the same as with a Wicket DataTable, where an >>>>>> IDataProvider provides an iterator of beans which are rendered as rows >>>>>> in the grid. We use Wicket IConverter to convert each field of the >>>>>> bean to a String, then use a JSON library to construct the JSON >>>>>> response, which is then used in a custom wicket IRequestTarget for >>>>>> JSON. >>>>>> >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Ernesto >>>>>>> >>>>>>> On Wed, Mar 3, 2010 at 11:33 AM, Cemal Bayramoglu < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards - Richard Wilkinson >>>>>> Developer, >>>>>> jWeekend: OO & Java Technologies - Development and Training >>>>>> http://jWeekend.com >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
