Thx for taking the time off your heavy schedule for the reply Jason. :-)
Jason, below are some of my limited undestanding of the components. Please do
correct me if there's any slightest mistakes.
- Checkbox group
I guess this something like the current <@ww.radio ..../> tag where one could
specified a list or a map that gets render as checkboxes.
- Tabbed Panel and Panel
Is this like what WW currently have? Where tabbped panel and panel are
rendered as divs and styled using css. Remote capabilities is done through dojo.
- Wizard and wizard step
Is this something like ....
<@ww.wizard ....>
<@ww.wizardstep .... >
<@ww.wizardstep>
<@ww.wizardstep ....>
<!-- this is step two ... ->
</@ww.wizardstep>
</@ww.wizard>
such that when this tag is render it will follow through step 1 to 2. Does it
used any backing bean that could be included in the tag such that logic of
determining if the next step should be achieved etc? How does way of doing
wizarding compared to scope interceptor or does it uses scope interceptor as
well.
- Table and column
Is this something like displaytag? There's some code in WW about rendering
table component. Is it based on that?
Thanks again Jason.
----- Original Message ----
From: Jason Carreira <[EMAIL PROTECTED]>
To: dev@struts.apache.org
Sent: Friday, 14 July, 2006 2:57:39 AM
Subject: Re: [s2] possible component tags
Well, the tree was the most complicated one, and we did contribute that one.
Other than that it's the common stuff:
* Checkbox group
* Tabbed Panel and Panel
* Wizard and Wizard Step
* Table and Column
Along with custom templates for the other UI tags for things like in-page
callbacks before a form is submitted, etc.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=37315&messageID=73204#73204
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
