sisyphus-rails/README.md

88 lines
2.8 KiB
Markdown
Raw Permalink Normal View History

2012-10-01 12:29:36 +00:00
# Sisyphus::Rails
A gem to add gmail like form saving through sisyphus.js
## Installation
Add this line to your application's Gemfile:
gem 'sisyphus-rails'
And then execute:
$ bundle
Or install it yourself as:
$ gem install sisyphus-rails
2012-10-01 20:55:36 +00:00
For a basic install include the following in your *app/assets/javascripts/application.js* file
2012-10-01 14:37:28 +00:00
//= require sisyphus
2012-10-02 14:47:02 +00:00
To support IE6/7 users include jStorage as well
2012-10-02 14:47:30 +00:00
//= require jstorage
2012-10-03 00:58:57 +00:00
//= require sisyphus
2012-10-02 14:47:02 +00:00
2012-10-01 20:42:14 +00:00
## How it Works
Sisyphus uses an aliased form_tag method to automatically put a *<script>...</script>* tag infront of your forms to initialize Sisyphus. It also uses an aliased FormHelper form_for method to read options.
2012-10-01 20:42:14 +00:00
2012-10-01 20:55:36 +00:00
<script>$(document).ready(function() {$('#sampleform').sisyphus();});</script>
<form id="sampleform">
...
2012-10-01 20:55:36 +00:00
</form>
2012-10-01 12:29:36 +00:00
## Usage
2012-10-01 20:42:14 +00:00
Sisyphus automatically works with all your forms, including custom form builders.
### Exclude form
2012-10-01 14:37:28 +00:00
To stop Sisyphus from initializing on a form include the *with_sisyphus* option in your form_for.
<%= form_for User.new, :with_sisyphus=>false do |f| %>
...
<% end %>
2012-10-01 14:37:28 +00:00
## Dependencies
- Rails >= 3.1
- Jquery 1.8+
2012-10-01 12:29:36 +00:00
## TODO
- Tests
2012-10-02 14:47:02 +00:00
- Move away from form_tag_helper, should be able to do it all from form_helper? Script tag can go at the end anyhow. Why aren't we doing that right now? We don't seem to have access to the same variables that the regular form_for does. Also the options array gets muddied by the FormHelper form_for call -> it removes the [:html] section (we need the id of the form for sisyphus).
- conflict resolution... i.e. you have an object edit form, the fields are populated from the DB but if you have local browser changes they may get overridden. We need a way to resolve conflicts between local and remote data -> could use a jquery based modal dialog to present the diff?
- Model based exclusions via activerecord extension?
2012-10-02 14:47:02 +00:00
- block based options (this would allow us to easily and neatly implement Sisyphus options)
<%= form_for User.new do |f| %>
<% :sisyphus => flase %>
2012-10-02 14:47:02 +00:00
<% :sisyphus_customKeyPrefix => 'sisy' %>
...
<% end %>
2012-10-02 14:47:30 +00:00
2012-10-02 14:47:02 +00:00
- implement all sisyphus options and any relevant ones in jStorage
2012-10-01 12:29:36 +00:00
## Contributing
If you have time to tackle something off the TODO list before I manage to get around to it then please do!
2012-10-01 12:29:36 +00:00
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
2012-10-02 14:47:02 +00:00
## Included Libraries
2012-10-01 12:29:36 +00:00
2012-10-02 14:47:02 +00:00
https://github.com/rails/jquery-rails
2012-10-01 12:29:36 +00:00
https://github.com/simsalabim/sisyphus
2012-10-02 14:47:02 +00:00
https://github.com/andris9/jStorage
## Resources
http://coding.smashingmagazine.com/2011/12/05/sisyphus-js-client-side-drafts-and-more/