Nicola Ken Barozzi a écrit :
Thorsten Scherler wrote:
...
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?
I agree with Nicola, the notation becomes a little complicated just to
add a div or a span...
Furthermore, I had big problem with empty <div/> tags which are not well
interpreted by browsers (Firefox and IE at least)
So why don't we automates the <div> </div> generation if the tag is empty ?
Salutations,
Cyriaque,
