feat: fast-forward the tutorial to the post-1.5.0 era

[gkalpak]

This PR constitutes a major re-structuring of the tutorial app's codebase, aiming at applying established best practices (in terms of file naming/layout and code organization) and utilizing several new features and enhancements (most notably components) introduced in recent versions of Angular (especially v1.5).

Apart from the overall changes, two new chapters were introduced: one on components and one on code organization.

In the process, several other things were (incidentally) taken care of, including:

• Dependencies were upgraded to latest versions.
• Animations were polished.
• Outdated links were updated.
• The app's base URL was changed to / (instead of /app/).
• ...etc...

BTW, I have tested with the following versions on Node (on Windows 10) and everything seems to work fine:

• 0.11.16
• 4.2.6
• 4.4.2
• 5.10.0

This was inspired by (and loosely based on) #289.
Mad props to @teropa for leading the way :)

Note:
The old version of the tutorial, that is compatible with Angular version 1.4 or older, has been saved in the pre-v1.5.0-snapshot branch. The v1.4.x version of the tutorial should be pointed to that branch instead of master.

Related to angular/angular.js#14416.
Related to angular/angular-seed#341.

---

Fixes #198
Fixes #214
Fixes #224
Fixes #230
Fixes #243
Fixes #246
Fixes #252
Fixes #277
Fixes #286
Fixes #295
Fixes #303
Fixes #304
Fixes #323
Fixes #324

Closes #268
Closes #270
Closes #278
Closes #280
Closes #289
Closes #309
Closes #311
Closes #319

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

[gkalpak]

This has to get merged simultaneously with corresponding PRs on:

Repo	PRs
angular.js	#14416
angular-seed	#341
angular.io	#1106 (see Upgrading from 1.x)

Things that should/could be considered (potentially after this PR has been merged merged):

• Make sure the static app on the gh-pages branch still works as expected.
• Adding an "advanced" section at the end, either pointing to resources (e.g. relevant Developer Guide sections) or as subsequent steps. Example topics:
  • Directives/DDO, 2-way/1-way/1-time bindings
  • Forms (+ ngMessages)
  • ngComponentRouter
  • (multi-slot) transclusion
  • Task runners/Build tools and best practices
  • Testing animations
• Update Travis to Node v5.
• To discuss: Is it better to import the core module from the main phonecatApp module only, or on a per-view basis ?
• To discuss: Is it better to split up the CSS per component or keep it in a couple top-level files (e.g. one for animations and one for the rest) ? What about animation-related JS code ?
• To discuss: Do we want to mention/use Protractor's directConnect: true config option ?

[teropa]

@gkalpak @petebacondarwin The corresponding PR for angular.io is angular/angular.io#1106 where all the relevant changes have been done.

[rleir]

gkalpak:post-v1.5.0-update works nicely for me. But first I have to change bower.js; it still calls for angular 1.4.x in some steps (I must be doing something wrong).

Would it make sense to merge the 16 commits, then sort out the minor glitches?

[gkalpak]

@rleir, if you can point out in what steps you see 1.4.x versions being called, I could look into it.

This (and the related PRs) are still under review - it is important to get them right, because it will be very frustrating for people trying to learn Angular running into random issues (because of a tutorial bug). Plus, this is a little more complicated than usual, because there are several repos affected (angular.js, angular-seed, angular-phonecat and even angular2 docs have a chapter that relies on this), so we need to coordinate.
That said, we are pretty close (although I am sure there will be glitches we will need to sort out later anyway 😛 )

[rleir]

Hi Georgios
In the bower.json. There are 12 versions of this, one for each tutorial step. This confused me, I wanted to do a pull but did not see how to get these versions in git. Explain it to me and I can do a pull.

Yes it is important to get it bug free! It is also important to get it up to date. Newcomers like myself trip up on the changes.
Thanks
Rick

On May 16, 2016 8:28:48 AM EDT, Georgios Kalpakas notifications@github.com wrote:

@rleir, if you can point out in what steps you see 1.4.x versions
being called, I could look into it.

This (and the related PRs) are still under review - it is important to
get them right, because it will be very frustrating for people trying
to learn Angular running into random issues (because of a tutorial
bug). Plus, this is a little more complicated than usual, because there
are several repos affected (angular.js, angular-seed, angular-phonecat
and even angular2 docs have a chapter that relies on this), so we need
to coordinate.
That said, we are pretty close (although I am sure there will be
glitches we will need to sort out later anyway 😛 )

---

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#326 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[gkalpak]

@rleir, phonecat uses an unusual setup, where each step is represented by a separate commit. This is cool when studying the tutorial - not so cool when trying to update it :(
(In a nutshell, you have to rebase and amend the X last commit.)

BTW, we just decided to drop bower in favor of npm (with a post-install script to copy the necessary files from node_modules/ into app/lib/ or something).
So, there will be one less tool to worry about.

[rleir]

Good plan. I will help by testing.

On May 16, 2016 9:50:01 AM EDT, Georgios Kalpakas notifications@github.com wrote:

@rleir, phonecat uses an unusual setup, where each step is represented
by a separate commit. This is cool when studying the tutorial - not so
cool when trying to update it :(
(In a nutshell, you have to rebase and amend the X last commit.)

BTW, we just decided to drop bower in favor of npm (with a post-install
script to copy the necessary files from node_modules/ into app/lib/
or something).
So, there will be one less tool to worry about.

---

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#326 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[gkalpak]

I ran into several bumps trying to use npm instead of bower, so we deferred that for a later time.