Can you guys please flesh out your ideas more on the wiki page. Lets do before sever too far....lisp/scheme is great IMO.
j...@fabricatorz.com http://fabricatorz.com On Mar 18, 2011 5:47 PM, "j...@rejon.org" <j...@rejon.org> wrote: > Lisp baby! > > j...@fabricatorz.com > http://fabricatorz.com > On Mar 18, 2011 5:39 PM, "Roger Martín" <rg1...@gmail.com> wrote: >>> If we include `if` and `for` aiki will be more flexible and allow to >>> create shorter widget that do more. >>> >>> >> totally agree....we must include for and if, but when i think in ocal >> librarians and their work making widget, i prefer ADD a shortcode >> like: >> >> <ul> >> (aiki walker("SELECT username FROM aiki_users WHERE id =$1", >> "<li>((username))</li>","<li>not user founds</li>")) >> </ul> >> >> or >> <div id='$0'> >> (aiki walker("SELECT * FROM ocal_files WHERE user_id =$1", ocal->thumb, > "the >> user has not clipart")) >> </div> >> >> a string starting with "" is HTML >> other: a call. >> >> or more more easy >> (aiki walker("SELECT * FROM ocal_files WHERE user_id =$1", ocal->thumb, > "the >> user has not clipart","div")) >> will generate: >> <div id=widget_name'> first. ... second<.. >> or >> <div id=widget_name' class='not-found'> the user has not clipart</div> >> >> this solution is less elegant and formal, .but i think we can mix the two >> proposal >> >> >> PD: note that every widget have a normal_select, widget and if_no_results >> fields. A walker is a mini-widget.
_______________________________________________ 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
