Re: CompileBL Scenario

[email protected] wrote:

> The purpose of the scenario com.xaraya.core.jamaica.compilebl is to make 
> it easier to add and remove custom tags. Currently the Blocklayout 
> compiler takes into account tags by having them included through hard 
> coded <xsl:include /> tags in the xsl stylesheet that transforms 
> templates from source to compiled versions.
> 
> This scenario introduces a prior transformation, in which the 
> <xsl:include /> tags are created dynamically. The transformation found 
> at lib/blocklayout/xslt/booter.xsl adds any xsl tag found in 3 directories:
> 
> lib/blocklayout/xslt/defaults
> lib/blocklayout/xslt/tags/bl
> lib/blocklayout/xslt/tags/xaraya
> 
> [The latter 2 directories are new. In addition, the debug.xsl 
> transformation has been moved to a new directory 
> lib/blocklayout/xslt/debug to avoid it being loaded automatically.]
> 
> The thinking here is that in the future, when a module installs, any 
> custom tags it has defined should be moved to 
> lib/blocklayout/xslt/tags/xaraya. Of course, we still need to implement 
> such a mechanism. At present this would need to be done manually. Any 
> ideas as to where we should park say the <xar:articles /> tag in the 
> odule's directory structure?

[module]/xartags/[tag].xsl seems appropriate to me.