Hi folk!:
some notes:
- about placeholder and html5 in general. When a html5 feature is supported
by some browsers, we will not waste time implementing it. For example:
Safari and Firefox supports placeholder.
- list. You are right. It's better using arrays, or a string that will be a
SQL statement:
"list": { "1": "yes", "2": "no "2":
"list": "SELECT .....FROM ",
(informational) Php support of JSON is very naive..For example {1: "foo"}
or { 2:false} or { 'foo': 'bar'} is not supported because all field and
values must be surrounded by double quote.
- current form support: enctype, onsubmit, onreset, post, class,
action,submit,reset
is submit is given and it's not empty a submit button with field value as
text will be added. Reset is similar, but is disabled by default.
- (form:add(, (form:delete(, (form:edit( will be not supported for
markup parse. We can put a field name "do" (action is a html attribute). In
current implementation "save": ..is the name of submit button that aiki
must detect to know that a record must be added or saved.
Really, i dont' know what behavior to use, but i thinking in this:
- in display_urls: /user/@action=edit/@id | /user/@action=add
- in widget
(form { { "do": @action, "pkey": @id....
In this way, you need only one widget to edit/add records.
@action=edit is a idea about this blueprint:
https://blueprints.launchpad.net/aikiframework/+spec/improved-routing-engine
- radio is a 'primitive' control that normally is used with other radio.
Radios (with s) construct a list of brother radios.
{ "type": "radios", "name": "foo", "list", {"0": "No", "1": "yes", "2":
"remember later")...
is equivalent to (but shorter)
{ "type": "radio", "name": "foo", "caption": "No"
{ "type": "radio", "name": "foo", "caption: "Yes")
{ "type": "radio", "name": "foo", "caption: " Remeber"
In the same way, checkboxes will be a group of checboxes.
- text, textarea,radio,radios, select, and all html5 as raw can be ready
for 21-abril.
Roger
PD: i don't mentioned it in my first mail, but i will add a parse for JSON
to support this
{ 0:"yes", 1: "none"}
{ "permission": $aiki->membership->is_root() )} or simply {
permission: root}
{ "permission": $aiki->membership->user_id= field)} or simply ({
permission: user_id=field(clipart_user_id) } (2))..
(2) note that some checks need to read the record.
_______________________________________________
Mailing list: https://launchpad.net/~aikiframework-devel
Post to : [email protected]
Unsubscribe : https://launchpad.net/~aikiframework-devel
More help : https://help.launchpad.net/ListHelp
