The stateEvents/saveState/restoreState scheme should be in Observable!

January 8th, 2009
  • Why limit this very useful way of hooking up state saving to UI Components?

    The methods which implement this should be part of Observable.

    That way we can save Model state as well as View state directly without having to use the View as a vehicle for accessing Model state.

    For instance a Store is Observable, you should be able to set some stateEvents on it and have it save its state.


  • +1


  • +1


  • +1


  • Any reason why the state saving configurations and methods cannot be moved up the inheritance hierarchy into Observable? After all, state saving is based on stateEvents

    All Components would still have the state handling, because they all extend Observable, so would continue to work.

    But other Observables would be able to save state. Like Stores and ColumnModels. Someone just asked how to save column widths. The easiest way would be to add stateEvents and a getState to the ColumnModel, but that doesn't have state handling.


  • +1


  • +1







    • #If you have any other info about this subject , Please add it free.#
    Your name:
    E-mail:
    Telphone:

    Your comments:


    If you have any other info about The stateEvents/saveState/restoreState scheme should be in Observable! , Please add it free.

    Posted in freedeadaim.com | edit