Alec Thomas wrote:
> Taking a look at a couple of them:
>
> #2048
>
>   | {{{
>   | ...
>   | }}}.urgent
>
> -1...do we really need more Wiki syntax? My favourite of the options was:
>
>   [[div(class)]]
>   Some text
>   [[/div]]
>
>   [[span(class)]]Some text[[/span]]
>
> or [[block]], [[inline]]. I think the main point is:
>
>   - Keep it simple and just let the user specify a class (they can add
>     the class styling in their site CSS)
>   

In what is the proposed syntax not simple? It reuses the well-known 
{{{...}}} construct (for both the inline and block case) and extends it 
a bit. Simple to understand and implement, and they nest cleanly.

>   - Use existing syntax: macros.
>   

Well, no. Macros are meant to provide clean content. Of course they can 
(for now) already generate broken XHTML, but then the macros are broken.

I don't much see the benefit of preventing the use of (and breaking 
compatibility with):

{{{
#!html
<div class="xyz">
}}}
...

If we're only replacing that by:

[[div(xyz)]]
...

which leaves the same possibilities to mess up the content.
The {{{...}}} approach is more robust and (IMO) also more readable.


Compare the following syntax:

-----------------------
{{{
Note: This is important

{{{
even more {{{important}}}.big
}}}.urgent

Thanks for listening.
}}}.note
-----------------------

With:

-----------------------
[[div(note)]]
Note: This is important

[[div(urgent)]]
even more [[span(big)]]important[[/span]]
[[/div]]

Thanks for listening.
[[/div]]
-----------------------


-- Christian

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to