cannam@502: # Ugly Duckling
angular-cli@0: 
cannam@502: A technology demo for [Piper Audio](https://github.com/piper-audio) libraries and components using [Waves UI](https://github.com/piper-audio/waves-ui-piper) and [Angular](https://github.com/angular/).
cannam@502: 
cannam@502: See the [example deployment here](https://piper-audio.github.io/ugly-duckling).
angular-cli@0: 
angular-cli@0: ## Development server
dev@236: 
angular-cli@0: Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.
angular-cli@0: 
angular-cli@0: ## Code scaffolding
angular-cli@0: 
dev@236: Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|module`.
angular-cli@0: 
angular-cli@0: ## Build
angular-cli@0: 
angular-cli@0: Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `-prod` flag for a production build.
angular-cli@0: 
angular-cli@0: ## Running unit tests
angular-cli@0: 
angular-cli@0: Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).
angular-cli@0: 
angular-cli@0: ## Running end-to-end tests
angular-cli@0: 
angular-cli@0: Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
angular-cli@0: Before running the tests make sure you are serving the app via `ng serve`.
angular-cli@0: 
angular-cli@0: ## Further help
angular-cli@0: 
dev@236: To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).