Thorsten Scherler wrote:
...
> <forrest:hook name="testIdDiv"/>
> *or*
> <forrest:hook name="testIdDiv" type="div"/>
> will be transformed into
> <div name="testIdDiv" />
Then why not simply use
<div name="testIdDiv" />
> The same is true for @class attribute for forrest:hooks.
> <forrest:hook class="testClassDiv"/>
> *or*
> <forrest:hook class="testClassDiv" type="div"/>
> will be transformed into
> <div class="testClassDiv" />
Then why not simply use:
<div class="testClassDiv" />
> Another feature is that you can as well output span elements for
> forrest:hooks instead of div elements.
> <forrest:hook name="testId" type="span"/>
> will be transformed into
> <span id="testId" />
Then why not simply use
<span id="testId" />
...
> Here is a small summary example:
> <forrest:hook class="testClass" type="span" nbsp="true"/>
> <forrest:hook name="testId" type="span"/>
> <forrest:hook class="testClassDiv" />
> <forrest:hook name="testIdDiv" type="div" nbsp="true"/>
>
> will be transformed to:
>
> <span class="testClass"> </span>
> <span id="testId" />
> <div class="testClassDiv" />
> <div id="testIdDiv"> </div>
Again, why cannot we use the second version instead of creating another
new language?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
