guys we should all work on one aiki markup implementation I think before anyone develop his own parser we should agree on the markup instead we will end up with three different parsers and three different engines. which doesn't make sense and will waste much effort. what do you think? let's have one wiki page for the specs of the final parser then we can break the implementation into tasks and all of us can work on it.
Cheers -- Bassel Safadi | http://bassel.ws Skype: i.know.sy | Global: +1-323-545-3855 2012/2/14 Jakub Jankiewicz <[email protected]> > This you read this? > http://www.aikiframework.org/wiki/Implementation_of_new_parser > > This was my plan for implementation my aiki markup proposal. > > On Mon, 13 Feb 2012 22:47:27 +0100 > Roger Martín <[email protected]> wrote: > > > Hi folks > > > > perhaspz i found a elegant solution for pagination with only on uery > > (now aiki make two query to make). > > > > see > > > http://www.aikiframework.org/wiki/Aiki_parser_2#SQL_PARSER_and_PAGINATION > > See too > > http://www.aikiframework.org/wiki/Aiki_parser_2#SQL_PARSER_and_COLUMNS > > -- > Jakub Jankiewicz > twitter: @jcubic > www: http://jcubic.pl > > _______________________________________________ > Mailing list: https://launchpad.net/~aikiframework-devel > Post to : [email protected] > Unsubscribe : https://launchpad.net/~aikiframework-devel > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
