On Dec 16, 2010, at 12:04 PM, Vincent Massol wrote:
On Dec 16, 2010, at 11:56 AM, Ecaterina Moraru (Valica) wrote:
Not sure what we are talking about, but can't we use http://extensions.xwiki.org/xwiki/bin/view/Extension/Include+Macro
with context=current?
That's a bit different since context=new creates a new context (context=current doesn't do anything).
or make the {{current}} macro a new parameters for the {{include}} ?
Yes i thought about adding a new param to the include macro but that won't solve the the second use case listed below.
We could have both though: a param for include + that macro for other use cases.
Since there's a good portion of code shared with the include macro, we could have the include macro either extend or use that new macro too. Thanks -Vincent
However Thomas raised a good question which we need to answer before we go further.
Thanks -Vincent
Thanks, Caty
On Thu, Dec 16, 2010 at 12:51, Thomas Mortagne <[email protected]>wrote:
On Thu, Dec 16, 2010 at 11:42, Vincent Massol <[email protected]> wrote:
Hi devs,
I'd like to propose a new macro (not sure how to call it): {{current}}
Usage:
{{current document="wiki:space.page"}} .... nested blocks.... {{/current}}
What it does:
* Execute the nested blocks in the context of the passed document, i.e. it sets the passed document as the current document in the execution context.
So that means "current" macro will execute itself the transformations for its content ? What would be the priority of "current" macro in this case ?
Rationale:
* We have several use cases: ** When we have an include and we want to use relative references (links,
images) in the included document
** On the Features page of enterprise.xwiki.org I query extensions.xwiki.org and get the data from one object field which has the format: "attach:...." (or "url:....", etc). I need to make this an image that is resolved based on the page where the information was taken from.
WDYT?
Thanks -Vincent