I would consider using local storage if that is an option. Alternatively using a some sort of generic Service for saving states. You may want to look at Restangular as I'm pretty sure that has some sort of state provider.
Cheers Rob On Monday, 17 March 2014 05:17:09 UTC, Rajesh wrote: > > We have a fairly complex application (more than 100 views and > controllers). Let me explain the problem space with an example. When a user > is trying to create a new quotation (View 1), they may not find a product > in the list. So they need to go to a different view (View 2) to add a new > product, and then continue working on the quotation (View 1). The data > entered on the quotation before adding the new product should be retained > while returning after adding the new product. > > While using a service to share data between these controllers seems to do > the job, we have a large number of such use cases, and therefore there will > be a large number of services and dependencies to manage. Is it a good > practice to use the rootScope for storing and retrieving the state instead? > > A similar use case is to retain the filter (search) values on a list view > after the user navigates to a different view and comes back. > > Thanks! > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
