good ideas.. aiki markup need more elegance and clearness
2011/3/17 Jakub Jankiewicz <[email protected]> > I have another idea for AIKI markup clean up, lets remove everything > and keep only $aiki public API and put in <aiki aiki>. > > and all functionality from markup move to aiki > > <aiki form->insert(10) aiki> > > <aiki form->ajax(10) aiki> > > <aiki widget(10)->add() aiki> > > Widgets should have parameters so instead of > > (#(inherit:97|SQL NEW SELECT STATMENT)#) > > <aiki widget(10)->insert((!(1)!), (!(2)!)) aiki> > > and URI parst should be $0, $1, $2 > > <aiki widget(10)->insert($1, "$2") aiki> > > <aiki system->widgets->create(....) aiki> > > database snapshots: > > <aiki system->save("name") aiki> > <aiki system->restore("name") aiki> > > and of course raw access to database > > <aiki system->query("select html from aiki_widgets where name = '$1") aiki> > > _______________________________________________ > Mailing list: https://launchpad.net/~aikiframework-devel > Post to : [email protected] > Unsubscribe : https://launchpad.net/~aikiframework-devel > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
