We thought a lot about this new markup, I think Jakub's proposal is much more sound and useful than others and the current implementation. Higher priority now IMO, forms, forms, forms, and parser improvements!
Jon On Fri, Feb 3, 2012 at 11:54 PM, Bassel Safadi <[email protected]> wrote: > hey guys, soooooo on http://aikiframework.org/wiki/Aiki_markup_2 > I don't agree on this markup at all, using (for( )for) just because it's > easier to process than for () doesn't make since. > we should keep the original plan that was something like: > <aiki > for (){ > > } > aiki> > > of course this looks less new markup and more like php and since aiki is > written in php I don't see why we need to invent yet another new markup > while the point of rewriteing the parser was not inventing new markup. > > sooooo and I'm making progress on making > <aiki > stuff like in php > aiki> > > I don't think the proposal on http://aikiframework.org/wiki/Aiki_markup_2 > will make aiki markup easier instead more complicated. > > -- > Bassel Safadi | http://bassel.ws > Skype: i.know.sy | Global: +1-323-545-3855 > > > > 2012/2/3 Jakub Jankiewicz <[email protected]> >> >> We can keep it till 1.0 but there should be switch they should >> not coexist together IMO, we don't need to do things like languages >> (python or php), we can add to $config 'use_old_syntax' and we can have >> code that will detect old markup and show error that they use old >> markup with new Aiki with link to new documentation and that they >> should use new markup and if they really want to use old one they can >> turn it on. But if they do it new markup feature will not work. So >> those few that use old markup will be encourage to use new markup, and >> we will be able to remove that code in 1.0. >> >> There should not be in the code stuff like check for two different >> markup. Like there is with inherit right now. >> >> On Fri, 3 Feb 2012 10:31:19 +0800 >> Jon Phillips <[email protected]> wrote: >> >> > I agree. And, one thing we should keep in mind is that there are still >> > few aiki-based sites, so we have to consider: >> > >> > * do we keep support for the old markup >> > * keep it for a while >> > * or just replace it with a well thought out solution >> > * or a combination of the above >> > >> > I would lean towards abstracting the old markup if possible, and >> > maintaining support for a while, but working on the more thorough plan >> > and implement it. >> > >> > Jon >> > >> > On Fri, Feb 3, 2012 at 1:29 AM, Jakub Jankiewicz <[email protected]> >> > wrote: >> > > Sorry, I already suggest markup >> > > http://aikiframework.org/wiki/Aiki_markup_2 >> > > >> > > and I registered a blueprint for things I want to remove >> > > https://blueprints.launchpad.net/aikiframework/+spec/remove-from-aiki >> > > >> > > There was no response either from you or from others, >> > > only Jon agree with me (in response on this list not whiteboard), >> > > so I assume that this markup I propose to remove are not in use, and >> > > everybody agree with that. So I was surprise that users use it. >> > > >> > > I assume that all that markup that is not in use will go to trash, >> > > sorry if I offended you by calling it shitty. You've done great work >> > > with Aiki, I just want to make it better. >> > > >> > > If you don't agree with me about those things I want to change, then >> > > just comment that blueprint and modify that proposal. >> > > >> > > >> > > On Thu, 2 Feb 2012 17:21:39 +0200 >> > > Bassel Safadi <[email protected]> wrote: >> > > >> > >> Jakub: this markup is used a lot and very useful. and so that you >> > >> know, I don't like the word shitty to be used that much about my >> > >> code. if you think it look bad, fine go ahead and suggest better >> > >> markup. but you can't just say shit about others work! >> > >> >> > >> >> > >> On Thu, Feb 2, 2012 at 12:46 PM, Jakub Jankiewicz <[email protected]> >> > >> wrote: >> > >> >> > >> > Do you use those shity markup I wanted to remove it from Aiki? >> > >> > >> > >> > And I think that this is the proper behaviour >> > >> > >> > >> > if ((post_content)) is >> > >> > >> > >> > ===0 >> > >> > this is paragraph one >> > >> > >> > >> > This is paragraph 2 >> > >> > ===0 >> > >> > >> > >> > and you put it in blockquote >> > >> > >> > >> > <blockquote>[p[ ((post_content)) ]p]</blockquote> >> > >> > >> > >> > You will have what you want. this is text sensitive not xml >> > >> > sensitive. >> > >> > >> > >> > What about if you have this >> > >> > >> > >> > ===0 >> > >> > <blockquote>this is <span>paragraph one >> > >> > >> > >> > This is</span> paragraph 2</blockquote> >> > >> > ===0 >> > >> > >> > >> > You will end with (if it work as you want): >> > >> > >> > >> > ===0 >> > >> > <blockquote><p>this is <span>paragraph one</p> >> > >> > >> > >> > <p>This is</span> paragraph 2</p></blockquote> >> > >> > ===0 >> > >> > >> > >> > which will be invalid xml too. How this simple text sensitive >> > >> > replacement should know how to handle this? >> > >> > >> > >> > >> > >> > On Thu, 02 Feb 2012 09:46:23 -0000 >> > >> > Christopher Adams <[email protected]> wrote: >> > >> > >> > >> > > Public bug reported: >> > >> > > >> > >> > > I noticed this while creating an RSS feed in Aiki: >> > >> > > >> > >> > > Let's say my ((post_content)) looks like this: >> > >> > > >> > >> > > ===0 >> > >> > > <blockquote>this is paragraph one >> > >> > > >> > >> > > This is paragraph 2</blockquote> >> > >> > > ===0 >> > >> > > >> > >> > > Then the output of [p[ ((post_content)) ]p] will be >> > >> > > >> > >> > > ==== >> > >> > > <p> >> > >> > > <blockquote>this is paragraph one</p><p> >> > >> > > This is paragraph 2</blockquote></p><p> >> > >> > > ==== >> > >> > > >> > >> > > You see how the </p><p> is located INISDE the <blockquote>? >> > >> > > >> > >> > > This will generate an invalid XML warning: >> > >> > > >> > >> > > Opening and ending tag mismatch: blockquote line 0 and p >> > >> > > >> > >> > > My temporary fix is to use [br[ instead of [p[ >> > >> > > >> > >> > > But it would be nice if [p[ doesn't ever produce invalid >> > >> > > markup! >> > >> > > >> > >> > > ** Affects: aikiframework >> > >> > > Importance: Undecided >> > >> > > Status: New >> > >> > > >> > >> > >> > >> > -- >> > >> > 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 >> > >> > >> > > >> > > -- >> > > 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 >> > >> > >> > >> >> -- >> Jakub Jankiewicz >> twitter: @jcubic >> www: http://jcubic.pl > > -- Jon Phillips 王✳爻气 http://fabricatorz.com ✳ skype: kidproto ✳ irc: rejon +1.415.830.3884 (global) ✳ +86-187-1003-9974 (beijing) -- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/925356 Title: The [p[ ]p] command can create invalid markup in certain edge cases Status in Aiki Framework: New Bug description: I noticed this while creating an RSS feed in Aiki: Let's say my ((post_content)) looks like this: ===0 <blockquote>this is paragraph one This is paragraph 2</blockquote> ===0 Then the output of [p[ ((post_content)) ]p] will be ==== <p> <blockquote>this is paragraph one</p><p> This is paragraph 2</blockquote></p><p> ==== You see how the </p><p> is located INISDE the <blockquote>? This will generate an invalid XML warning: Opening and ending tag mismatch: blockquote line 0 and p My temporary fix is to use [br[ instead of [p[ But it would be nice if [p[ doesn't ever produce invalid markup! To manage notifications about this bug go to: https://bugs.launchpad.net/aikiframework/+bug/925356/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
