thanks for the suggestions Jackub, I think we need to discuss each one of those on it's own, so would be great if you can take it a step further and file a blue print for each one, there is a lot to say about each situation, please find bellow what I think about some of the cases
On Thu, Mar 17, 2011 at 4:50 AM, Jakub Jankiewicz <[email protected]> wrote: > 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> > > those functions currently can also be accessed like: <php $aiki->widget->ineherit((!(1)!)); php> actually I see such vars as (!(1)!) uglier than the rest and think it should be highest priority to change those. so we need to think if we want the markup to look like xml? or like other programming language? in both cases <aiki aiki> is not looking good and doesn't solve the problem unless we want to invent our own language. but the whole idea of aiki is to build widgets so you don't need markup that much, my main concern is to have as less markup as possible, and the latest revisions and features (multi database setup) are example of how aiki is moving forward to detect what user mean rather than adding markup > and URI parst should be $0, $1, $2 > > Totally agree on this > <aiki widget(10)->insert($1, "$2") aiki> > > <aiki system->widgets->create(....) aiki> > > database snapshots: > > <aiki system->save("name") aiki> > <aiki system->restore("name") aiki> > > are those supposed to be used inside a widget? > and of course raw access to database > > <aiki system->query("select html from aiki_widgets where name = '$1") aiki> > there is advantage of using (sql( (select html from aiki_widgets where name = '$1||html output) )sql) and it's to build multi queries that can read from each other so you can do: (sql( (select html from aiki_widgets where name = '$1||html output) (select something from some_table where name = html_value_from_previous query||html output) )sql) using such method to build trees of data is much easier than normal php, and you can actually have loops of results inside loops. _______________________________________________ > Mailing list: https://launchpad.net/~aikiframework-devel > Post to : [email protected] > Unsubscribe : https://launchpad.net/~aikiframework-devel > More help : https://help.launchpad.net/ListHelp > -- Bassel Safadi http://bassel.ws http://aikilab.org Global +1 323-545-3855 Singapore +65 93488349
_______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
