2012/2/3 Jakub Jankiewicz <jcu...@onet.pl>

>
>
> On Sat, 4 Feb 2012 03:07:33 +0800
> Jon Phillips <j...@fabricatorz.com> wrote:
>
> > I'm fine with the (aiki()aiki) over the (script()script)
> >
> > The <aiki aiki> I don't care for.
> >
> > Anyway, I think the (()) fits in well, with the db variables, etc...
> >
> > Jakub, could you make sure the aiki markup 2 proposal plan also
> > incorporates the other markup types and the variables...we really need
> > consistency.
>
> I want all variables will be the same ((variable)), and there will be
> not $foo. I don't like also
>        $aiki->membership->logOut
> better
>        membership::logOut
>
> there is only one namespace in aiki. This is php leaking from Aiki Core
> into markup.
>
> And Bassel give me idea about to remove (script( or (aiki( and use
>
>        (membership::logOut())
>
>
<aiki
membership::logOut();
aiki>



> But it don't look like other (if(  )if) so maybe it will be better to
> have (if(   ))    (if( ((foo)) = "foo" { <do stuff>  }))
>
> Other idea to not use (script( but (embed( or (insert( because
> this exactly what it does, it insert text that was returned by
> extension, why it should be called aiki? Script is also not good
> because it not a script only one function invocation.
>
> Other are (call( , (invoke( (exec(
>
> (in different places: "exec" is used for invoking program on the system,
> "call" is good because it is used to call a function, "invoke" is used
> to call a method, which also sound good)
>
> invoke also is good if you want to use extension that don't return a
> value, you don't insert that you "invoke extension"
>
> I vote for (invoke( memeberhip::logOut() )invoke)
> -> is legacy in php from C, and $aiki is php legacy in Aiki markup
>
>
> <aiki for script is reasonable but it will be difficult to define how
> it should work for complex nested Aiki code (and it will not look good
> for such complex usage)
>
> Comments?
>
>
it should look natural without having to write <aiki each time, and this is
something I have been working on since a while. but also if you guys don't
like <aiki aiki> we can make:

<aiki> then stuff goes here without having to use <aiki> each time for each
command</aiki>

but using <aiki> looks more like script for people like html. and <aiki
will give them the impression that they can write normal php which sorta
they can if we managed to process the functions one by one



> >
> > Jon
> >
> > On Fri, Feb 3, 2012 at 11:47 PM, Bassel Safadi
> > <bassel.saf...@gmail.com> wrote:
> > > I think using markup like in (script( or (if( is also non standard
> > > and still ugly, the old aiki markup used to
> > > look something like:
> > > <php
> > > if ....
> > > php>
> > >
> > > ok and we removed the <php tag since Jon and others thought it's
> > > not php. ok we can replace with something like script (although the
> > > script is used in html) but lets say we have something like <aiki
> > > which is not implemented now fully, I mean if the markup parser was
> > > only triggered when <aiki is used that will save us a lot of
> > > processing power. so instead of having stuff that look like <aiki
> > > aiki> and other stuff that look like (script( or (if( they all
> > > aiki> should look like:
> > >
> > > <aiki
> > > if (something = something){
> > > do something
> > > }
> > > aiki>
> > >
> > > --
> > > Bassel Safadi | http://bassel.ws
> > > Skype: i.know.sy | Global: +1-323-545-3855
> > >
> > >
> > >
> > > On Fri, Feb 3, 2012 at 12:14 PM, Jakub Jankiewicz <jcu...@onet.pl>
> > > wrote:
> > >>
> > >> I wanted in Aiki markup to have place for functions like
> > >> (replace( so we can simple add more of them like (p( and (br( and
> > >> also it would be create if users will be able to add new once.
> > >> Maybe with this parser extensions.
> > >>
> > >> Maybe instead of $aiki->Class->some_function we will have
> > >> (some_function(
> > >>
> > >> IMO the (script( should stay because users maybe will need to call
> > >> function that are in Aiki Core, and if this will be removed they
> > >> will need to write (api_function( wrapper only to call built-in
> > >> function.
> > >>
> > >> but maybe instead of (script( $aiki->membership->logOut(); )script)
> > >> we will have (membership::logOut( ))
> > >> this is too long (membership::logOut( )membership::logOut)
> > >>
> > >>
> > >> and in other places we will have it too
> > >>
> > >> (if( membership::permission == 'SystemGOD' {
> > >>    <p>Master I'm here to serve you</p>
> > >> })if)
> > >>
> > >> we will get rid with this php legacy with this.
> > >>
> > >> maybe instead of
> > >>
> > >>        (if(  foo == bar {
> > >>           <p>true</p>
> > >>        })if)
> > >> this
> > >>        (if( foo == bar {
> > >>           <p>true</p>
> > >>        }))
> > >>
> > >> in this case it will look the same as (function_call( ))
> > >>
> > >> What do you think?
> > >>
> > >> On Fri, 03 Feb 2012 03:29:51 -0000
> > >> Christopher Adams <ch...@raysend.com> wrote:
> > >>
> > >> > Blueprint changed by Christopher Adams:
> > >> >
> > >> > Whiteboard changed:
> > >> >   This is list that also might be removed
> > >> >
> > >> >   [br[html or db field]br] - who will use this
> > >> >   [p[html or db field]p] - the same
> > >> >
> > >> >   (#(related:some||keywords||here)#) - is this even working, the
> > >> > same tags
> > >> >   (#(tags: some, tags, go, here)#) - Aiki don't have tags so how
> > >> > this is gonna work
> > >> >
> > >> >   {+{SOME_STORED_IMAGE_NAME|alternative text|float|vspace
> > >> > attribute|hspace attribute|path prefix|description}+} not even
> > >> > used by OCAL / and is just to complicated why don't use simple
> > >> > <a><img..../></a> Aiki should help in developing html not
> > >> > replace it. ###
> > >> > + The [br[ and [p[ functions are very useful. Anyone working
> > >> > with a
> > >> > + WordPress or other blogging database will need these. Can you
> > >> > turn them
> > >> > + into a function or filter to be consistent with your Aiki
> > >> > markup
> > >> > + changes? Please keep these functions available. ~~~~christopher
> > >> > +
> > >> >   HOWTO deprecate these ? @rejon
> > >> >
> > >> >   Can you update this blueprint with more reasoning why possible
> > >> > to remove? @rejon
> > >> >
> > >>
> > >> --
> > >> 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
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> > >
> >
> >
> >
>
> --
> 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

Reply via email to