sproutit-sproutcore 1.0.0.20090407205609 → 1.0.0.20090408130025

data/frameworks/sproutcore/frameworks/deprecated/lib/menu_views.rb

@@ -0,0 +1,93 @@
+############################################################
+# MENU VIEW HELPERS
+#
+# The view helpers defined in this file help you create popup menus.  You can
+# define a menu in your RHTML helper to be used somewhere else with code like
+# this:
+#
+
+# This is the quick way to define a menu item.  Use this approach if you just
+# want to create a menu with item names and perform an action:
+#
+# <% menu_view :action_menu, :validate=>'My.controller.validate' do |m| %>
+#   <%= m.item :item_1, 'Item 1', :action => 'doSomething' %>
+#   <%= m.separator_item %>
+#   <%= m.item :item_2, 'Item 2', :action => 'doAnother Thing' %>
+# <% end %>
+#
+require_helpers 'core_views'
+require_helpers 'button_views'
+
+# This will create a popup menu.  You should define internal outlets 
+# for the menu items.  More options to follow.
+view_helper :popup_menu_view do
+  var :tag, 'ul'
+  view 'SC.PopupMenuView'
+end
+
+# Creates a menu item view.  Normally you don't want to create these 
+# directly.  Instead use the menu_view helpers.
+#
+# OPTIONS:
+# :action =>
+#   The action to invoke when the menu item is selected.
+#
+# :label =>
+#   The label for the menu item.
+# 
+# :icon =>
+#   The icon for the menu item.  No icon will show if this is not set.
+#   
+# :shortcut =>
+#   You must pass the actualy bit of HTML you want to display as a keyboard
+#   shortcut
+#
+#   THE FOLLOWING PREVIOUS BEHAVIOR IS CURRENTLY DISABLED
+#   The shortcut key for this menu item.  Shortcuts are only active when
+#   the anchorview the popup menu is attached to is part of the in-focus
+#   pane.  Shortcuts should be named in the standard input manager
+#   syntax like this: alt_ctrl_shift_k (for Alt-Ctrl-Shift-K)
+#
+#   Note that on the web, Cmd (on the Mac) and Ctrl are equivalent. 
+#   Always use ctrl when defining shortcuts.
+# 
+# :enabled (bindable) =>
+#   Determines if the menu item will be enabled or not.  This is generally
+#   handled by your validate method or through bindings.
+# 
+# :selected (bindable) =>
+#   Determines if the menu item is selected or not.  May also be a mixed
+#   state.  This is generally handled by your validate method or through
+#   bindings.
+# 
+# :alt =>
+#   name another item in this menu that is the alternate form of the 
+#   receiver.  If the alt item is enabled, this one will be hidden and 
+#   visa versa.
+#
+view_helper :menu_item_view, :extends => :button_view do
+
+  # JavaScript
+  view 'SC.MenuItemView'
+
+  # HTML
+  var :tag, 'li'
+  var :shortcut
+  # var(:shortcut) { |sc| sc.split('_').map { |x| x.capitalize } * '-' }
+  css_class_names << 'menu-item'
+  
+  @my_href = @href || 'javascript:;'
+  @href = nil
+  @inner_html = [
+    %(<a href="#{@my_href}">),
+      '<span class="inner">',
+        @image,
+        %(<span class="label">#{@label}</span>),
+      '</span>',
+      '<span class="sel">&#x2713;</span>',
+      '<span class="mixed">-</span>',
+      %(<span class="shortcut">#{@shortcut}</span>),
+    '</a>'
+  ] * ''
+  
+end

data/frameworks/sproutcore/frameworks/deprecated/server/rails_server.js

@@ -0,0 +1,80 @@
+// ========================================================================
+// SproutCore -- JavaScript Application Framework
+// Copyright ©2006-2008, Sprout Systems, Inc. and contributors.
+// Portions copyright ©2008 Apple, Inc.  All rights reserved.
+// ========================================================================
+
+require('server/rest_server') ;
+
+/**
+  @class
+
+  This server extends SC.RestServer and leverages Rails feature to protect
+  your controller actions from CSRF attacks by using the authenticity token
+  from rails in requests from SproutCore. For more information about this
+  feature from Rails see the documentation in rails for module
+  ActionController::RequestForgeryProtection.
+
+  To use this server create it like for example:
+
+  {{{
+    Contacts = SC.Object.create({
+      server: SC.RailsServer.create({ prefix: ['Contacts'] })
+    }) ;
+  }}}
+
+  In order for SproutCore to send the authenticity token in the body of 
+  requests there is one prerequisite: you must initialize the SproutCore app 
+  by setting the following two variables:
+
+  | SC.RAILS_AUTH_TOKEN_NAME  | Should be set to the name of the authenticity token |
+  | SC.AUTH_TOKEN | Should be set to the value of the authenticity token |
+
+  Following is a description of how this can be achieved. Stick the following 
+  code in one of your controllers:
+
+  {{{
+    # Passes the authenticity token for use in javascript
+    def auth_token
+      respond_to do |wants|
+        wants.js do
+          if protect_against_forgery?
+            render :text => "var SC = SC || {};  
+              SC.RAILS_AUTH_TOKEN_NAME = '#{request_forgery_protection_token}';
+              SC.RAILS_AUTH_TOKEN = '#{form_authenticity_token}';"
+          end
+        end
+      end
+    end
+  }}}
+
+  And make it accessible via your rails routes.rb file, for example:
+
+  {{{
+    map.connect 'auth-token.js', :controller => 'application', :action => 'auth_token'
+  }}}
+
+  Lastly, add a reference to the script to the :javascript_libs property
+  in your sc-config file, for example:
+  
+  {{{
+    c[:javascript_libs] = ['/sc/auth-token.js']
+  }}}
+
+
+  @extends SC.RestServer
+  @author Lawrence Pit
+  @copyright 2006-2008, Sprout Systems, Inc. and contributors.
+  @since SproutCore 1.0
+*/
+SC.RailsServer = SC.RestServer.extend({
+
+  urlFor: function(resource, action, ids, params, method) {
+    if (method != 'get' && SC.RAILS_AUTH_TOKEN_NAME) {
+      params[SC.RAILS_AUTH_TOKEN_NAME] = SC.RAILS_AUTH_TOKEN;
+    }
+
+    return sc_super();
+  }
+
+}) ;

data/frameworks/sproutcore/frameworks/deprecated/server/rest_server.js

@@ -0,0 +1,178 @@
+// ========================================================================
+// SproutCore -- JavaScript Application Framework
+// Copyright ©2006-2008, Sprout Systems, Inc. and contributors.
+// Portions copyright ©2008 Apple, Inc.  All rights reserved.
+// ========================================================================
+
+require('server/server') ;
+
+/** 
+  @class
+  
+  Usually you wouldn't need to call any of the methods on this class or it's 
+  superclass, except for calling the +listFor+ method. The other methods are 
+  called for you when you work with your model objects. For example, calling 
+  myObject.commit(); will call the commitRecords method on this server if you 
+  had defined this server to be to the +dataSource+ of myObject.
+
+  To have an SC model reflect data on a backend server attach an instance of 
+  this class to your application. For example:
+
+  {{{
+    Contacts = SC.Object.create({
+      server: SC.RestServer.create({ prefix: ['Contacts'] })
+    }) ;
+  }}}
+
+  Then attach that server as the +dataSource+ to each model class that you 
+  want to have reflected. Also define a +resourceURL+ which defines the URL 
+  where the collection of your model can be queried. For example:
+
+  {{{
+    Contacts.Contact = SC.Record.extend(
+      dataSource: Contacts.server,
+      resourceURL: 'sc/contacts',
+      properties: ['guid','firstName','lastName'],
+      primaryKey: 'guid'
+    }) ;
+  }}}
+
+  When you work with your models, behind the scenes SC will use 5 main methods 
+  on this server. Each is listed below, together with the HTTP method used in 
+  the call to the backend server and the URL that is being called. The URL is 
+  based on the example given above.
+
+      listFor             GET    /sc/contacts
+
+      createRecords       POST   /sc/contacts
+
+      refreshRecords
+      for one record      GET    /sc/contacts/12345
+
+      refreshRecords
+      for many records    GET    /sc/contacts?ids=1,2,3,4,5,6
+
+      commitRecords
+      for one record      PUT    /sc/contacts/12345
+
+      commitRecords
+      for many records    PUT    /sc/contacts?ids=1,2,3,4,5
+
+      destroyRecords
+      for one record      DELETE /sc/contacts/12345
+
+      destroyRecords
+      for many records    DELETE /sc/contacts?ids=1,2,3,4,5
+
+  The above is the default behaviour of this server. If you want different 
+  URLs to be generated then extend this class and override the +urlFor+ 
+  method.
+
+  Another way to override the above is to tell SC where member resources can
+  be refreshed, committed and destroyed. For example, when SC calls
+  
+  {{{
+    GET /sc/contacts
+  }}}
+  
+  you could reply as follows:
+
+  {{{
+    records: [
+      {  guid: '123',
+        type: "Contact",
+        refreshURL: "/contacts?refresh=123",
+        updateURL: "/contacts/123?update=Y",
+        destroyURL: "/contacts/123",
+        firstName: "Charles",
+        ...
+      }],
+      ...
+    }
+  }}}
+
+  Then when contact 123 needs to be refreshed later on by SC, it will call:
+
+  {{{
+    GET /contacts?refresh=123
+  }}}
+
+  instead of GET /contacts/123. Note that this only works for members on your
+  resource. If a collection of contacts needed to be refreshed it would still
+  call for example GET /contacts?id=123,456,789 instead of making 3 separate
+  calls.
+
+  Because some browsers cannot actually perform an HTTP PUT or HTTP DELETE it
+  will actually perform an HTTP POST but will put an additional key,value pair
+  in the post data packet. For HTTP PUT it will add _method='put' and for
+  HTTP DELETE it will add _method='delete' in the post data.
+
+  Via the SC.Server#request method you can also call collection and member
+  functions on your resource. Use the +action+ parameter for this. For
+  example, server.request('contacts', 'archive', null, params, 'delete')
+  would call:
+
+  {{{
+    DELETE /contacts/archive
+  }}}
+
+  And server.request('contacts', 'give', [12345], {'amount': 1000}, 'put')
+  would call:
+
+  {{{
+   PUT /contacts/12345/give
+  }}}
+  
+  with post data amount=1000.
+
+  Alternatively explicitely define the URL to use by setting the +url+
+  property in the +params+ argument that is passed to the server.request 
+  method. For example:
+
+  {{{
+    Contacts.server.request(null,null,null, {url: '/sc/archive'}, 'delete')
+  }}}
+
+  would call:
+
+  {{{
+    DELETE /sc/archive
+  }}}
+
+
+  @extends SC.Server
+  @author Lawrence Pit
+  @copyright 2006-2008, Sprout Systems, Inc. and contributors.
+  @since SproutCore 1.0
+*/
+SC.RestServer = SC.Server.extend({
+
+  /**
+    @see SC.Server.urlFor
+  **/
+  urlFor: function(resource, action, ids, params, method) {
+    url = resource;
+    if (ids && ids.length == 1) url = url + '/' + ids[0];
+    if (action && action != '') url = url + '/' + action;
+    return url;
+  },
+
+
+  /* privates, overrides the values in SC.Server */
+
+  _listForAction: '',
+  _listForMethod: 'get',
+
+  _createAction: '',
+  _createMethod: 'post',
+
+  _refreshAction: '',
+  _refreshMethod: 'get',
+
+  _commitAction: '',
+  _commitMethod: 'put',
+
+  _destroyAction: '',
+  _destroyMethod: 'delete'
+
+}) ;