The scripting and stylesheet extensions in pre-1_0-cleanup require a lot 
of changes to the CGs:

o the component's ids have to be written to make the components 
  addressable by scripts
o the styles, that are defined in the component's attribute set are 
  written to the dynamic stylesheet. They address the target component
  using the "#"-selector (by id).

the button cg may render the following code, if the button has a text but 
no icon:

href && enabled:

  <a href="blubber" id="${id}" ...>
    <span id="s_${id}"
          class="${style_class}"
          style="${inline}">
      ${text}
    </span>
  </a>

form && enabled:

  <span id="s_${id}"
        class="${style_class}"
        style="${inline}">
      <input type="submit"
             id="${id}"
             name="${nameprefix}"
             value="${text}"/>
  </span>

disabled:

  <span id="${id}" ...>
    <span id="s_${id}"
          class="${style_class}"
          style="${inline}">
      ${text}
    </span>
  </span>


Some weeks ago, we decided to use different id attributes for scripting 
and styling. Does somebody remember, why? We could save lots of spans, if 
we wouldn't ..

We still have a problem with cell renderers. The ids of a cell renderer 
component must not be written for every cell, because the ids have to be 
unique. Either we need a way to switch off ids or some counter mechanism.
I tend to the latter. The counter has to be reset before every code 
generation traversal and there has to be a counter for every component, 
that uses cell renderers. Imagine a table:

id.0 | id.1 | id.2
-----+------+-----
id.3 | id.4 | id.5

How can we achieve this? Any ideas? We need something like a code 
generation context, do we?


BTW: I'd rather make all these changes to the jsp plafs .. when can we 
bargain for the compiler?

Holger


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to