Hi,
I'm using angularjs version 1.2.19 on Chrome browser.
I have a SPA with several views (around 8).
Each view is packed with dynamic objects (like kendoui widgets, tons of
listeners etc.).
Now that everything's working fine, I want to fine tune things.
I've read about 2 methods that can be used to easily boost load speed and
save state of a page when moving away from it.
1) Speed boost - using ng-animate: How exactly does this help to speed up
the load time? From what I've read, it caches the partials I'm using. Is
this correct? If so, do I need to ng-animate every time I'm using partials
(e.g. ng-include)? Can someone give a live example how to use ng-animate in
order to speed things up (or maybe, just using ng-include does the caching
already?).
2) Speed boost + state saving - caching dom elements/whole views with
cacheFactory: from what I've read, I can save the dom elements inside a
cache object on view change, and then use the cache instead of reloading
the view once the user returns to this view again (as long as it is the
same session, I believe). Has anyone actually done this? Can someone give a
live example for how this works using the core route module?
Thanks
I'm using angularjs version 1.2.19 on Chrome browser.
I have a SPA with several views (around 8).
Each view is packed with dynamic objects (like kendoui widgets, tons of
listeners etc.).
Now that everything's working fine, I want to fine tune things.
I've read about 2 methods that can be used to easily boost load speed and
save state of a page when moving away from it.
1) Speed boost - using ng-animate: How exactly does this help to speed up
the load time? From what I've read, it caches the partials I'm using. Is
this correct? If so, do I need to ng-animate every time I'm using partials
(e.g. ng-include)? Can someone give a live example how to use ng-animate in
order to speed things up (or maybe, just using ng-include does the caching
already?).
2) Speed boost + state saving - caching dom elements/whole views with
cacheFactory: from what I've read, I can save the dom elements inside a
cache object on view change, and then use the cache instead of reloading
the view once the user returns to this view again (as long as it is the
same session, I believe). Has anyone actually done this? Can someone give a
live example for how this works using the core route module?
Thanks