David Abrahams wrote:
> on Thu Jun 28 2007, Christian Boos <cboos-AT-neuf.fr> wrote:
>
>> 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.
>>
>
> >From the user's POV, the triple curlies today clearly imply: "this
> will *not* be interpreted by the regular trac wiki markup engine.
> Either we are going to treat it as literal text, or some other markup
> processor will handle it." IIUC, you're proposing to change that, and
> I think it could be confusing.
>
Ok, I understand the concerns. Actually I think it's possible to take
the "macro" route, if we use the wikiprocessor block style for the div,
that way we're nearly 100% compatible with the existing WikiFormatting
syntax.
A span macro can be used for spans, the first argument will be the class:
[[span(NOTE, this is cool)]]
A div wiki-processor can be used for divs. The only syntax extension
needed here would be to accept macro arguments in block expression
(something that we wanted to have anyway in quite a number of other
situations):
{{{
#!div(NOTE)
This is something to consider when...
}}}
The syntax for passing arguments could either be the macro call one, or
named arguments, MIME-Type style, as this would better work for other
scenarios (e.g. #!python; annotate=linenum), or both of course.
-- 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
-~----------~----~----~----~------~----~------~--~---
