Re: wiQuery components with server side state - live demo
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 tedel...@gmail.com 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 jweekend_for...@cabouge.com wrote: http://labs.jweekend.com/public/grid/GridRowExpanderPage On 3 March 2010 18:20, John Armstrong siber...@siberian.org wrote: Hi Richard, See here: http://www.extjs.com/examples/explorer.html#gridplugins http://www.extjs.com/examples/explorer.html#gridpluginsIn 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 richard.wilkin...@jweekend.com 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 reier...@gmail.com 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 jweekend_for...@cabouge.com wrote: -- Regards - Richard Wilkinson Developer, jWeekend: OO Java Technologies - Development and Training http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands,
Re: wiQuery components with server side state - live demo
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 jweekend_for...@cabouge.com wrote: http://labs.jweekend.com/public/grid/GridRowExpanderPage On 3 March 2010 18:20, John Armstrong siber...@siberian.org wrote: Hi Richard, See here: http://www.extjs.com/examples/explorer.html#gridplugins http://www.extjs.com/examples/explorer.html#gridpluginsIn 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 richard.wilkin...@jweekend.com 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 reier...@gmail.com 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 jweekend_for...@cabouge.com wrote: -- Regards - Richard Wilkinson Developer, jWeekend: OO Java Technologies - Development and Training http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
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 wic...@leangen.net 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 jweekend_for...@cabouge.com wrote: http://labs.jweekend.com/public/grid/GridRowExpanderPage On 3 March 2010 18:20, John Armstrong siber...@siberian.org wrote: Hi Richard, See here: http://www.extjs.com/examples/explorer.html#gridplugins http://www.extjs.com/examples/explorer.html#gridpluginsIn 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 richard.wilkin...@jweekend.com 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 reier...@gmail.com 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 jweekend_for...@cabouge.com wrote: -- Regards - Richard Wilkinson Developer, jWeekend: OO Java Technologies - Development and Training http://jWeekend.com - To unsubscribe, e-mail:
Re: wiQuery components with server side state - live demo
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 wic...@leangen.net 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 jweekend_for...@cabouge.com wrote: http://labs.jweekend.com/public/grid/GridRowExpanderPage On 3 March 2010 18:20, John Armstrong siber...@siberian.org wrote: Hi Richard, See here: http://www.extjs.com/examples/explorer.html#gridplugins http://www.extjs.com/examples/explorer.html#gridpluginsIn 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 richard.wilkin...@jweekend.com 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 reier...@gmail.com 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 jweekend_for...@cabouge.com wrote: --
Re: wiQuery components with server side state - live demo
David, Unfortunately not: my free time is very limited and I've tried to use it doing what I need (create new components). But getting a local copy to work should not be that hard. 1- Check out http://code.google.com/p/wiquery-plugins/source/browse/#svn/trunk/wiquery-plugins 2- on wiquery-plugins type maven install 3- and then use maven jetty:run on wiquery-plugins/example-war 4- browse at http://localhost:8080/wiquery-plugins/ As said the demo is very small and just contains a few screens but at least it is something to get started with. Best, Ernesto On Mon, Jun 14, 2010 at 8:40 AM, David Leangen wic...@leangen.net wrote: 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 wic...@leangen.net 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 jweekend_for...@cabouge.com wrote: http://labs.jweekend.com/public/grid/GridRowExpanderPage On 3 March 2010 18:20, John Armstrong siber...@siberian.org wrote: Hi Richard, See here: http://www.extjs.com/examples/explorer.html#gridplugins http://www.extjs.com/examples/explorer.html#gridpluginsIn 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 richard.wilkin...@jweekend.com 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 reier...@gmail.com 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
Re: wiQuery components with server side state - live demo
and David, the project is compatible with wiquery. Best, Ernesto On Mon, Jun 14, 2010 at 9:02 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: David, Unfortunately not: my free time is very limited and I've tried to use it doing what I need (create new components). But getting a local copy to work should not be that hard. 1- Check out http://code.google.com/p/wiquery-plugins/source/browse/#svn/trunk/wiquery-plugins 2- on wiquery-plugins type maven install 3- and then use maven jetty:run on wiquery-plugins/example-war 4- browse at http://localhost:8080/wiquery-plugins/ As said the demo is very small and just contains a few screens but at least it is something to get started with. Best, Ernesto On Mon, Jun 14, 2010 at 8:40 AM, David Leangen wic...@leangen.net wrote: 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 wic...@leangen.net 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 jweekend_for...@cabouge.com wrote: http://labs.jweekend.com/public/grid/GridRowExpanderPage On 3 March 2010 18:20, John Armstrong siber...@siberian.org wrote: Hi Richard, See here: http://www.extjs.com/examples/explorer.html#gridplugins http://www.extjs.com/examples/explorer.html#gridpluginsIn 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 richard.wilkin...@jweekend.com 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 reier...@gmail.com 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
Re: wiQuery components with server side state - live demo
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 jweekend_for...@cabouge.com wrote: http://labs.jweekend.com/public/grid/GridRowExpanderPage On 3 March 2010 18:20, John Armstrong siber...@siberian.org wrote: Hi Richard, See here: http://www.extjs.com/examples/explorer.html#gridplugins http://www.extjs.com/examples/explorer.html#gridpluginsIn 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 richard.wilkin...@jweekend.com 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 reier...@gmail.com 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 jweekend_for...@cabouge.com wrote: -- Regards - Richard Wilkinson Developer, jWeekend: OO Java Technologies - Development and Training http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
http://labs.jweekend.com/public/grid/GridRowExpanderPage On 3 March 2010 18:20, John Armstrong siber...@siberian.org wrote: Hi Richard, See here: http://www.extjs.com/examples/explorer.html#gridplugins http://www.extjs.com/examples/explorer.html#gridpluginsIn 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 richard.wilkin...@jweekend.com 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 reier...@gmail.com 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 jweekend_for...@cabouge.com wrote: -- Regards - Richard Wilkinson Developer, jWeekend: OO Java Technologies - Development and Training http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Really cool demo! Is there a place where I can see source for the portal demo? If I show the guys at work I can use it, we will defently choose WiQuery. They're talking about GXT and other stuff which I really don't want to go into. Eyal Golan egola...@gmail.com Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 P Save a tree. Please don't print this e-mail unless it's really necessary On Tue, Mar 2, 2010 at 6:58 PM, Cemal A Bayramoglu ce...@jweekend.comwrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Eyal, Thanks. We will be working on that as soon as we get another opportunity. Perhaps we will try to coincide our release with the release of wiQuery 1.0.1 which we may also have by the end of the month. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com On 8 March 2010 15:05, Eyal Golan egola...@gmail.com wrote: Really cool demo! Is there a place where I can see source for the portal demo? If I show the guys at work I can use it, we will defently choose WiQuery. They're talking about GXT and other stuff which I really don't want to go into. Eyal Golan egola...@gmail.com Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 P Save a tree. Please don't print this e-mail unless it's really necessary On Tue, Mar 2, 2010 at 6:58 PM, Cemal A Bayramoglu ce...@jweekend.comwrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
AW: wiQuery components with server side state - live demo
Hi, i've found a bug at http://labs.jweekend.com/public/grid/GridDnDPage Click and hold on a column header and moving mouse around expands the header columnm, what i think is not intended. Greets Chris -Ursprüngliche Nachricht- Von: ce...@jweekend.com [mailto:ce...@jweekend.com] Im Auftrag von Cemal Bayramoglu Gesendet: Mittwoch, 3. März 2010 11:33 An: users@wicket.apache.org Betreff: Re: wiQuery components with server side state - live demo This is all useful feedback, thank you. Storing things like the user's selected columns, their order, row sort order, number of rows per page, preferred/selected themes etc ... are on our list of things to consider. I envisage persisting these user-specific setting (preferences/profiles/perspectives/views?) server-side, perhaps triggered by a user request to do so (eg hitting a Save A (Named) View Settings button). We've also talked about the less permanent persistence for page-refreshes, which could potentially be held on the client-side, in the Wicket page or session. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com On 2 March 2010 23:10, Vladimir K koval...@gmail.com wrote: Looks great! One thing is missing - the components don't restore their state on refresh. I believe cookie, window name or dom storage can be used to keep the position and settings of components that are available for dragging/re-arrangement. Roman Ilin wrote: Great, ready for use components. On Tue, Mar 2, 2010 at 5:58 PM, Cemal A Bayramoglu ce...@jweekend.com wrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://old.nabble.com/wiQuery-components-with-server-side-state---live-demo-tp27758298p27762474.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Chris - Thanks for spotting that. I think it is a bug with the underlying jqGrid javascript code. I notice that on the jqGrid drag and drop demo, sortable columns are not enabled. I will try and confirm that the problem is indeed with jqGrid and report the bug to them when I get chance. John - I see, cool feature. jqGrid supports something like this so I have added onto my list of desired features. -- Regards - Richard Wilkinson Developer, jWeekend: OO Java Technologies - Development and Training http://jWeekend.com On 5 March 2010 08:49, Giambalvo, Christian christian.giamba...@excelsisnet.com wrote: Hi, i've found a bug at http://labs.jweekend.com/public/grid/GridDnDPage Click and hold on a column header and moving mouse around expands the header columnm, what i think is not intended. Greets Chris -Ursprüngliche Nachricht- Von: ce...@jweekend.com [mailto:ce...@jweekend.com] Im Auftrag von Cemal Bayramoglu Gesendet: Mittwoch, 3. März 2010 11:33 An: users@wicket.apache.org Betreff: Re: wiQuery components with server side state - live demo This is all useful feedback, thank you. Storing things like the user's selected columns, their order, row sort order, number of rows per page, preferred/selected themes etc ... are on our list of things to consider. I envisage persisting these user-specific setting (preferences/profiles/perspectives/views?) server-side, perhaps triggered by a user request to do so (eg hitting a Save A (Named) View Settings button). We've also talked about the less permanent persistence for page-refreshes, which could potentially be held on the client-side, in the Wicket page or session. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com On 2 March 2010 23:10, Vladimir K koval...@gmail.com wrote: Looks great! One thing is missing - the components don't restore their state on refresh. I believe cookie, window name or dom storage can be used to keep the position and settings of components that are available for dragging/re-arrangement. Roman Ilin wrote: Great, ready for use components. On Tue, Mar 2, 2010 at 5:58 PM, Cemal A Bayramoglu ce...@jweekend.com wrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://old.nabble.com/wiQuery-components-with-server-side-state---live-demo-tp27758298p27762474.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Hi Cemal, Yes you are right. I'll keep the details for our private communications... My apologies if I have been a bit pushy on this matter... Best regards, Ernesto On Wed, Mar 3, 2010 at 10:42 PM, Cemal Bayramoglu jweekend_for...@cabouge.com wrote: Ernesto, Thanks for putting so much time and thought into your project and your response. Our jqGrid implementation has been gathering dust for several months in our own repository but we do like to work on it when we can, and Richard keeps an eye on interesting features the jqGrid guys introduce so we can expose the ones we like via our component. We've only just unveiled it here, even though it is not ready to be opened/released, because we are keen to get the gitHub hosted wiQuery plugins project off the ground promptly so we can have discussions such as this (very detailed and specific to wiQuery plugins) in a central place and benefit from the ideas and effort developers like you are generously and eagerly already putting in! This will also give you the access we have not yet been able to grant you so far to our code base, so you can contribute directly to the evolution of these new wiQuery components if that makes sense for you. I can already see that you are in a good position to speed up the development process on this component, In the meantime, I suggest we keep the detailed emails like this on our own private thread that you mentioned below and that I started for all directly interested last week so all this useful information is not too scattered and hard to find. You will also learn tomorrow from Lionel that we have some interesting ideas for further, reference components that will be a great place to direct your contributions while we get ready to open these components too. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com On 3 March 2010 21:13, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Hi Richard, Some of these I already answered in a private e-mail... Just about XML vs JSON. You can have a flag on the grid that decides XML or JSON and then transparently generate one or the other See for instance http://code.google.com/p/wijqgrid/source/browse/trunk/wijqgrid/src/main/java/com/wijqgrid/component/GridXMLData.java and how it is used on http://code.google.com/p/wijqgrid/source/browse/trunk/wijqgrid/src/main/java/com/wijqgrid/component/Grid.java The original grid supports either XML or JSON. Why not support both of them then? Regarding events see: http://code.google.com/p/wijqgrid/source/browse/trunk/wijqgrid/src/main/java/com/wijqgrid/component/#component/event Best, Ernesto On Wed, Mar 3, 2010 at 7:17 PM, Richard Wilkinson richard.wilkin...@jweekend.com 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 reier...@gmail.com 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
Re: wiQuery components with server side state - live demo
This is all useful feedback, thank you. Storing things like the user's selected columns, their order, row sort order, number of rows per page, preferred/selected themes etc ... are on our list of things to consider. I envisage persisting these user-specific setting (preferences/profiles/perspectives/views?) server-side, perhaps triggered by a user request to do so (eg hitting a Save A (Named) View Settings button). We've also talked about the less permanent persistence for page-refreshes, which could potentially be held on the client-side, in the Wicket page or session. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com On 2 March 2010 23:10, Vladimir K koval...@gmail.com wrote: Looks great! One thing is missing - the components don't restore their state on refresh. I believe cookie, window name or dom storage can be used to keep the position and settings of components that are available for dragging/re-arrangement. Roman Ilin wrote: Great, ready for use components. On Tue, Mar 2, 2010 at 5:58 PM, Cemal A Bayramoglu ce...@jweekend.com wrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://old.nabble.com/wiQuery-components-with-server-side-state---live-demo-tp27758298p27762474.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
This looks very very nice. Thank you for sharing. I am espacially interested in the cometd demo. When do you plan to release it? Regards, richard Cemal A Bayramoglu wrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://old.nabble.com/wiQuery-components-with-server-side-state---live-demo-tp27758298p27767506.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Richard, WeI had a meeting with Lionel and Julien last night where we decided to open a wiQuery plugins project on gitHub,. Our components will also eventually start their public life there. We are also in the process of fixing a Maven repo for wiQuery itself, where we may also host the binaries for the best plugins people contribute. We should have that and a basic LegUp [1] ready for wiQuery this week. We may wait for 1.4.7's release so we don't have to release our LegUp this twice in quick succession though. WRT our wiQuery CometD demo, we do have a working prototype but it's not ready for release; we need to contact the wicket-push project guys first because we have made quite a few changes to that (locally) and we have used the jQuery APIs for CometD. We will be contacting them soon. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [1] http://www.jweekend.com/dev/LegUp On 3 March 2010 12:22, morbo richard.wiesin...@gmail.com wrote: This looks very very nice. Thank you for sharing. I am espacially interested in the cometd demo. When do you plan to release it? Regards, richard Cemal A Bayramoglu wrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://old.nabble.com/wiQuery-components-with-server-side-state---live-demo-tp27758298p27767506.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
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. -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?) . -All the examples seem to use JSON for data transfer? Is XML supported? Best, Ernesto On Wed, Mar 3, 2010 at 11:33 AM, Cemal Bayramoglu jweekend_for...@cabouge.com wrote: This is all useful feedback, thank you. Storing things like the user's selected columns, their order, row sort order, number of rows per page, preferred/selected themes etc ... are on our list of things to consider. I envisage persisting these user-specific setting (preferences/profiles/perspectives/views?) server-side, perhaps triggered by a user request to do so (eg hitting a Save A (Named) View Settings button). We've also talked about the less permanent persistence for page-refreshes, which could potentially be held on the client-side, in the Wicket page or session. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com On 2 March 2010 23:10, Vladimir K koval...@gmail.com wrote: Looks great! One thing is missing - the components don't restore their state on refresh. I believe cookie, window name or dom storage can be used to keep the position and settings of components that are available for dragging/re-arrangement. Roman Ilin wrote: Great, ready for use components. On Tue, Mar 2, 2010 at 5:58 PM, Cemal A Bayramoglu ce...@jweekend.com wrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://old.nabble.com/wiQuery-components-with-server-side-state---live-demo-tp27758298p27762474.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
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 reier...@gmail.com 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 jweekend_for...@cabouge.com wrote: -- Regards - Richard Wilkinson Developer, jWeekend: OO Java Technologies - Development and Training http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Hi Richard, See here: http://www.extjs.com/examples/explorer.html#gridplugins http://www.extjs.com/examples/explorer.html#gridpluginsIn 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 richard.wilkin...@jweekend.com 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 reier...@gmail.com 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 jweekend_for...@cabouge.com wrote: -- Regards - Richard Wilkinson Developer, jWeekend: OO Java Technologies - Development and Training http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Hi Richard, Some of these I already answered in a private e-mail... Just about XML vs JSON. You can have a flag on the grid that decides XML or JSON and then transparently generate one or the other See for instance http://code.google.com/p/wijqgrid/source/browse/trunk/wijqgrid/src/main/java/com/wijqgrid/component/GridXMLData.java and how it is used on http://code.google.com/p/wijqgrid/source/browse/trunk/wijqgrid/src/main/java/com/wijqgrid/component/Grid.java The original grid supports either XML or JSON. Why not support both of them then? Regarding events see: http://code.google.com/p/wijqgrid/source/browse/trunk/wijqgrid/src/main/java/com/wijqgrid/component/#component/event Best, Ernesto On Wed, Mar 3, 2010 at 7:17 PM, Richard Wilkinson richard.wilkin...@jweekend.com 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 reier...@gmail.com 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 jweekend_for...@cabouge.com wrote: -- Regards - Richard Wilkinson Developer, jWeekend: OO Java Technologies - Development and Training http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Ernesto, Thanks for putting so much time and thought into your project and your response. Our jqGrid implementation has been gathering dust for several months in our own repository but we do like to work on it when we can, and Richard keeps an eye on interesting features the jqGrid guys introduce so we can expose the ones we like via our component. We've only just unveiled it here, even though it is not ready to be opened/released, because we are keen to get the gitHub hosted wiQuery plugins project off the ground promptly so we can have discussions such as this (very detailed and specific to wiQuery plugins) in a central place and benefit from the ideas and effort developers like you are generously and eagerly already putting in! This will also give you the access we have not yet been able to grant you so far to our code base, so you can contribute directly to the evolution of these new wiQuery components if that makes sense for you. I can already see that you are in a good position to speed up the development process on this component, In the meantime, I suggest we keep the detailed emails like this on our own private thread that you mentioned below and that I started for all directly interested last week so all this useful information is not too scattered and hard to find. You will also learn tomorrow from Lionel that we have some interesting ideas for further, reference components that will be a great place to direct your contributions while we get ready to open these components too. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com On 3 March 2010 21:13, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Hi Richard, Some of these I already answered in a private e-mail... Just about XML vs JSON. You can have a flag on the grid that decides XML or JSON and then transparently generate one or the other See for instance http://code.google.com/p/wijqgrid/source/browse/trunk/wijqgrid/src/main/java/com/wijqgrid/component/GridXMLData.java and how it is used on http://code.google.com/p/wijqgrid/source/browse/trunk/wijqgrid/src/main/java/com/wijqgrid/component/Grid.java The original grid supports either XML or JSON. Why not support both of them then? Regarding events see: http://code.google.com/p/wijqgrid/source/browse/trunk/wijqgrid/src/main/java/com/wijqgrid/component/#component/event Best, Ernesto On Wed, Mar 3, 2010 at 7:17 PM, Richard Wilkinson richard.wilkin...@jweekend.com 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 reier...@gmail.com 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
wiQuery components with server side state - live demo
We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Great, ready for use components. On Tue, Mar 2, 2010 at 5:58 PM, Cemal A Bayramoglu ce...@jweekend.com wrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Looks great! One thing is missing - the components don't restore their state on refresh. I believe cookie, window name or dom storage can be used to keep the position and settings of components that are available for dragging/re-arrangement. Roman Ilin wrote: Great, ready for use components. On Tue, Mar 2, 2010 at 5:58 PM, Cemal A Bayramoglu ce...@jweekend.com wrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://old.nabble.com/wiQuery-components-with-server-side-state---live-demo-tp27758298p27762474.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wiQuery components with server side state - live demo
Wow, this is fantastic. Wish I'd had it 4 months ago before I had to start dealing with GXT for its grid support :( We'll pick it up for our next project if possible, its exactly what we need. Nice stuff guys. John- PS : RowExpanders would be awesome ;) On Tue, Mar 2, 2010 at 3:10 PM, Vladimir K koval...@gmail.com wrote: Looks great! One thing is missing - the components don't restore their state on refresh. I believe cookie, window name or dom storage can be used to keep the position and settings of components that are available for dragging/re-arrangement. Roman Ilin wrote: Great, ready for use components. On Tue, Mar 2, 2010 at 5:58 PM, Cemal A Bayramoglu ce...@jweekend.com wrote: We've been building a few wiQuery components [0], for clients' and internal projects. These wiQuery components typically maintain some of their state server-side, in the spirit of standard Wicket components. Here's a simple demo [1] to show some of them in action. Look carefully and you'll find lots of stuff to click on [2]. We could plan to open up the ones we may [3] if they look useful to you or you'd like to get involved with design/development/testing. Regards - Cemal jWeekend OO Java Technologies, Wicket Consulting, Development, Training http://jWeekend.com [0] includes components based on sortable portlet, jqGrid/Tree, jGrowl, jQuery UI: Accordian, Dialog, Tabs all integrated with Wicket using wiQuery (http://code.google.com/p/wiquery/) [1] http://labs.jWeekend.com/public/ [2] We'd naturally prefer if you didn't zap _all_ the records from our toy database! Yes, we know some of you will take this as an invitation to have a go! [3] No promises on dates just now, but it is something we'd like to do soon. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://old.nabble.com/wiQuery-components-with-server-side-state---live-demo-tp27758298p27762474.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org