creating a simple cookbook application. There's also a Rapid Start if
you want a few quick how-tos. Or for an in depth example,
read Organizing a jQuery Application.
Check out the
It's an older treatment, but still touches on JMVC's strong points.
Before jumping in, there are some things you should know:
of making quality, maintainable applications in the shortest amount of time.
JMVC logically separates a basic app into following folder structure:
appname - your app files
\controllers - organized event handlers
\models - manage data
\resources - helper scripts
\test - test files
\funcunit - funcunit tests
\qunit - qunit tests
\views - html templates
documentjs - documentation engine
funcunit - testing tool
jquery - jquery and jQuery plugins (like $.Controller)
steal - compression and build
P.S. Don't worry about creating an 'appname' folder yet. We'll do that in a second.
- DocumentJS - A documentation engine
- FuncUnit - A web testing framework
- jQueryMX - jQuery MVC eXtensions.
- StealJS - A code manager : dependency management, code cleaning, building, etc.
Everything is a plugin. Just steal the ones you need.
Plugins load their own dependencies and won't load duplicate files. It looks like:
to your project.
These exceptions, although permissive licenses themselves, are not linked in your final production build.
Making a Cookbook