https://github.com/zfogg/turtlemap
A better navigation webapp for my university.
https://github.com/zfogg/turtlemap
Last synced: about 1 month ago
JSON representation
A better navigation webapp for my university.
- Host: GitHub
- URL: https://github.com/zfogg/turtlemap
- Owner: zfogg
- Created: 2013-10-12T23:49:22.000Z (over 12 years ago)
- Default Branch: master
- Last Pushed: 2020-08-12T10:44:58.000Z (almost 6 years ago)
- Last Synced: 2025-12-29T08:06:06.890Z (6 months ago)
- Language: CoffeeScript
- Size: 36.1 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Brunch with Chaplin
This is HTML5 application, built with
[Brunch](http://brunch.io) and
[Chaplin](http://chaplinjs.org).
## Installation
Clone this repo manually with Git or use `brunch new gh:paulmillr/brunch-with-chaplin`.
## Getting started
* Install [Brunch](http://brunch.io): `npm install -g brunch`.
* Install Brunch plugins and Bower components: `npm install & bower install`.
* Watch the project with continuous rebuild by
`brunch watch --server`. This will also launch HTTP server.
* `public/` dir is fully auto-generated and served by HTTP server.
* Write your code in `app` dir.
* Optionally, you can scaffold things, see readme in `generators` directory.
* For production, build minified project with `brunch build --optimize`.
See [Chaplin site](http://chaplinjs.org) for docs and more info.
---------------
# For newcomers
Brunch with Chaplin is a skeleton (boilerplate) for [Brunch](http://brunch.io)
based on [Chaplin](http://chaplinjs.org) architecture. Requires Brunch 1.7+.
Example application built with the skeleton:
[Ost.io](https://github.com/paulmillr/ostio).
This branch does not contain ready-to-use test environment.
If you want take a look how tests can be used, see `with-tests` git branch.
## Difference from Chaplin Boilerplate
[Chaplin Boilerplate](https://github.com/chaplinjs/chaplin-boilerplate)
is a official boilerplate all for chaplin. This skeleton is almost the same,
except a few changes:
* Added Header.
* CommonJS is used instead of AMD, because it's easier to use & debug.
## Features
* HTML5Boilerplate html & css are included.
* CoffeeScript + Stylus + Handlebars as app languages
(you can change this to anything you want)
* Backbone as main MVC/MVP library, Chaplin as meta-framework.
* Support of IE8 and up.
* Cross-module communication using the Mediator and Publish/Subscribe patterns
* Controllers for managing individual UI views
* Rails-style routes which map URLs to controller actions
* An application view as dispatcher and view manager
* Extended model, view and collection classes to avoid repetition and
enforce conventions
* Strict memory management and object disposal
* A collection with additional manipulation methods for smarter change events
* A collection view for easy and intelligent list rendering
## Authentication
If you build an application with authentication, there are some useful abstractions for it out there: https://github.com/chaplinjs/chaplin-auth.
## License
The MIT license.
Copyright (c) 2012 Paul Miller (http://paulmillr.com/)
Copyright (c) 2012 Moviepilot GmbH, 9elements GmbH et al.
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do
so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.