any fresh ideas on this? On Tue, Nov 30, 2010 at 4:47 PM, Roger Martín <rg1...@gmail.com> wrote: > Hi bassel and jon!! > > I am thinking about widget, parsers, markups. Again i have suggestions and > ideas, but don't know where, how and with who can discuss it. > Perhaps if you or Jon can open a discuss or incorporate this idea in a open > discussion (if you judged convenient). > Sorry, i'm lost in wiki, launchad, lists...etc. > > IDEA > --------------------------------- > i want widget likes: > SQL: select id from ocal_files WHERE ... ORDER BY .... > content: <aiki ocal(image,((id))) /> (*) > > SQL: select user_id from user where......... > content: <aiki ocal(user,((id)) /> > > ocal(user,id) must read users data and generate the all HTML. > > That means: > - the site add a class to $aiki that gives some basic templates (ocal for > example require image-template and user-template ). > - the widget parser must: > - first parser the [] terms [root] (they are static). > - then, for every record, made the fields substitution. > - then, make the aiki parser substitution. I suggest, migrate all to > unified standard. > <php substr (..) -> <aiki substr()...> > <php str_replace -> <aiki replace() ->so..we are ready for > ruby.. > <php $aiki->...->... -> <aiki class(function,id) ... > new <aiki t(string to translate)... > (i've forget other variables..but don't have whole idea of aiki) > > Advantages: > - unified templates across the site in terms. > - improvements in template will be propagate to entire site. > - easy widget creation. You only need a SQL to move the world. > - The SQL can be simpler (only a id is required). > - the markup can be changed easy <aiki /> <aiki..></aiki>. > - powerfull: a site can add cached vars, hits, without changing parse > method. > - easy to parse algoritm : find every <aiki, and then or is a predefined > (if,substr,replace) ..or must be a class of aiki > - it can be DONE. > > inconveniences > - a site requires PHP programing..but it better and easy program in PHP than > aiki-code. Really, every site requires its templates: a font library for > font, a cms for news. > - all widget must be revised. > > Example: > for ocal, i suggested this methods: > - image(id) ->returns template filled for the id-image(thumbnail). > Required for byhits, byauthor, bydate, tag, search.... > - user(id) ->returns template filled for the user. Required for users, > most-active (new), nearest...etc. > - var(id) ->return some important var (total images, total users, > total this month) That avoid using (#inherent:121|SQl....) > - anotateHit($id)-->other markup that can disappear. > > > (in facts, is the same idea that $aiki->class-> ) > > roger > > > (*) i don't want all widget in this form. Global-rss, css, about,dmca...must > remain > > > >
-- Jon Phillips http://rejon.org/ | http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (global) | +1-510-499-0894 (sf) +86-187-1003-9974 (beijing) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : aikiframework-devel@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
