Part 2 of this series were going to talk about nested states. Specifically states nested deeper than two levels.
Ionic uses Ui Router to handle all of it’s routing and state change. Ionic uses many directive throughout it’s framework to add functionality or mimic functionality of angular directives. Ionic uses ion-nav-view to replace UI Routers ui-view and add additional functionality. From their site:
The ion-nav-view is our container. Ionic’s router will look for this directive throughout our code to insert templates. ion-nav-view supports inheritance, named views, and other features that we will discuss in depth throughout this series.
Note: If you’re familiar with angular-ui-router, ion-nav-view is equivalent to ui-view. On top of that, ion-nav-view provides for animations, history, and more.
I am just about finished building my first *complete* mobile application with the Ionic Framework. There were several things I got hung up on and found useful solutions too after doing some research. Some of the answers were on the Ionic website while some were buried on the web. The first post will be in regards to geolocation.
Dependency injection (DI) as defined by Angular… DI in Angular allows you to use modules, services, controllers, directives, and filters that can depend on one another to operate.
By $injecting these dependencies into each other they can reference each others public APIs and operate accordingly. This concept of DI loads all files upfront so that they are available for use whenever necessary (which may be never for certain use cases).