rhoconnect 3.0.0.beta1

data/doc/contributing.txt

@@ -0,0 +1,60 @@
+Contributing to RhoConnect
+===
+Want to add features to RhoConnect?  Found a bug that you want report or fix?  Please follow the steps below to help with the RhoConnect project.  Thanks to developers like you, RhoConnect continues to be the best and fastest open-source mobile sync server!
+
+## Report RhoConnect Issues
+Please first report bugs/features/enhancements to the [google group](http://groups.google.com/group/rhomobile).  Someone may already be working on the issue!
+
+## Run RhoConnect Specs
+First run the rhoconnect specs to make sure your environment is up-to-date for development:
+
+1. [Fork](http://help.github.com/forking/) the [RhoConnect repository](http://github.com/rhomobile/rhoconnect).
+
+2. Clone your new repo: 
+		
+		$ git clone git://github.com/<yourhandle>/rhoconnect.git
+		$ cd rhoconnect
+
+3. Install [Bundler](http://gembundler.com/):
+		
+		$ [sudo] gem install bundler
+
+4. Install all of the required gems. If any of the needed gems are already installed, Bundler will use them:
+		
+		$ [sudo] bundle install
+
+5. Install [hsqldata](http://github.com/rhomobile/hsqldata):
+		
+		$ git clone git://github.com/rhomobile/hsqldata.git
+		$ cd hsqldata
+		$ ant
+		$ mkdir -p <path-to-rhoconnect>/vendor/
+		$ cp bin/hsqldata.jar <path-to-rhoconnect>/vendor/
+
+6. Run the RhoConnect specs:
+
+ 		$ rake   #=> runs all rhoconnect specs by default
+
+
+If everything passes (pending specs are OK), then your environment is ready for development.  If you have trouble installing a particular gem or the specs just won't run properly, please feel free to ping the [rhomobile google group](mailto:rhomobile@googlegroups.com) or [hop on IRC](http://webchat.freenode.net/?channels=rhomobile) to chat with other RhoConnect developers.
+
+## Contributing your Patch
+Now that you're environment is ready, make your changes!
+
+1. Create a topic branch:
+		
+		$ git checkout -b cool_new_feature
+
+2. Write tests ([example](http://github.com/rhomobile/rhoconnect/commit/f95cfdbf3f53d64c3957499906c77d7127b7c3db#diff-2))
+
+3. Make changes...
+
+4. Add relevant documentation(RDoc, update the README if relevant)
+
+5. Push to your branch:
+		
+		$ git push origin cool_new_feature
+
+6. Send a note to the [google group](http://groups.google.com/group/rhomobile)
+
+That's it!  Please follow [these ruby style guidelines](http://github.com/chneukirchen/styleguide/blob/master/RUBY-STYLE) when coding.

data/doc/deploying.txt

@@ -0,0 +1,82 @@
+Deploying a RhoConnect Application
+===
+
+Since RhoConnect applications are standard ruby [sinatra](http://www.sinatrarb.com/) applications, you have many hosting options.  This section will cover two ways to deploy a RhoConnect application: use the RhoHub service, deploy to an on-premise server.
+
+## Preparing App for Production
+By default your RhoConnect application generates a few files that you should be familiar with and understand the settings.
+
+### `config.ru`
+This rackup file contains runtime configuration for the RhoConnect sinatra application:
+	
+	:::ruby
+	Rhoconnect::Server.disable :run
+	Rhoconnect::Server.disable :clean_trace
+	Rhoconnect::Server.enable  :raise_errors
+	Rhoconnect::Server.set     :secret,      '<changeme>'
+	Rhoconnect::Server.set     :root,        ROOT_PATH
+	Rhoconnect::Server.use     Rack::Static, :urls => ["/data"], :root => Rhoconnect::Server.root
+	
+The important setting here `:secret` you will want to change.  `:secret` should be set to a long random string, it ___should not___ be set to a dictionary word or short string (30 characters or more is sufficient).  This is used for the session storage using a digest algorithm as described [here](http://guides.rubyonrails.org/security.html#session-storage).
+
+If you don't change the `:secret` setting, RhoConnect automatically warns you each time the application starts:
+
+ 	[11:34:56 AM 2011-01-12] ************************************************************
+
+	[11:34:56 AM 2011-01-12] WARNING: Change the session secret in config.ru from <changeme> to something secure.
+	[11:34:56 AM 2011-01-12]   i.e. running `rake rhoconnect:secret` in your app will generate a secret you could use.
+
+	[11:34:56 AM 2011-01-12] ************************************************************
+	
+
+As this warning states, a good way to generate a cryptographically secure secret is by running `rake rhoconnect:secret` in your RhoConnect  application.
+
+	:::term
+	$ cd storemanager-server
+	$ rake rhoconnect:secret
+	040a2355475e9d0fb591ef78d5b9ca61a34cbcfd3f11942b18bc1d91f1ca66c27b2e0386333843a7efa29f40fff03624cd908d0883364ffbfa3208ab23fa2664
+	
+Then plug this secret into your `config.ru`:
+
+	:::ruby
+	Rhoconnect::Server.set     :secret, '040a2355475e9d0fb591ef78d5b9ca61a34cbcfd3f11942b18bc1d91f1ca66c27b2e0386333843a7efa29f40fff03624cd908d0883364ffbfa3208ab23fa2664'
+
+To run RhoConnect in production mode, use `RACK_ENV` environment variable set to "production".  This ensures RhoConnect will use the `:production` section of the settings.  For example:
+
+	:::term
+	$ thin start -e production -p 9292
+
+Will start thin in with `RACK_ENV` set to "production".  
+
+NOTE: If you deploy using passenger or on RhoHub, this variable is automatically set to production.
+
+### `settings/settings.yml`
+This file contains all source adapter options and settings like the redis server connection.  Before deploying to production, make sure you have the appropriate production settings:
+
+	:::yaml
+	:sources: 
+	  Product: 
+	    :poll_interval: 300
+
+	:production: 
+	  :redis: myredishost:6379
+	  :licensefile: settings/license.key
+	  :syncserver: http://localhost:9292/application/
+
+### `settings/license.key`
+This contains your RhoConnect license key text.  By default, a RhoConnect application comes with a 10 device license.  Please see the [licensing page](/rhoconnect/licensing) for more details.
+
+## Hosting on RhoHub
+The [RhoHub](/rhohub/introduction) service offers several [production RhoConnect application hosting levels](http://rhohub.com/pricing).  Simply sign up on [rhohub.com](http://rhohub.com/) and go through the [tutorial](/rhohub/tutorial) on deploying your first RhoConnect application with RhoHub.
+
+## Deploying On-Premise
+The [sinatra book](http://sinatra-book.gittr.com/) has some great [deployment documentation](http://sinatra-book.gittr.com/#deployment) that you should review before running your RhoConnect application in production.
+
+## Deploying into J2EE environment
+In JRuby environment, there is an option to create the WAR container for the Rhoconnect app
+and deploy it into the J2EE App Server.
+(see the corresponding 'rake' task for creating the WAR containers).
+Deploying the WAR container varies per J2EE App Server, for JBoss it is necessary
+to place the WAR file into the server's deploy directory.
+
+We recommend using the [phusion passenger](http://modrails.com/index.html) stack for deploying an on-premise RhoConnect application.  Please refer to the [section on rack applications](http://modrails.com/documentation/Users%20guide%20Apache.html#_deploying_a_rack_based_ruby_application) for information on deploying a RhoConnect sinatra application.

data/doc/install.txt

@@ -0,0 +1,28 @@
+Installing RhoConnect
+===
+
+## Windows
+
+If you're running Windows, download the latest [RhoConnect windows installer](http://github.com/rhomobile/rhoconnect/downloads).  This installs the [Ruby stack](http://www.ruby-lang.org/en/), [Redis](http://redis.io/), [Apache](http://httpd.apache.org/), and a default RhoConnect application so you don't need to generate one by hand.
+
+Your RhoConnect application folder will be located in C:\RhoConnect\rhoconnect by default so you can skip to the [generating a source instructions](/rhoconnect/command-line#rhoconnect-generator) in the next section.
+
+## Mac OS / Linux
+
+### Prerequisites
+
+1. [Ruby v1.8.7+](http://www.ruby-lang.org/en/downloads/)
+
+2. [RubyGems v1.3.7+](http://rubygems.org/pages/download) 
+
+3. Ruby Web Server - We test with [thin](http://code.macournoyer.com/thin/), and [passenger](http://www.modrails.com/).  WEBrick, the web server that ships with ruby, is known to cause issues with HTTP headers/cookies and is ***not*** recommended.
+
+4. [Redis 2.2.x](http://redis.io/) - RhoConnect includes a simple [rake task](/rhoconnect/command-line#rake-tasks) `redis:install` to install redis, covered in the next section.  Alternatively, you can [install redis directly](http://redis.io/download).
+
+### Installing RhoConnect Gem
+
+To install the RhoConnect gem, run:
+
+	:::term
+  	$ [sudo] gem install rhoconnect --pre
+ 

data/doc/introduction.txt

@@ -0,0 +1,20 @@
+RhoConnect Introduction
+===
+
+RhoConnect is the first of a new category of “mobile app integration” servers. Using RhoConnect drastically simplifies the development of connectivity to an enterprise backend app. The RhoConnect server and built-in RhoConnect client in the smartphone app perform all the work to get data down to the device. This eliminates 50 to 80 percent of the development effort in enterprise smartphone apps: performing the backend application integration.
+
+RhoConnect also does the ongoing synchronization work: keeping all of the data from backend applications current on the local device.   As information is changed in backend applications it is immediately synchronized down to all devices, and available on devices even when they are offline.  Data changed on the devices is also synchronized by RhoConnect to the backend system.
+
+RhoConnect does not require use of Rhodes for the client app.  It can also be used from apps written in Objective C or even from other frameworks using JavaScript.
+
+RhoConnect consists of the following components:
+
+* Synchronization Framework - The core of RhoConnect, this facilitates data synchronization between the Rhodes / RhoConnect-Client and a 3rd party source (SOAP, REST, etc...). Each source is synchronized by implementing a simple "source adapter" class. The client connects with the embedded [sinatra](http://www.sinatrarb.com/) server to interact with the collection of source adapters.  RhoConnect uses [redis](http://redis.io/) to efficiently cache data to be synchronized.
+
+* REST API - RhoConnect exposes a simple REST API for interacting with an application.  See the [REST API docs](/rhoconnect/rest-api) for more information.
+
+* Administration Web Console - The RhoConnect [web console](/rhoconnect/web-console) is sinatra server used for manipulating and peeking into a running RhoConnect app. The console uses the [RhoConnect REST API](/rhoconnect/rest-api) for everything it does.
+
+* Asynchronous Job System - RhoConnect uses the [resque](https://github.com/defunkt/resque) library to provide asynchronous execution of various tasks it needs to perform. These tasks include source adapter execution, sending push messages, preparing bulk data, etc... Resque is dead-simple to use and highly extensible, so it can easily be used for other functionality not described here.
+
+The bulk of the work involved in making RhoConnect work with your smartphone application is writing source adapters. This process is described in the [source adapter section](/rhoconnect/source-adapters). A longer [tutorial](/rhoconnect/tutorial) is also available.

data/doc/licensing.txt

@@ -0,0 +1,18 @@
+Licensing Your RhoConnect Application
+===
+
+## RhoHub License
+If you plan to deploy your RhoConnect application on RhoHub under a premium or enterprise plan, just click on the **"Production app?"** button to enable your paid-level license.
+
+**NOTE: Toggling this button will re-deploy your RhoConnect application to a new redis database.  Make sure you __backup all critical data__ before doing this!**
+
+## On-Premise License
+Your RhoConnect application was generated with a default license which supports up to 10 devices.  After [purchasing](http://rhomobile.com/products/rhoconnect/) a license, you can save the new license text in settings/license.key.  Just restart the application and it will pick up the new license automatically.  
+
+If you want to load the license file in a different location, you can edit `:licensefile:` in settings/settings.yml:
+
+	:::yaml
+    :development:
+      :licensefile: settings/license.key
+      :redis: localhost:6379
+      :syncserver: http://localhost:9292/application/

data/doc/metadata.txt

@@ -0,0 +1,458 @@
+Building Dynamic Views with Metadata
+===
+
+The metadata framework is a RhoConnect & Rhodes tool which provides synchronized application layouts.  For example, if your application had an "account" model with the fields "name" and "address", metadata would allow you to add an additional field "phone" in the source adapter and this new field would automatically display in the Rhodes application.  
+
+In addition to adding/removing/updating fields, metadata also provides powerful features like handling field validations, data-binding, collections, repeatable elements, and much more.
+
+## How Metadata Works
+* Metadata is first defined in a [source adapter](/rhoconnect/source-adapters) by implementing an adapter method `metadata` that returns a JSON structure. The JSON structure may contain a hash of hashes, as well as having child elements defined as arrays of hashes. The keys in each object can be any string, however there are some reserved labels and labels used by certain elements. 
+
+* The metadata for an adapter is synchronized to Rhodes along with the rest of the adapter dataset.  Metadata is called before the query method in the [`SyncEngine` workflow](/rhodes/synchronization#syncengine-workflow), so you can tailor your query method based on metadata.
+
+* Rhodes uses the synchronized [metadata definition](#metadata-definition) to render views at runtime.  These views are driven by the metadata definition, so when a new definition is synchronized, the views will automatically reflect the changes.
+
+## Getting Started with Metadata
+The first step is to install the rhodes-translator gem:
+
+	:::term
+  	$ gem install rhodes-translator
+
+Then add `rhodes_translator` to your extensions in your Rhodes application's `build.yml`:
+
+	:::yaml
+  	extensions: ["rhodes_translator"]
+
+Now define some metadata and add this to a `metadata` method your [source adapter](/rhoconnect/source-adapters).  For example:
+
+	:::ruby
+	def metadata
+	  # define the metadata
+	  row1 = { 
+	    :label => 'Address 1',
+	    :value => '123 fake street',
+	    :name => 'address1',
+	    :type => 'labeledrow' 
+	  }
+	  table = { 
+	    :label => 'Table',
+	    :type => 'table',
+	    :children => [ row1, row1, row1 ] 
+	  }
+	  view = { 
+	    :title => 'UI meta panel',
+	    :type => 'iuipanel',
+	    :children => [table] 
+ 	  }
+
+ 	  # return the definition as JSON
+	  {'index' => view}.to_json
+    end
+	
+	
+## Metadata Definition
+The following elements are available for building metadata definitions.
+
+### Reserved Labels
+
+The following labels are reserved, used by the metadata framework.
+
+* `:type`
+* `:children`
+* `:repeatable`
+* `:validation`
+
+### Children
+
+Children of an element are defined by an array of hashes. To specify the children of an element you add the ":children" key and specify the children of that element.
+
+The following example shows a table element that has three `row1` elements as `:children`:
+
+	:::ruby
+	row1 = { 
+	  :label => 'Address 1',
+	  :value => '123 fake street',
+	  :name => 'address1',
+	  :type => 'labeledrow' 
+	}
+	
+	table = { 
+	  :label => 'Table',
+	  :type => 'table',
+	  :children => [ row1, row1, row1 ] 
+	}
+
+### Repeatable
+
+Repeatable elements use [data binding](#data-binding) to specify an array of objects to iterate over. The children of the repeatable element are duplicated for each element in the object referred to by the repeatable hash key. For more information on data-binding  see the data binding section on this page.
+
+The following example will result in a table with 2 child rows, one row with the value set to '123 fake street' and the second row value set to '321 fake street'
+
+	:::ruby
+	@addresses = [ 
+	  { :name => "123 fake street" }, 
+	  { :name => "321 fake street" } 
+	]
+
+	row1 = { 
+	  :label => 'Address 1',
+	  :value => '{{name}}',
+	  :name => 'address1',
+	  :type => 'labeledrow' 
+	}
+
+	table = { 
+	  :label => 'Table',
+	  :type => 'table',
+	  :children => [ row1 ],
+	  :repeatable => '{{@addresses}}' 
+	}
+
+
+## Controlling How Metadata is Rendered
+
+By default, any controller actions that have metadata for a given model with the key corresponding to the action will be rendered with metadata instead of the view.
+
+However, you can render arbitrary metadata in the view with the `render_metadata` method. You must specify the action to the metadata. By default, the metadata provided is pulled from the model, however this can be overridden as well. 
+
+Example:
+
+	:::ruby
+ 	<%= render_metadata('indexdata') %>
+
+
+Or, using explicit metadata resource:
+
+	:::ruby
+ 	<%= render_metadata('index', Account.metadata) %>
+
+## Data Binding
+
+Data binding happens before the elements get translated to html. All of the instance variables in your method are able to be referenced by the data binding keys.
+
+A data binding key is always contained within a string. It is indicated by using double bracket enclosure: `{{databinding path here}}`
+
+To reference hash keys, or index arrays, the `/` operator is used.  You must specify the whole path to the object, the only exception being within [repeatable](#metadata-definition) elements.
+
+We will use the following dataset for example:
+
+	:::ruby
+ 	@data = { 
+	  :key1 => [ 'array', 'with', 'elements'], 
+	  :key2 => { :this => "is", :a => "hash" } 
+	}
+
+
+Example data binding keys using this data:
+
+`{{@data/key1/0}}` will be replaced with 'array'
+
+`{{@data/key1/2}}` will be replaced with 'elements'
+
+`{{@data/key1/5}}` will be replaced with an error message
+
+`{{@data/key2/this}}` will be replaced with 'is'
+
+`{{@data/key2/this}}` will be replaced with 'hash'
+
+
+Within a repeatable element, the root node is replaced with the element that is being repeated. See the example in the repeatable section above. To reference the root element while inside a repeatable a `/` should be prepended to your data binding expression: `{{/@data/key1/0}}`
+
+## Validation
+
+Validation is expressed as a key added to an existing metadata definition. Below is a sample showing all of the validations that can be used.
+
+	:::ruby
+	:validation => {
+	   :regexp = "^.+$",
+	   :validators = [:required, :number, :currency, :email, :phone],
+	   :min_len = 0,
+	   :max_len = 100,
+	   :min_value = 10,
+	   :max_value = 1000
+	}
+
+## Templates
+### Form
+An HTML form that is used for submitting data:
+
+	:::html
+	<form></form>
+    
+
+* **Type**
+	* `form`
+* **Keys**
+ 	* `name` - used as name attribute in &lt;form&gt; tag
+	* `action` - used as action attribute in &lt;form&gt; tag
+	* `method` - used as method attribute in &lt;form&gt; tag
+* **Children** 
+	* Children are rendered between the &lt;form&gt; and &lt;/form&gt;  tags
+
+### Panel
+Contains children with a &lt;div&gt; tag with the div class set to 'panel':
+
+	:::html
+	<div class="panel"></div>
+
+* **Type**
+	* `panel`
+* **Keys** 
+	* `unused`
+* **Children** 
+	* Children are rendered between the &lt;div&gt; and &lt;/div&gt;  tags
+
+### View
+Contains children with no extra html.
+
+* **Type** 
+	* `view`
+* **Keys** 
+	* `unused`
+* **Children** 
+ 	* Children rendered directly
+
+### Table
+HTML Table.
+	
+	:::html
+	<table></table>
+
+* **Type** 
+ 	* `table`
+* **Keys** 
+	* `class` - class attribute on &lt;table&gt; element
+* **Children** 
+	* Children are rendered between the &lt;table&gt; and &lt;/table&gt;  tags
+
+### Text
+A labeled text display.
+
+	:::html
+	<div>
+  	  <label></label>
+      <span></span>
+	</div>
+
+* **Type** 
+	* `text`
+* **Keys** 
+	* `div_class` - class attribute for div
+	* `label_class` - class attribute for label
+ 	* `value_class` - class attribute for span
+ 	* `label` - value for label element
+	* `value` - value for inner div element
+* **Children** 
+	* Does not render children
+
+### Text Input, Password
+A labeled text input.
+
+	:::html
+	<div>
+  	  <label></label>
+      <input type="text|password"></input>
+    </div>
+
+* **Type** 
+	* `textinput|password`
+* **Keys** 
+	* `div_class` - class attribute for outer div
+	* `label_class` - class attribute for label
+ 	* `value_class` - class attribute for input
+	* `label` - value for label element
+	* `value` - value attribute for input
+	* `name` - name attribute for input
+	* `editable` - boolean value, enable/disable changing of selection. Default `true`.
+* **Children** 
+	* Does not render children.
+
+### Text Area
+Text area input field.
+
+	:::html
+	<textarea>
+	</textarea>
+
+* **Type** 
+	* `textarea`
+* **Keys** 
+	* `class` - class attribute for  textarea
+	* `value` - value attribute for textarea
+	* `name` - name attribute for textarea
+	* `rows` - rows attribute for textarea
+	* `cols` - cols attribute for textarea
+	* `editable` - boolean value, enable/disable changing of selection. Default `true`.
+* **Children** 
+	* Does not render children.
+
+### Select
+HTML Select.
+
+	:::html
+	<div>
+  	  <label></label>
+      <select>
+        <option></option>
+      </select>
+	</div>
+
+* **Type** 
+	* `select`
+* **Keys** 
+	* `size` - size attribute for select
+	* `class` - class attribute for select
+	* `allow_multi` - boolean value, allow multiple selection on dropdown. Default `false`.
+	* `editable` - boolean value, enable/disable changing of selection. Default `true`.
+	* `div_class` - class attribute for outer div
+	* `label_class` - class attribute for label
+	* `label` - value for label element
+	* `value` - default value displayed
+	* `values` - array of strings to provide as options
+* **Children** 
+	* Does not render children.
+
+### Checkbox
+A checkbox field
+
+	:::html
+	<div>
+  	  <label></label>
+  	  <input type="checkbox"></input>
+	</div>
+
+* **Type** 
+	* `checkbox`
+* **Keys** 
+	* `div_class` - class attribute for outer div
+	* `label_class` - class attribute for label
+	* `label` - value for label element
+	* `name` - name attribute for input
+	* `default_value` - boolean value, true = checked, false = unchecked. Default `false`.
+	* `value` - string value, 'true' = checked, anything else = unchecked
+* **Children** 
+	Does not render children.
+
+### link
+An anchor tag.
+
+	:::html
+	<a href=""></a>
+
+* **Type** 
+	* `link`
+* **Keys** 
+	* `url` - the url inside the href attribute
+	* `text` - the text that the link displays
+* **Children** 
+	* Does not render children.
+
+### telephone
+Anchor tag, with click to call information.
+
+	:::html
+	<a href=""></a>
+
+* **Type** 
+	* `telephone`
+* **Keys** 
+	* `number` - the phone number to call
+	* `text` - The text that the link displays
+* **Children** 
+	* Does not render children.
+
+## Advanced Adapter Example
+Here is a more advanced source adapter `metadata` example which demonstrates the concepts we described here:
+
+	:::ruby
+	def metadata
+	  @contact = {
+		:label => '{{name}}',
+	    :name => 'contact',
+	    :type => 'labeledrow', # a row which links to another 
+							   # object in a different model
+	    :value => '{{age}}, {{year}}' 
+	  } # name and phone of the contact object not the account!
+
+	  @rows = {
+	    :type => 'view',
+	    :children => [@contact],
+	    :repeatable => '{{@forms}}'
+	  }
+
+	  @link = {
+		:label => 'New',
+	    :value => '{{@link1}}',
+	    :type => 'labeledrow'
+	  }
+
+	  @table = {
+		:label => 'table',
+	    :name => 'table',
+	    :type => 'table',
+	    :class => 'grid',
+	    :children => [@link, @rows]
+	  }
+
+	  @index = {
+	    :title => 'PEOPLE',
+	    :type => 'iuipanel',
+	    :children => [@table]
+	  }
+
+	  @error = { 
+	    :label => '{{@errorlabel}}',
+	    :type => 'text',
+	    :name => 'name',
+	    :value => '{{@errors}}'
+	  }
+
+	  @name = { 
+		:label => 'name',
+	    :type => 'textinput',
+	    :name => 'name',
+	    :value => '{{@form/name}}',
+	    :validation => { :validators => [:required] }
+	  }
+
+	  @age = { 
+		:label => 'age',
+	    :type => 'textinput',
+	    :name => 'age',
+	    :value => '{{@form/age}}',
+	    :validation => { 
+		  :validators => [:required], 
+		  :min_value => 13 
+		}
+	  }
+
+	  @year = { 
+		:label => 'year',
+	    :type => 'textinput',
+	    :name => 'year',
+	    :value => '{{@form/year}}',
+	    :validation => { 
+		  :validators => [:required], 
+		  :max_value => 2010 
+		}
+	  }
+	    
+	  @submit = { 
+		:name => 'submit',
+	    :value => 'submit',
+	    :type => 'submit'
+	  }
+
+	  @form = { 
+		:name => 'inputform',
+	    :action => '{{@submiturl}}',
+	    :type => 'form',
+	    :children => [@error, @name, @age, @year, @submit]
+	  }
+
+	  { 'indexdata' => @index, 'new' => @form }.to_json
+	end
+
+## Custom Templates
+
+Templates can be overridden by placing the ERB files in the `app/templates` folder in your Rhodes application. They will be used before using any of the built-in templates.