The first build of the 4.1 release has been posted and links can be
found on the download page.
https://woodstock.dev.java.net/Download.htm
This is the first build in the main trunk for Version 4.1. The Roadmap
page is still preliminary.
https://woodstock.dev.java.net/ProjectRoadmap.htm
I have attached updated Release Notes. We are still working on getting
the timing down with getting done in time for the build itself, but for
now I will likely be posting them either in the announcement or on the
download page. In any case, they are in the CVS tree now and you will
get them if you Update your workspace.
Thanks,
Woodstock Team
Woodstock 4.0 Components Release Notes
Woodstock 4.1 JSF Components Release Notes
4.1 Build 1 (03/23/2007)
New Features
- Client-side rendering for Image
- Client-side rendering for StaticText
- Client-side rendering for Label
- NetBeans Visual Web Pack module to enable updating the components in
NetBeans Visual Web Pack 5.5.x.
Bug Fixes
- Issue
#9 - onLoad/onUnLoad are broken
- CR 6527268 - JavaScript namespace is incorrect
- Issue
#6 - progressbar example fails - missing index.jsp
- NB Issue
#96990.
During static initialization of the class AutoSubmitOnChangeAction, a call
was made to JavaScriptUtilities.getMethodName(), which in turn tried to look
up the theme. The theme however is not on the class path at this time, which
is weird. As a work-around, I have moved the static initializer into a
getter method, so that the invocation is done lazily.
- NB Issue
# 97015 - CALENDAR: Renders poorly at runtime
- Issue
#15
Due to recent changes that unconditionally render a span for a complex
component that can have a "built in" label, resize functionality in Creator
for these components broke. More information on this issue can be seen
in CR 6519675. This CR resulted in the unconditional rendering of the
"span" as the containing element for complex components with built in
labels. Those changes are backed out.
- NB Issue
#97012
- Issue
#23 - CTS: CommonTaskRenderer is missing tr and td tags
- Issue
#24 - CommonTaskRenderer & CommonTasksSectionRenderer should use
writer.writeText()
- Issue
#25 - CTS: CommonTaskRenderer does not use ImageComponent or Icon
- Issue
#26 - Change the encoding of the url to client side.
- Issue
#50 - Design time for client side components needs to be fixed.
4.0.1 GA (02/15/2007)
IE7 Button width issue
When displayed in IE7, the button component might be rendered
with an incorrect width. This problem occurs when the button is placed
using absolute positioning.For example, Netbeans with
Visual Web Pack, uses absolute positioning to place components in Grid
Layout
Mode, and in such situation this problem could occur.
IE7 expects a value to be specified for the width of buttons. If
a width attribute is not specified, the width is set to width:auto,
which results in the button's width being set to the entire available
width of the button's container element. For example, if the
button
style has left=130px then the button will start at 130px left and will
expand to the width of the <body>.
Workarounds
There are several workarounds that can be used in the
developer's code to solve the problem.
- Specify the width attribute for the button, or resize
the button in the IDE to make the IDE assign a width to the button.
- Use relative positioning instead of absolute positioning on
the button component. For example:
<input name="Button2" style="position:relative; left:72px;top:18px" type="button" value="Button" />
- Enclose the button inside a div or span element to
restrict the available width to the div/span element's width. Remember
to
set the positioning for the div/span element.
- HTML Example 1: Button inside a div tag
<div style="position:absolute; left:72px; top:68px">
<input name="Button1" type="button" value="button" />
</div>
- HTML Example 2: Button inside span tag
<span style="position:absolute; left:72px; top:68px">
<input name="Button1" type="button" value="button" />
</span>
- In VWP IDE, drop the button into a Group Panel to put the
button inside a span tag. In this case no need to set the
positioning as IDE
sets the positioning for Group Panel.
- JSP Example: Button inside Group Panel component
<webuijsf:panelGroup binding="#{Page1.groupPanel1}" id="groupPanel1" style="position:absolute; left:240px; top:168px">
<webuijsf:button binding="#{Page1.button1}" id="button1" text="Button"/>
</webuijsf:panelGroup>