Done. It is now org.icefaces.component.utils.ScriptWriter.

Need to move this into the Sparkle platform (out of the std. bridge) as a new utility API. Please review and complete the move.

Introduced ScriptWriter utility class to eliminate component renderer boiler plate code when writing script code to be evaluated on the client.

There are two ways to write (and eventually evaluate) JS code.

Calling ScriptWriter.insertScript(FacesContext , UIComponent, String) allows the component renderer to write the script markup and code in one method call. This method is useful when the JS code complexity is low. For example:

public void encodeEnd(FacesContext context, UIComponent component) throws IOException

The other method of writing the JS code allows writing the code gradually by streaming it directly through the response writer. This method can be used when the complexity of JS code is higher. For example:

public void encodeBegin(FacesContext facesContext, UIComponent uiComponent) throws IOException {
....
ScriptWriter writer = ScriptWriter.insertScript(facesContext, uiComponent);
writer.startScript();
writer.write("ice.yui3.slider.updateProperties('");
writer.write(clientId);
writer.write("', ");
//pass through YUI slider properties
writer.write("

);");
writer.endScript();
}

This is the pattern of HTML elements for the commandLink component.

<div id="clientId" >
<span id="clientId" + "_span" class="yui-button yui-link-button" >
<span id="clientId" + "_s2" class="first-child" >
<a id="cliendId" + "_anchor" actionListener="..." href="..." etc>
</span>
</span>
<span id="clientId" + "_js">
<script ...>
yadda
</script>
</span>
</div>

The first two spans are necessary for the YUI toolkit to find and replace our stuff. The third span is useful to wrap the script with id so it can be replaced independent of the component.