Posted by silence on June 2, 2006 at 9:14pm
The main aime behind creating this story are:
-- We list all the requirements at one place.
-- We can discuss any shortcomings or anything else that is missing or wrong (So please contribute :).
The requirements as discussed in Meeting 1 are as follows:
-
On the server side:
- Load existing form array for editing (pass to JSON)
- Save draft/edited form(maybe as serialized array)
- validate edited/newly created form
On client Side:
- Creating the basic form - Includes textfields, textarea, password fields, checkboxes, radio buttons, dropdown lists, file Uploads, buttons, hidden fields and other things
- Editing their HTML properties and some of the properties which are allowed by Form API
- Provision for Parent/Tree structure
- A basic set of validation functions
- Multi Page functionality
- At a lower priority ... some frequently use fields
- If possible, There's a Drupal module called CCK that defines field types. It would be greate to link form-builder to that somehow.
Now these were the points exactly as discussed in meeting. Please comment on them, Categorize them in priorities 1-3(1-most imp, 3-can do without it in 1st version). We hope to freez them before 9th June
Comments
CCK integration probably out of scope
If you get to that point by the end of SoC, the CCK integration won't be a big challenge. I think we should say right up front that CCK is out of scope. Jeff, Nedjo? What do you guys think?
Agreed
But it would be useful to have the code reviewed by folks familiar with CCK to make sure we're building it in ways that will work for CCK.