this (eval( )eval) will bit of confusing. If we want to add php it
should be <?php and ?>. If we will have (eval( we will need to have
also ((field)) and [username] and (eval( don't tell users that this is
php. If we want learning curve to be small we need to have the same
thing as normal php file, so this:
<?php for ($i=; $i<0; ++$i) { ?>
<li><?= $i ?></li>
<?php } ?>
with only eval will not, so if we will have only one markup it should
be called (php( )php), our old (script( )script), (aiki( )aiki) or
Bassel's <aiki aiki>.
the one thing that will be missing is inherit widget but we can use
$aiki->Widgets->inherit("SELECT * FROM aiki_users"); (there is
blueprint or bug that we should have widgets API).
But personally I will prefer aiki markup with as few tags as possible
that will allow to do all stuff that's is needed (I don't care about
the markup, but it should allow to do complicated stuff if users need
them). I also will prefer, if Aiki just support php, that it will
not be the default engine and Admin panel will allow so change to it and
that Aiki support all php the same way as php file. It can be executed
as eval but it will need some modification of the widget content to
execute the code I put above.
On Thu, 23 Feb 2012 22:27:20 +0100
Roger Martín <rg1...@gmail.com> wrote:
> Hi Jakubs!
>
> Your right A pure-php engine only needs one parser (eval(...)eval) to
> work. It's dangerous, but can represent a advantage: the learning
> curve for php programmer is shorter. For the rest, learn php!!
>
> PD: moustache is genial...i'm thinking to make a markup to support
> it!!
--
Jakub Jankiewicz
twitter: @jcubic
www: http://jcubic.pl
_______________________________________________
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
