Re: [cowiki-dev] The new coWiki parser

John (yt) Hogenmiller wrote:

>Ahh... well, in that case, I misunderstood you.  
>
Wouldn't be the first time I've been misunderstood!  <G>

>I think a few people know how the parser *works*, but reliably
>modifying pretty much the only thing in the project that isn't a
>plugin is in fact a major undertaking in any project. 
>
Agreed!

>Recently, I have
>been thinking that it could be possible to /move/ the parser out from
>core and adding alternative parsers to the mix, choosing your parser
>in the configuration.  However, once you have documents created, you
>couldn't just "switch" parsers and expect all of your documents to
>work as before (of course, if one parser is expected to behave exactly
>the same as the other, you could expect it).  I don't want to
>experiment with that until after the next release.
>  
>
This is a lot like I was once upon a time proposing, and I think it has 
some merit.  But I'm concerned that it is in fact complicated for the 
user.  And there were potential security issues pointed out previously 
by others.  Basically I think you need to specify which tools you will 
grant to particular users.  Great if you're a control or process freak, 
but difficult to manage if you have many users of different types.

OTOH, I do like the notion of positioning coWiki as an access engine 
into which you can plug different sorts of language plugins for 
different purposes.  In some ways, this should be a very easy thing to do.