Hi,
imagine a SmartGwt application that restores it's ListGrid's view state at startup, and saves it on every action, that changes it. It doesn't matter where the view state is stored: in a preference, data source, or elsewhere. No buttons should be involved in saving or restoring the view state, it should be done automatically, based on event handling.
Which ListGrid handlers should be used as "a good practice" in such case? For instance, the job to save the view state (getViewSate + save it somewhere) could be done inside ViewStateChangedHandler, and the job to restore the state (read it from somewhere + setViewState) - inside DrawHandler?
Thanks!
imagine a SmartGwt application that restores it's ListGrid's view state at startup, and saves it on every action, that changes it. It doesn't matter where the view state is stored: in a preference, data source, or elsewhere. No buttons should be involved in saving or restoring the view state, it should be done automatically, based on event handling.
Which ListGrid handlers should be used as "a good practice" in such case? For instance, the job to save the view state (getViewSate + save it somewhere) could be done inside ViewStateChangedHandler, and the job to restore the state (read it from somewhere + setViewState) - inside DrawHandler?
Thanks!