> Just had a question/idea while creating a new tw page and installing
> the great nested slider plugin.

> What if I install a plugin that uses the wiki markup beginning with +++
> + to do something, but that markup is already "taken" by another
> plugin I already installed or may install in future?

> In other words how to make markup extensible?   Or is this not a
> problem?

> Anyway, my solution is to allow the switching of markup namespace.
> Just before I use the '+++' markup and its possible end markup, I
> indicate which plugin namespace it should use, and allow nesting of
> namespaces.  The default namespace is TW's.

> --- Josef

> A markup clash like that has only come up once that I'm aware of
> (relating to some slider syntax, in fact), and the plugin authors
> sorted it out so that there was no clash.  I guess any future problems
> will be resolved the same way.

> Cheers
> ;Daniel

> On Thu, Jul 3, 2008 at 1:13 AM, Josef <josef.betanco...@gmail.com> wrote:

> > Just had a question/idea while creating a new tw page and installing
> > the great nested slider plugin.

> > What if I install a plugin that uses the wiki markup beginning with +++
> > + to do something, but that markup is already "taken" by another
> > plugin I already installed or may install in future?

> > In other words how to make markup extensible?   Or is this not a
> > problem?

> > Anyway, my solution is to allow the switching of markup namespace.
> > Just before I use the '+++' markup and its possible end markup, I
> > indicate which plugin namespace it should use, and allow nesting of
> > namespaces.  The default namespace is TW's.

> > --- Josef

> --
> Daniel Baird
> /to be or not to be/ => /(2b|[^2]b)/ => /(2|[^2])b/ => /.b/
> ...optimise your regexes, people!