Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/dtex/fidos
Form Description Objects
https://github.com/dtex/fidos
Last synced: 3 days ago
JSON representation
Form Description Objects
- Host: GitHub
- URL: https://github.com/dtex/fidos
- Owner: dtex
- Created: 2013-02-14T17:34:08.000Z (almost 12 years ago)
- Default Branch: master
- Last Pushed: 2013-02-15T18:58:04.000Z (almost 12 years ago)
- Last Synced: 2024-11-04T11:25:15.315Z (about 2 months ago)
- Size: 113 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
fidos
=====Form Description Objects are JSON objects that describe a form's structure, validation, presentation and posting rules. This document describes only the JSON format for fidos and does not address the renderer, validator or posting acceptor.
{
"myKey": "addToDoItem",
"action": "default.asp",
"method": "POST",
"title": "Create a new to do item",
"instructions": "Fill out this form, playing close attention to the required fields to add a new item to your to do list",
"class": "simple wide",
"fields": {
"[fieldName]": {
"rules": { required: true, maxlength: 100 },
"type": "text",
"label": "Item Name",
"tooltip": "Enter a descriptive name for the to do item",
"value": "someValue"
}
},
"init": function() { console.log('initializing the form'); },
"submitHandler": function() { console.log('The user submitted the form'),
"onValid": function() { console.log('Validation passed'),
}**myKey** - A unique name for the form/fido.
**action** - The value for the form action property
**method** - The value for the form method property
**title** - A title to be displayed at the top of the form (not field specific)
**instuctions** - Instructions to be displayed at the top of the form (not field specific)
**class** - A class or classes that should be appied to the form element
**fields** - An object containing field objects for the form
**fieldName** - A unique name for the field that should be used on the form element's name and id properties
**rules** - Validation rules that match the rules defined in [jQuery validate](http://docs.jquery.com/Plugins/Validation/Methods/maxlength#length), our preferred for validator
**message** - Message that matches the object defined in [jQuery validate](http://docs.jquery.com/Plugins/Validation/Methods/maxlength#length), our preferred for validator
**type** - A form field type (text|hidden|div|select|checkbox|*custom*). You may create your own custom type, just be sure to handle it preoperly in your presentation validation and posting
**label** - The name to be used in the form element label
**tooltip** - Text to be displayed when rolling over a help icon
**value** - The default value for the field
**class** - A class or classes that should applied to the form element or a div that wraps the form element (depends on your presentation code).
**init** - A function that is called after your form is inserted into the DOMjQuery Validate
---------------All the [jQuery Validate options](http://docs.jquery.com/Plugins/Validation/validate#options) are valid options on the fido.
Note: jQuery Validate defines all messages in one object and all rules in another object. Here the individual rules and message are children of the field object. Your client side code should build the rules and messages object for jQuery Validate using these pieces. Check out the fidoHandler.js example for an example of how this can be done.
Presentation Handler
--------------------Your presentation handler could be client or server side. A client side implementation is shown in sampleFidoHandler.js. It should handle all the above properties and options. We will work on a standard FDO handler to use as a starting point.
Customizing
-----------You can of course sprinkle in your own properties and functions and use them in your presentation or posting acceptor code.