Theis, It has just been brought to my attention that we have not responded on this thread yet - thanks for your patience.
This has never been an open source project - it was just a show case of what can be achieved with Wicket, wiQuery, and various jQuery components (like grids, growls, splitters, "portlets" etc) for RIA. We are working on aspects of these extensions with/for various clients and it is quite likely we will only make publicly available/open-source limited parts of it. These should eventually live on the wiQuery-plugins project on gitHub we have been planning for wiQuery with ODLabs and Lionel. As things stand, I would say don't hold your breath as there are various commercial factors we have no control over that any related decisions are dependent on. Regards - Cemal jWeekend Training, Development, Consultancy http://jWeekend.com On 12 June 2010 23:42, Thies Edeling <[email protected]> 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]
