I should change #3 to read: 3. Values used elsewhere on the page that are also in the form are often rendered before the form is processed
On Fri, Mar 23, 2012 at 3:50 PM, Christopher Adams <[email protected]>wrote: > Another huge problem with Aiki forms: > > 1. The form is displayed and processed on the same page in the same widget > 2. Values entered in the form are often part of the page the form is on > 3. Values taken from the form are often rendered before the form is > processed > > Therefore > > 4. After submitting a form, parts of the page can be out of date and not > reflect the current state of the database. > > How would you address this problem? > > Christopher > > On Fri, Mar 23, 2012 at 2:56 PM, Christopher Adams <[email protected]>wrote: > >> It's really great to see progress on new Aiki forms! This and the new >> ideas for the routing engine are the two most important features I need! >> >> Some comments: >> >> * The "process": field is exactly what I have been looking for! In >> addition to calling functions, is there a way to apply logic? There would >> seem to be a need both for the ability to process the input with a >> function, but also to run some true/false test on it before inserting into >> the database. Maybe there should be two fields, "process": and >> "validation": ? >> >> I also want to see more about how to load and insert form values from/to >> multiple tables. >> >> * the "placeholder" - I would like to have this field. If browsers don't >> support it, Aiki does not have to do anything. Site designers have the >> choice of using a placeholder polyfill if they want, but there is no reason >> to bake that into Aiki. >> >> * in addition I would like a way to disable a form element. To do that >> you need to add class="disabled" and disabled="" to the <input> >> >> * the "layout": - I want to know more about this >> >> If I am using a CSS framework to design a site, I often need my forms to >> follow the framework's form markup. At this point my only solution is to >> use JavaScript to rewrite the form before the page loads. >> >> There's no way for Aiki forms engine to support every kind of form markup. >> >> I wonder if instead the Aiki forms markup could allow us to interleave >> HTML and aiki markup. >> >> { "type":"custom" } >> >> followed by actual HTML and even Aiki code! >> >> What do you think? >> >> Christopher >> >> 2012/3/19 Jakub Jankiewicz <[email protected]> >> >>> Maybe using "submit" since this name is used in html. Or maybe using >>> add as argument to form >>> >>> (form( add { >>> >>> "sumbit": "Register" >>> })form) >>> >>> and users will be able to put >>> >>> (form( (!(2)!) { >>> >>> "submit": "(!(1)!)" >>> })form) >>> >>> NOTE: new parser should have ((1)) instead >>> >>> and have one form, it will be better then looking at the form and >>> search for "save" if you will have 20 fields it will be more difficult >>> to change form to edit, and if user need to form he too will need to >>> copy that form and put different "save" so it will not be simpler. >>> >>> What about radio[] and permission do you agree? >>> >>> >>> On Sun, 18 Mar 2012 22:29:33 +0100 >>> Roger Martín <[email protected]> wrote: >>> >>> > hi jabuk >>> > >>> > Forms2 doesn't use table for save/load forms. With your syntax, >>> > form:add, form:edit, a developer need write two times the same form >>> > to edit and add data. >>> > >>> > Save attribute is not old "save". Perhaps a better name can be >>> > "save-when-there-is-detected-a-submit-button-named-as": >>> > "name-of-submit', but for a strange reason, i choose the 'save' >>> > option ;-). "save-on" and "add-on" can be clearer ? >>> > >>> > The objective of the attribute "save" is that with only one form, >>> > aiki can: show a existing record, show a blank (new) record, save an >>> > existing record, add a new record. Make it simpler. >>> > >>> > >>> > Roger: >>> >>> -- >>> Jakub Jankiewicz >>> twitter: @jcubic >>> www: http://jcubic.pl >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~aikiframework-devel >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~aikiframework-devel >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >> >> -- >> ——— >> christopher adams >> 86 186 1172 0021 | 1 646 201 3335 >> 49 15 156 219931 | 886 953 036 630 >> chris.raysend.com >> > > > > -- > ——— > christopher adams > 86 186 1172 0021 | 1 646 201 3335 > 49 15 156 219931 | 886 953 036 630 > chris.raysend.com > -- ——— christopher adams 86 186 1172 0021 | 1 646 201 3335 49 15 156 219931 | 886 953 036 630 chris.raysend.com
_______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
