Announcing GWT 2.0.1

[Miguel Méndez]

The GWT 2.0.1 point release is now available for download. It contains fixes for bugs found in the 2.0.0 release.

Potentially breaking changes and fixes

• Fixed a bug in how code generators collect method arguments from generated source, which impacted the Messages interfaces generated for UiBinder template files. In GWT 2.0, such argument names were incorrectly changed to ARGn. Most GWT applications will be unaffected, but external systems relying on these names may need to be updated.
• The development mode server will, by default, only bind to localhost which will break cross-machine debugging. You can get the old behavior by specifying -bindAddress 0.0.0.0. Please see issue (#4322) for more details. For webAppCreator-generated ant files, you can pass this with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode.
• The CurrencyList/CurrencyData APIs are now public - if you were relying upon these classes in their non-public location, you should only need to update your imports.

Noteworthy Fixed Issues

• UiBinder Image class with resource attribute, removes styles on that image (#4415)
• Widgets lose focus if its placed on FocusPanel (Opera, Safari) (#1471)
• Standard.css missing new layout styles (#4429)
• Remove method in SplitLayoutPanel is broken (#4217)
• Splitter constructor hard codes the background color of the splitter to white (#4335)
• Image should provide method to set alternative text (#4335)
• CssResource cannot parse unescaped '-', '_' in class selectors and unknown at-rules (#3946)
• Focusable implementation breaks ScrollPanels in Safari (#1313)
• RequestBuilder restricted to GET and POST (#3388)
• HTMLTable.Cell.getElement() calls getCellFormatter().getElement() with row and column swapped RequestBuilder restricted to GET and POST (#3757)
• MenuBar steals focus when hovered (#3884)
• TabLayoutPanel tabs don't line up properly on IE (#4447)
• webAppCreator produces ant build files which support the gwt.args property for passing additional flags to the gwtc and devmode rules, such as ant -Dgwt.args="-style PRETTY" gwtc.

See the GWT issue tracker for the complete list of bug fixes and enhancements in this release.

--

Miguel on behalf of the GWT Team

[jarrod]

Hey great job! Thanks a mil!

On Feb 2, 9:01 pm, Miguel Méndez <mmen...@google.com> wrote:
> The GWT 2.0.1 point release is now available for download. It contains fixes
> for bugs found in the 2.0.0 release.
>
> Potentially breaking changes and fixes
>

>    - Fixed a bug in how code generators collect method arguments from

>    generated source, which impacted the Messages interfaces generated for
>    UiBinder template files. In GWT 2.0, such argument names were incorrectly
>    changed to ARGn. Most GWT applications will be unaffected, but external
>    systems relying on these names may need to be updated.

>    - The development mode server will, by default, only bind to localhost

>    which will break cross-machine debugging. You can get the old behavior by
>    specifying -bindAddress 0.0.0.0. Please see issue

> (#4322<http://code.google.com/p/google-web-toolkit/issues/detail?id=4322>)

>    for more details. For webAppCreator-generated ant files, you can pass this
>    with ant -Dgwt.args="-bindAddress 0.0.0.0" devmode.

>    - The CurrencyList/CurrencyData APIs are now public - if you were relying

>    upon these classes in their non-public location, you should only need to
>    update your imports.
>
> Noteworthy Fixed Issues
>

>    - UiBinder Image class with resource attribute, removes styles on that
>    image (#4415<http://code.google.com/p/google-web-toolkit/issues/detail?id=4415>
>    )
>    - Widgets lose focus if its placed on FocusPanel (Opera, Safari)
> (#1471<http://code.google.com/p/google-web-toolkit/issues/detail?id=1471>
>    )
>    - Standard.css missing new layout styles
> (#4429<http://code.google.com/p/google-web-toolkit/issues/detail?id=4429>
>    )
>    - Remove method in SplitLayoutPanel is broken
> (#4217<http://code.google.com/p/google-web-toolkit/issues/detail?id=4217>
>    )
>    - Splitter constructor hard codes the background color of the splitter to
>    white (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
>    )
>    - Image should provide method to set alternative text
> (#4335<http://code.google.com/p/google-web-toolkit/issues/detail?id=4335>
>    )
>    - CssResource cannot parse unescaped '-', '_' in class selectors and
>    unknown at-rules
> (#3946<http://code.google.com/p/google-web-toolkit/issues/detail?id=3946>
>    )
>    - Focusable implementation breaks ScrollPanels in Safari
> (#1313<http://code.google.com/p/google-web-toolkit/issues/detail?id=1313>
>    )
>    - RequestBuilder restricted to GET and POST
> (#3388<http://code.google.com/p/google-web-toolkit/issues/detail?id=3388>
>    )
>    - HTMLTable.Cell.getElement() calls getCellFormatter().getElement() with

>    row and column swapped RequestBuilder restricted to GET and POST

> (#3757<http://code.google.com/p/google-web-toolkit/issues/detail?id=3757>
>    )
>    - MenuBar steals focus when hovered
> (#3884<http://code.google.com/p/google-web-toolkit/issues/detail?id=3884>
>    )
>    - TabLayoutPanel tabs don't line up properly on IE
> (#4447<http://code.google.com/p/google-web-toolkit/issues/detail?id=4447>
>    )
>    - webAppCreator produces ant build files which support the gwt.args

>    property for passing additional flags to the gwtc and devmode rules, such as
>    ant -Dgwt.args="-style PRETTY" gwtc.
>
> See the GWT issue tracker for the complete list of bug fixes and

> enhancements<http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...>

[Arthur Kalmenson]

Great job! Some nice bug squishing.

--
Arthur Kalmenson

2010/2/2 Miguel Méndez <mme...@google.com>:

> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors

[John LaBanca]

Another important change that we forgot to mention is that new applications created by webAppCreator now default to standards mode instead of quirks mode.

This makes it easier for new apps to take advantage of the new LayoutPanels, introduced in GWT 2.0, which only work in standards mode.  However, there are some widgets, such as StackPanel, which generally do not work in standards mode.  You can look at a widget's JavaDoc to see if it only work in standards mode or quirks mode.

If you use the Google Plugin for Eclipse to run JUnit tests for your project, you will need to pass in the "-standardsMode" compiler argument to run them in standards mode.  This has always been true, but its especially important now that new apps default to standards mode.  The plugin team is working on changes to make this easier to do.

1. Open Run/Debug Configurations.
2. Select your GWT JUnit test.
3. Click on the Arguments tab.
4. Add the following to the VM arguments:
   -Dgwt.args="-out www-test -standardsMode"
   
   Note that gwt.args replaces all gwt specific arguments in the "GWT JUnit" tab, so you need to pass the output directory, log level, output style, and production mode settings if you want to use non-default values for these fields.  In the above example, you can see that we pass the output directory as www-test.
5. Run your test.

Thanks,
John LaBanca
jlab...@google.com

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors