GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - angular-app/Samples: Sample code - chapter by chapter

BranchesTags
Open more actions menu

Latest commit

 

History

78 Commits
78 Commits

Folders and files

NameName
Last commit message
Last commit date
1820EN_01_Code
1820EN_01_Code
 
 
1820EN_02_Code
1820EN_02_Code
 
 
1820EN_03_Code
1820EN_03_Code
 
 
1820EN_04_Code
1820EN_04_Code
 
 
1820EN_05_Code
1820EN_05_Code
 
 
1820EN_06_Code
1820EN_06_Code
 
 
1820EN_07_Code
1820EN_07_Code
 
 
1820EN_08_Code
1820EN_08_Code
 
 
1820EN_09_Code
1820EN_09_Code
 
 
1820EN_10_Code
1820EN_10_Code
 
 
1820EN_11_Code
1820EN_11_Code
 
 
build
build
 
 
lib
lib
 
 
.gitignore
.gitignore
 
 
.travis.yml
.travis.yml
 
 
README.md
README.md
 
 
grunt.js
grunt.js
 
 
karma.conf.js
karma.conf.js
 
 
package.json
package.json
 
 

Repository files navigation

Book Samples

Sample code - chapter by chapter

Each chapter has its own folder, which will correspond to the zip file name for that chapter on submission. Within each chapter folder is a folder for each sample. The folder should contain enough to run the sample independent of the other samples, including tests. There is an index (i.e. 01, 02, etc.) in front of each sample so that you can see the order in which they appear in the chapter. Where the sample has a corresponding Plunk, the Plunk ID is added in brackets after the name of the sample in the folder name.

Library files

There is a common folder for libraries called lib.

Testing

There is a basic grunt file that can run all the unit tests.

You need to install the grunt CLI and testacular globally:

npm -g install grunt-cli testacular

You also need the grunt library locally (using the values in the package.json):

npm install grunt

Run grunt to check for jslint errors, generate HTML2JS templates and execute all the samples' tests.

grunt.cmd

About

Sample code - chapter by chapter

Resources

Readme
Activity
Custom properties

Stars

117 stars

Watchers

9 watching

Forks

54 forks
Report repository

Releases

Packages

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.