joosy 0.1.0.alpha → 1.0.0.RC1

data/.codoopts

@@ -0,0 +1,5 @@
+--readme	README.md
+--title		"Joosy API"
+--verbose
+--output-dir	./doc
+./app

data/.gitignore

@@ -3,3 +3,5 @@
 log/*.log
 pkg/
 tmp/
+.DS_Store
+doc/

data/Gemfile

@@ -1,4 +1,17 @@
 source "http://rubygems.org"
 
-# Specify your gem's dependencies in joosy-rails.gemspec
-gemspec
+# Specify your gem's dependencies in joosy.gemspec
+gemspec
+
+group :development do
+  gem 'jasmine',         :git => 'git://github.com/pivotal/jasmine-gem.git'
+  gem 'guard-sprockets', :git => 'git://github.com/roundlake/guard-sprockets.git'
+  gem 'thin'
+end
+
+group :test do
+  if RUBY_PLATFORM =~ /linux/
+    gem 'rb-inotify'
+    gem 'libnotify'
+  end
+end

data/Gemfile.lock

@@ -1,110 +1,127 @@
+GIT
+  remote: git://github.com/pivotal/jasmine-gem.git
+  revision: c72e8d248d49a1ebe53f31a09ac511194ad4edf1
+  specs:
+    jasmine (1.2.0.rc3)
+      jasmine-core (>= 1.2.0.rc3)
+      rack (~> 1.0)
+      rspec (>= 1.3.1)
+      selenium-webdriver (>= 0.1.3)
+
+GIT
+  remote: git://github.com/roundlake/guard-sprockets.git
+  revision: 77365fbf48b2af0c93a42fcb05747c174b90d8d7
+  specs:
+    guard-sprockets (0.3.1)
+      guard (~> 1.0.0)
+      sprockets (~> 2.0)
+
 PATH
   remote: .
   specs:
-    joosy-rails (0.1.0)
+    joosy (0.1.0.RC3)
       coffee-rails
+      haml_coffee_assets
+      i18n-js
       jquery-rails
-      rails (>= 3.0.0)
+      rails (>= 3.1.0)
 
 GEM
   remote: http://rubygems.org/
   specs:
-    actionmailer (3.1.3)
-      actionpack (= 3.1.3)
-      mail (~> 2.3.0)
-    actionpack (3.1.3)
-      activemodel (= 3.1.3)
-      activesupport (= 3.1.3)
+    actionmailer (3.2.3)
+      actionpack (= 3.2.3)
+      mail (~> 2.4.4)
+    actionpack (3.2.3)
+      activemodel (= 3.2.3)
+      activesupport (= 3.2.3)
       builder (~> 3.0.0)
       erubis (~> 2.7.0)
-      i18n (~> 0.6)
-      rack (~> 1.3.5)
-      rack-cache (~> 1.1)
-      rack-mount (~> 0.8.2)
+      journey (~> 1.0.1)
+      rack (~> 1.4.0)
+      rack-cache (~> 1.2)
       rack-test (~> 0.6.1)
-      sprockets (~> 2.0.3)
-    activemodel (3.1.3)
-      activesupport (= 3.1.3)
+      sprockets (~> 2.1.2)
+    activemodel (3.2.3)
+      activesupport (= 3.2.3)
       builder (~> 3.0.0)
-      i18n (~> 0.6)
-    activerecord (3.1.3)
-      activemodel (= 3.1.3)
-      activesupport (= 3.1.3)
-      arel (~> 2.2.1)
+    activerecord (3.2.3)
+      activemodel (= 3.2.3)
+      activesupport (= 3.2.3)
+      arel (~> 3.0.2)
       tzinfo (~> 0.3.29)
-    activeresource (3.1.3)
-      activemodel (= 3.1.3)
-      activesupport (= 3.1.3)
-    activesupport (3.1.3)
+    activeresource (3.2.3)
+      activemodel (= 3.2.3)
+      activesupport (= 3.2.3)
+    activesupport (3.2.3)
+      i18n (~> 0.6)
       multi_json (~> 1.0)
-    arel (2.2.1)
+    arel (3.0.2)
     builder (3.0.0)
-    childprocess (0.3.0)
+    childprocess (0.3.1)
       ffi (~> 1.0.6)
-    coffee-rails (3.1.1)
+    coffee-rails (3.2.2)
       coffee-script (>= 2.2.0)
-      railties (~> 3.1.0)
+      railties (~> 3.2.0)
     coffee-script (2.2.0)
       coffee-script-source
       execjs
     coffee-script-source (1.2.0)
+    daemons (1.1.8)
     diff-lcs (1.1.3)
     erubis (2.7.0)
-    execjs (1.2.13)
+    eventmachine (0.12.10)
+    eventmachine (0.12.10-java)
+    execjs (1.3.0)
       multi_json (~> 1.0)
     ffi (1.0.11)
     ffi (1.0.11-java)
-    guard (0.10.0)
+    guard (1.0.1)
       ffi (>= 0.5.0)
       thor (~> 0.14.6)
-    guard-coffeescript (0.5.4)
+    guard-coffeescript (0.5.7)
       coffee-script (>= 2.2.0)
       guard (>= 0.8.3)
-    guard-shell (0.2.0)
-      guard (>= 0.2.0)
-    guard-sprockets (0.2.0)
-      guard (>= 0.2.2)
-      sprockets (~> 2)
+    haml_coffee_assets (0.8.5)
+      execjs (>= 1.2.9)
+      sprockets (>= 2.0.3)
+      tilt (>= 1.3.3)
     hike (1.2.1)
     i18n (0.6.0)
-    jasmine (1.1.2)
-      jasmine-core (>= 1.1.0)
-      rack (>= 1.1)
-      rspec (>= 1.3.1)
-      selenium-webdriver (>= 0.1.3)
-    jasmine-core (1.1.0)
-    jquery-rails (1.0.19)
-      railties (~> 3.0)
+    i18n-js (2.1.2)
+      i18n
+    jasmine-core (1.2.0.rc3)
+    journey (1.0.3)
+    jquery-rails (2.0.2)
+      railties (>= 3.2.0, < 5.0)
       thor (~> 0.14)
-    json (1.6.4)
-    json (1.6.4-java)
-    mail (2.3.0)
+    json (1.6.6)
+    json (1.6.6-java)
+    mail (2.4.4)
       i18n (>= 0.4.0)
       mime-types (~> 1.16)
       treetop (~> 1.4.8)
-    mime-types (1.17.2)
-    multi_json (1.0.4)
+    mime-types (1.18)
+    multi_json (1.2.0)
     polyglot (0.3.3)
-    rack (1.3.6)
-    rack-cache (1.1)
+    rack (1.4.1)
+    rack-cache (1.2)
       rack (>= 0.4)
-    rack-mount (0.8.3)
-      rack (>= 1.0.0)
     rack-ssl (1.3.2)
       rack
     rack-test (0.6.1)
       rack (>= 1.0)
-    rails (3.1.3)
-      actionmailer (= 3.1.3)
-      actionpack (= 3.1.3)
-      activerecord (= 3.1.3)
-      activeresource (= 3.1.3)
-      activesupport (= 3.1.3)
+    rails (3.2.3)
+      actionmailer (= 3.2.3)
+      actionpack (= 3.2.3)
+      activerecord (= 3.2.3)
+      activeresource (= 3.2.3)
+      activesupport (= 3.2.3)
       bundler (~> 1.0)
-      railties (= 3.1.3)
-    railties (3.1.3)
-      actionpack (= 3.1.3)
-      activesupport (= 3.1.3)
+      railties (= 3.2.3)
+    railties (3.2.3)
+      actionpack (= 3.2.3)
+      activesupport (= 3.2.3)
       rack-ssl (~> 1.3.2)
       rake (>= 0.8.7)
       rdoc (~> 3.4)
@@ -112,30 +129,34 @@ GEM
     rake (0.9.2.2)
     rdoc (3.12)
       json (~> 1.4)
-    rspec (2.8.0)
-      rspec-core (~> 2.8.0)
-      rspec-expectations (~> 2.8.0)
-      rspec-mocks (~> 2.8.0)
-    rspec-core (2.8.0)
-    rspec-expectations (2.8.0)
-      diff-lcs (~> 1.1.2)
-    rspec-mocks (2.8.0)
-    rubyzip (0.9.5)
-    selenium-webdriver (2.17.0)
+    rspec (2.9.0)
+      rspec-core (~> 2.9.0)
+      rspec-expectations (~> 2.9.0)
+      rspec-mocks (~> 2.9.0)
+    rspec-core (2.9.0)
+    rspec-expectations (2.9.1)
+      diff-lcs (~> 1.1.3)
+    rspec-mocks (2.9.0)
+    rubyzip (0.9.6.1)
+    selenium-webdriver (2.20.0)
       childprocess (>= 0.2.5)
-      ffi (~> 1.0.9)
-      multi_json (~> 1.0.4)
+      ffi (~> 1.0)
+      multi_json (~> 1.0)
       rubyzip
-    sprockets (2.0.3)
+    sprockets (2.1.2)
       hike (~> 1.2)
       rack (~> 1.0)
       tilt (~> 1.1, != 1.3.0)
+    thin (1.3.1)
+      daemons (>= 1.0.9)
+      eventmachine (>= 0.12.6)
+      rack (>= 1.0.0)
     thor (0.14.6)
     tilt (1.3.3)
     treetop (1.4.10)
       polyglot
       polyglot (>= 0.3.1)
-    tzinfo (0.3.31)
+    tzinfo (0.3.33)
 
 PLATFORMS
   java
@@ -144,7 +165,7 @@ PLATFORMS
 DEPENDENCIES
   guard
   guard-coffeescript
-  guard-shell
-  guard-sprockets
-  jasmine
-  joosy-rails!
+  guard-sprockets!
+  jasmine!
+  joosy!
+  thin

data/Guardfile

@@ -1,24 +1,24 @@
-guard 'coffeescript',
-  :output => 'tmp/spec/javascripts' do
-    watch(%r{^spec/javascripts/(.+)[sS]pec\.js\.coffee$})
+require 'coffee_script'
+
+guard 'coffeescript', :output => 'tmp/spec/javascripts', :all_on_start => true do
+  watch(%r{^spec/javascripts/(.+)[sS]pec\.js\.coffee$})
 end
 
-guard 'coffeescript',
-  :output => 'tmp/spec/javascripts/helpers' do
-    watch(%r{^spec/javascripts/helpers/(.+)\.js\.coffee$})
+guard 'coffeescript', :output => 'tmp/spec/javascripts/helpers', :all_on_start => true do
+  watch(%r{^spec/javascripts/helpers/(.+)\.js\.coffee$})
 end
 
 jquery_path = File.join(Gem.loaded_specs['jquery-rails'].full_gem_path, 'vendor/assets/javascripts')
-guard 'sprockets',
-  :destination => 'tmp/javascripts',
-  :asset_paths => ['vendor/assets/javascripts', jquery_path] do
-    watch('vendor/assets/javascripts/joosy.js.coffee')
-end
 
-guard 'shell' do
-  watch(%r{^vendor/assets/javascripts/(?!joosy\.js).+\.js}) do
-    `touch vendor/assets/javascripts/joosy.js.coffee`
-  end
+guard 'sprockets', :destination => 'tmp/javascripts',
+  :asset_paths => ['app/assets/javascripts', 'vendor/assets/javascripts', jquery_path],
+  :root_file => [
+    'app/assets/javascripts/joosy.js.coffee',
+    'app/assets/javascripts/joosy/preloaders/caching.js.coffee',
+    'app/assets/javascripts/joosy/preloaders/inline.js.coffee'
+  ] do
+  watch %r{^app/assets/javascripts/joosy/core.+\.js}
+  watch 'app/assets/javascripts/joosy.js.coffee'
 end
 
-puts 'HI! Hit <Enter> to generate all stuff.'
+puts 'HI! Hit <Enter> to generate all stuff.'

data/LICENSE

@@ -0,0 +1,22 @@
+The MIT License
+
+Copyright (c) 2012 Round Lake, inc.,
+                   Peter Zotov <whitequark@whitequark.org>.
+
+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.

data/MIT-LICENSE

@@ -1,5 +1,5 @@
-Copyright (C) 2011 by Boris Staal <boris@roundlake.ru>,
-                      Peter Zotov <p.zotov@roundlake.ru>.
+Copyright (C) 2011, 2012 by Boris Staal <boris@roundlake.ru>,
+                            Peter Zotov <p.zotov@roundlake.ru>.
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

data/README.md

@@ -0,0 +1,118 @@
+![Joosy](http://f.cl.ly/items/2N2J453J2B353F1A0t0I/joocy1.1.png)
+
+## What is Joosy
+
+Joosy is a full-featured javascript MVC framework, which mostly follows Rails philosophy, particularly in preferring conventions over configuration. It helps you to avoid boilerplate and makes it easy to maintain and extend the app.
+
+Joosy allows you to create web apps which work completely in the browser. So that, it helps you to relocate all your Rails Views to the client side. It also helps you with managing the growing quantity of JS code. On another hand, it makes your backend to have exactly one function --  to be a simple REST provider. That leads to easier development support and improves the scalability greatly.
+
+Joosy doesn't compete with jQuery. It is built on the top of [jQuery](http://jquery.com/), and utilizes [CoffeeScript](http://coffeescript.org/). It either includes [Sugar.js](http://sugarjs.com/) in role of ActiveSupport to make your life even better.
+
+Finally, Joosy boosts your development drastically.
+
+### How is Joosy different from X
+
+We share quite different goals and totally differ in ways to achieve it. While existing MVC frameworks define basic entities for you and leave you alone with application basic patterns and solutions, Joosy tries to give convention for each of them.
+
+#### [Backbone](http://documentcloud.github.com/backbone/)
+
+In Backbone or Spine you only have abstract Views, Models and "Packs of …" and you should even decide on your own what's Controller for you. Joosy gives you the ready plan on how to move on to the success. If you ever used Rails you know that feeling: you concentrate on _what_ you create and not on _how_ to structure it.
+
+#### [Ember](http://emberjs.com/)
+
+Ember is the closest framework by spirit. But it still doesn't give you enough conventions and is even more abstract than Backbone in several parts. It either limits you to Handlebars. Joosy rendering system is built on top of same solution, Morpher. That said you can bind your variables dynamically just like in Ember. But it allows you to any templates syntax.
+
+### The Joosy MVC Interpretation
+
+You probably are familiar with the concept of MVC. It's a pattern to keep code DRY, isolate business logic from the UI. However the concept of Model-View-Controller just doesn't work for browser applications. There are numerous reasons for that that can't be fit into this introduction. Instead we'll tell you what we propose.
+
+#### Views
+
+In Joosy views are just views. Set of files (in templates/ folder). They do not differ from Rails and give you quite the same abilities (including helpers!). Besides that Joosy has renderDynamic which allows you to bind your variables to HTML representation tightly. You change variable value, Joosy changes HTML.
+
+By default Joosy comes with Coffee-Haml (which looks and works pretty much like Ruby Haml). Combined with Sugar.js it will feel very similar to Ruby and server-side and will provide you the easiest migration.
+
+#### Controllers
+
+Unlike server-side, client-side has a state. At server-side you only have incoming data and you convert it to output data. At client-side you work with events. To handle correct bootstrap and help you organize your code well, we have 3 entities which play the role of controller. Their organizing functions are similar but they behavior dramatically different at bootstrap.
+
+They are:
+
+###### Pages
+Pages are the heart of the entire application. They are used to fetch data, bind events, setup widgets, trig visual effects, and pass the data to the templates.
+
+###### Layouts 
+Layouts are mainly used to set a part of your page that won't be reloaded often. Pages are wrapped into Layouts. Just like pages Layouts can bind events and setup widgets. Consider layouts as a bit extended version of what you have in Rails.
+
+###### Widgets 
+Widgets are needed to keep your code DRY. They help you organize it in reusable modules.
+
+#### Models
+
+There are some facts that should be noted to explain it how we understand browser-side models.
+
+* In most cases you will want to leave your logic on server-side. In a real models. 
+* You rarely want to make 5 HTTP requests instead of 1.
+* In most cases you will have to give user a Form as a way to change anything.
+* You'll get different possible set of fields depending on case you use your model at.
+
+With all that in mind we came up to the fact: you can not reproduce real models in browser nor you should try to. What you need is a comfortable channel between browser and server-side to get structured data, work with that and send it back. That's mainly a transport and interface task while models are MUCH more than that. To solve this task Joosy offers you two things:
+
+###### Resources
+Resource is wrapper on top of JSON dump which will help you to get data from server, parse it and structure it. It will trigger 'changed' if you change resource, will map inline hashes in other resources if possible and do all other magic stuff you expect from your model when you read data. Resources either define Collections. In most cases you can say Resources are fully-functional read part of what you get used to as model.
+
+###### Forms
+After you got your data as resources and used it to display something, you'll need to change it. While resource defines modification methods like _save_ and _destroy_ most of complex modifications should go through Joosy.Form. It turns your form into AJAX and binds the resource to it. It handles file uploads, it gives you upload progress callback and makes it a dream to handle. Joosy.Form will either understand standard Rails invalidation response and will mark invalidated fields with ".field_with_errors" out of box.
+
+
+## What is Joosy good for
+
+Joosy is intended to ease building of modern medium and large-sized browser-based applications, minimize code base while providing more features and what's most important, giving you ready conventions for typical tasks.
+
+Compare Joosy to Backbone like Rails to Sinatra. While Rails engine is much more powerful, Sinatra still has a lot of cases to be used at. If all you need is to enable some RICHness on one of your pages, Joosy can handle that. But Backbone will do the trick with lesser dependencies. If you need to move complete web-resource to browser Joosy will do the task at its Best.
+
+## What's next?
+
+We have a set of guidelines showing you, step-by-step, how to create a Joosy application. Follow them at our [Guides site](http://guides.joosy.ws/).
+
+### Hello world app
+
+Add Joosy gem to your Gemfile:
+
+    gem 'joosy'
+
+Using built-in generators you can quickly generate small app inside your Rails app to see Joosy application from inside a bit.
+
+    rails g joosy:application dummy
+    rails g joosy:preloader dummy
+
+Now you can `rails s` and see Joosy placeholder at [localhost:3000/dummy](http://localhost:3000/dummy)
+
+Generated application will consist of one `Layout` and one `Page` both including very basic practices of Joosy.
+
+# Hacking
+
+Don't forget to run tests!
+
+```ruby
+bundle install
+rake guard
+rake jasmine
+```
+
+http://localhost:8888/ <- they are here :)
+
+Credits
+-------
+
+<img src="http://roundlake.ru/assets/logo.png" align="right" />
+
+* Boris Staal ([@_inossidabile](http://twitter.com/#!/_inossidabile))
+* Andrew Shaydurov
+* Alexander Pavlenko ([@alerticus](http://twitter.com/#!/alerticus))
+* Peter Zotov ([@whitequark](http://twitter.com/#!/whitequark))
+
+LICENSE
+-------
+
+It is free software, and may be redistributed under the terms of MIT license.

data/app/assets/javascripts/joosy/core/application.js.coffee

@@ -0,0 +1,53 @@
+#= require joosy/core/joosy
+
+#
+# Joosy Application container
+#
+# @mixin
+#
+Joosy.Application =
+  Pages: {}
+  Layouts: {}
+  Controls: {}
+  
+  loading: true
+  identity: true
+
+  #
+  # Starts Joosy application by binding to element and bootstraping routes
+  #
+  # @param [String] name        Name of app (the dir its located in)
+  # @param [String] selector    jQuery-compatible selector of root application element
+  # @param [Object] options
+  #
+  initialize: (@name, @selector, options={}) ->
+    @[key] = value for key, value of options
+    @templater = new Joosy.Templaters.RailsJST @name
+
+    Joosy.Router.__setupRoutes()
+
+    @sandboxSelector = Joosy.uuid()
+    @content().after "<div id='#{@sandboxSelector}' style='display:none'></div>"
+    @sandboxSelector = '#' + @sandboxSelector
+
+  #
+  # Gets current application root node
+  #
+  content: ->
+    $(@selector)
+
+  #
+  # Gets current application sandbox node
+  #
+  sandbox: ->
+    $(@sandboxSelector)
+
+  #
+  # Switches to given page
+  #
+  # @param [Joosy.Page] page      The class (not object) of page to load
+  # @param [Object] params        Hash of page params
+  #
+  setCurrentPage: (page, params) ->
+    #if @page not instanceof page
+    @page = new page params, @page