totally. but how would this work on ruby? we should make this robust and logical so it works across installations.
IMO, we should allow NO PHP in, or ALL PHP in. In that case, I will just write PHP from commandline and vim like I love to do, rather than use AIki. Get my point? We sell aiki as a solution that could be rewritten in ruby, php, c, c++, but if we allow php in, like the real php, then we are tainting the code. I would even take this further down into extensions level as a pure concept, but, I'm flexible on this since one could rewrite those in other langagues....soooo, back to the point on the <aiki ... aiki>. Anyone? Jon On Sun, Jan 2, 2011 at 4:25 AM, Bassel Safadi <b...@ssel.me> wrote: > yes rejon I get your point, BUT when using <php $aiki->wiki->parse( text > ); php> you are actually calling a php class you just wrote, got my > point on this one? > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/692108 > > Title: > parsed php shouldn't even be called php > -- Jon Phillips http://rejon.org/ http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (sf/global) +86.187.1003.9974 (china) +65.8330.5807 (singapore) -- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/692108 Title: parsed php shouldn't even be called php Status in Aiki Framework: Confirmed Bug description: because its not. need to move to aiki: namespace or <aikiscript ... aikiscript> or something...anyway, this is a big learning problem for newbies. _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : aikiframework.admins@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
