[pmwiki-users] Planning for 2.2.0

Henrik Bechmann henrik.bechmann at sympatico.ca
Fri Sep 22 14:16:58 CDT 2006

I see, so the problem has to do with unqualified values.

So for argument's sake if unqualified new text vars {!...} default to 
local scope, and {$...} and [[...]] default to global scope (ie same as 
now), and ".." means global and "." means local (consistent with 
relative directory notation) then one could write

{$.PageVar} local scope; {$PageVar} or {$..PageVar} global scope

[[.PageName]] local scope; [[..PageName]] or [[PageName]] global scope

{!TextVar}or {!.TextVar} local scope; {!..TextVar} global scope

or fully qualify them:

{Group.Page$PageVar}, [[Group.Page]], {Group.Page!TextVar}

Just brainstorming...

- Henrik

> The approach I'm looking at right now is to do a scan for
> {$...} and [[...]] text that isn't already fully qualified, 
> and fully qualify each before inserting them into the markup text.
> For example, if Group.ABC has things like
>     {$Name}  
>     [[link]]  
>     [[PmWiki/Foo]] 
>     WikiWord
>     {AnotherPage$:xyz}
> then these will be automatically converted to
>     {Group.ABC$Name}          
>     [[Group/link]]  
>     [[PmWiki/Foo]]               # note, unchanged, already fully qualified
>     Group/WikiWord               # changed only if wikiwords enabled
>     {Group.AnotherPage$:xyz}
> so that they're fully qualified when rendered.  And, of course,
> the conversion will know to honor [=...=] and [@...@] escapes, etc.
> Pm


Henrik Bechmann
Webmaster, www.dufferinpark.ca

More information about the pmwiki-users mailing list