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 < [email protected]> 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 <[email protected]> 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 <[email protected]> > >> 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: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > >> > > > > -- > > 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: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
