I see a plan here: 1.) We clean-up the classes where current aikimarkup is located and abstract the markup capability, so that its simple to extend markup. * Add a hooks capability so that filters can be called upon widgets composition and/or markup processing
2.) We clean up aikimarkup into a lisp-like markup, with current functionality supported in aikimarkup and provide REAL documentation. This should be part of the core, but extend the base functionality in aiki core, so we can prove it works to extend aiki markup. (somefunc(someparam)) ALT: we copy current functionality, and use xmllike markup: <am:somefunction /> or <aiki:somefunction /> 3.) We allow hooking in other markups if others want: * phptal, http://phptal.org/manual/en/ * F3, http://fatfree.sourceforge.net/page/views-templates Another approach, which I'm starting to lean towards is to just allow full on php inside of aiki. I really don't see a demand for aiki core being rewritten in ruby, or any other language, other than php. A stopgap would be to only allow simple markup when editing aiki sites, and any business logic should be separated out into extensions or apps. If there is no good reason to break this rule, then we won't. In building a few of these content management systems, notably ccHost, I've seen how markup usually goes. You add something like phptal, it is just another step that keeps developers out, and eventually the php slog gets introduced or used. So, why not just allow full on php? I'm curious to hear some more thoughts on this. I feel pretty clear about a plan now to abstract the markup, just need to decide on how our default should work. Jon SIDENOTE: Check out this old system aaron swartz developed that we used in making http://openlibrary.org: http://infogami.org/ Its somewhat like aiki in intent. Something I think has been lost in aiki. -- 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 : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
