and to the View is to use Controllers. Every controller created has a $scope object that lets us do some powerful things Retrieve and Store data Add helper functions Watch when data changes Use events
our app. All content from that new location would be rendered into a single "view" element. <div ng-app="AngularDemo"> <h1>This is a Demo!</h1> <div ng-view=""></div> </div> angular.module('AngularDemo', ['ngRoute']).config(function($routeProvider){ $routeProvider .when('/', { templateUrl: 'partial/main.html', controller: 'MainController' }) .when('/page1',{ templateUrl: 'partial/page1.html', controller: 'Page1Controller' }) .otherwise({ redirectTo: '/' }) });
us define multiple views where content can be loaded into Also is stateful and allows for 'parent' routes (for common templating) This difference was the biggest hurdle I had to get over
Side Menu, Keyboard, etc) Other projects coming Ionic: Ionicons - Icon set ngCordova - AngularJS style extensions for Phonegap/Cordova Ionic Box - Ready-to-go dev. environment to build Ionic Apps onto Android. Creator - a GUI-based Ionic designer (soon to be in Beta)