Update README.md
This commit is contained in:
parent
aaf6e94942
commit
1ddca06100
@ -80,6 +80,7 @@ The switches work together to see if a form should be protected by Sisyphus or n
|
|||||||
|
|
||||||
- Tests
|
- Tests
|
||||||
- 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).
|
- 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).
|
||||||
|
- rubydoc.info hosted documentation so the rubygems.org page doesn't look like crap.
|
||||||
- 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?
|
- 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/options via activerecord extension? We have config based exclude/includes now
|
- Model based exclusions/options via activerecord extension? We have config based exclude/includes now
|
||||||
- block based options (this would allow us to easily and neatly implement Sisyphus options)
|
- block based options (this would allow us to easily and neatly implement Sisyphus options)
|
||||||
|
Loading…
Reference in New Issue
Block a user