jqmViewport
jqmViewport
directive defines the element under which
the mobile pages are added. This automatically adds ng-view
to it.
Defining transitions for pages
Every route can have the extra property transition
with the name of the transition to use
when going to that page. Transition names:
Integration with browser history
When going back using the browser back button, the transition that was used to show the page is
played backwards, ignoring the transition
property of the page that is about to be shown.
This is the same behavior as in jqm.
Feature detection
Browsers that don't support 3d animations, all complex transitions (like pop
) fall back to the slide
transition.
This is the same behavior as in jqm.
The angular-jqm
projects adds caching to angular views (ng-view
).
Cached views allow to cache views including their scopes using the $jqmViewCache
service.
By this, changing views with routes gets very fast as there is no need to recompile them on every visit.
To make this work the semantics of routes were changed a little:
$templateCache
service are compiled with a new disconnected scope
on startup.$viewContentLoaded
event to be notified that
their route is activated again.