On 10/23/06, Christopher Lenz <[EMAIL PROTECTED]> wrote:
> It's a solution because it solves the problem at hand. Sure it's not
> optimal, that's why I wrote "I personally think that's an okay trade-
> off to make".

That's rather wide definition of a solution :-).

> The alternative would be to keep all the wiki_to_xxx() invocations in
> the controller code. That's an option I don't find attractive. Moving
> them into templates would have the following benefits:

Not necessarily. Parsing the wiki text for just macros and
preprocessors (I think it would be a fast and rather simple task) in
code and doing the rest of the work in template is also a possibility.
That's what I meant by not going the all-or-nothing route.

Sergey.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to