Diego Netto diegonetto

## app.js
// Quick and dirty example that illustrates the ModelService paradigm
// for sharing data models between multiple controllers.
//
// Once `UserService` is injected into a controller and `UserService.login()`
// returns successfully, any expressions data-bound to properties of the
// `UserService.model` object in the scope of other controllers should be properly updated.
//
// In this example, model mutation is controlled within the context of the
// service, so only calls to `UserService.login()` will update `UserService.model`.
// It would also make since to have the UserService API expose an `update()`

## index.html
<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <meta name="viewport" content="initial-scale=1, maximum-scale=1, user-scalable=no, width=device-width">
    <title>"Test3"</title>

    <!-- build:css({.tmp,app}) styles/main.css -->
    <link rel="stylesheet" href="styles/main.css">
    <!-- endbuild -->
	// Quick and dirty example that illustrates the ModelService paradigm
	// for sharing data models between multiple controllers.
	//
	// Once `UserService` is injected into a controller and `UserService.login()`
	// returns successfully, any expressions data-bound to properties of the
	// `UserService.model` object in the scope of other controllers should be properly updated.
	//
	// In this example, model mutation is controlled within the context of the
	// service, so only calls to `UserService.login()` will update `UserService.model`.
	// It would also make since to have the UserService API expose an `update()`
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8">
	<meta name="viewport" content="initial-scale=1, maximum-scale=1, user-scalable=no, width=device-width">
	<title>"Test3"</title>

	<!-- build:css({.tmp,app}) styles/main.css -->
	<link rel="stylesheet" href="styles/main.css">
	<!-- endbuild -->