Revision: 7193
Author: [email protected]
Date: Wed Nov 25 12:51:41 2009
Log: Edited wiki page through web user interface.
http://code.google.com/p/google-web-toolkit/source/detail?r=7193

Modified:
  /wiki/GWT_2_0_RC.wiki

=======================================
--- /wiki/GWT_2_0_RC.wiki       Wed Nov 18 09:08:21 2009
+++ /wiki/GWT_2_0_RC.wiki       Wed Nov 25 12:51:41 2009
@@ -1,17 +1,21 @@
-#summary Getting Started with the GWT 2.0 Release Candidate
-
-= Getting Started with GWT 2.0 RC1 =
+#summary Getting Started with the GWT 2.0 Release Candidates
+
+= Getting Started with the GWT 2.0 Release Candidates =

  <i>
-Before using GWT 2.0 RC1, please understand that it is still a release  
candidate and will likely change before its official release.
-We do not recommend using this release candidate build for production  
applications.
+Before using GWT 2.0 RC2 or RC1, please understand that they are release  
candidates and will change before the official release.
+We do not recommend using these release candidate builds for production  
applications.
  </i>

  This release contains big changes to improve developer productivity, make  
cross-browser development easier, and produce faster web applications.

-== Downloading and Installing GWT 2.0 RC1 SDK ==
+== Downloading and Installing GWT 2.0 RC SDKs ==
  No installation process is required to use the GWT SDK; simply unzip it  
into any convenient directory.

+<blockquote>
+<a  
href="http://google-web-toolkit.googlecode.com/files/gwt-2.0.0-rc2.zip";>Download
  
GWT 2.0 RC2</a>
+</blockquote>
+
  <blockquote>
  <a  
href="http://google-web-toolkit.googlecode.com/files/gwt-2.0.0-rc1.zip";>Download
  
GWT 2.0 RC1</a>
  </blockquote>
@@ -19,12 +23,18 @@
  The new debugging support in GWT 2.0, called Development Mode, requires a  
native browser plugin that will be installed on-demand as you use GWT.
  See "Getting Started with Development Mode" below for step-by-step  
instructions for this process.

-== Downloading and Installing the Google Plugin for Eclipse 1.2 RC1 ==
+== Downloading and Installing the Google Plugin for Eclipse 1.2 RCs ==
  Google Plugin for Eclipse 1.2 RC1 includes functionality to support the  
new features in GWT 2.0, so if you're an Eclipse users, we highly recommend  
installing it as well.

  === Installation Instructions ===
  Download the Google Plugin for Eclipse 1.2.0 Release Candidate zip  
distributions for your version of Eclipse:

+==== RC2 ====
+  * 3.5 (Galileo): <a  
href="http://dl.google.com/eclipse/plugin/3.5/zips/gpe-e35-1.2rc2.zip";>http://dl.google.com/eclipse/plugin/3.5/zips/gpe-e35-1.2rc2.zip</a>
+  * 3.4 (Ganymede) <a  
href="http://dl.google.com/eclipse/plugin/3.4/zips/gpe-e34-1.2rc2.zip";>http://dl.google.com/eclipse/plugin/3.4/zips/gpe-e34-1.2rc2.zip</a>
+  * 3.3 (Europa): <a  
href="http://dl.google.com/eclipse/plugin/3.3/zips/gpe-e33-1.2rc2.zip";>http://dl.google.com/eclipse/plugin/3.3/zips/gpe-e33-1.2rc2.zip</a>
+
+==== RC1 ====
    * 3.5 (Galileo): <a  
href="http://dl.google.com/eclipse/plugin/3.5/zips/gpe-e35-1.2rc1.zip";>http://dl.google.com/eclipse/plugin/3.5/zips/gpe-e35-1.2rc1.zip</a>
    * 3.4 (Ganymede) <a  
href="http://dl.google.com/eclipse/plugin/3.4/zips/gpe-e34-1.2rc1.zip";>http://dl.google.com/eclipse/plugin/3.4/zips/gpe-e34-1.2rc1.zip</a>
    * 3.3 (Europa): <a  
href="http://dl.google.com/eclipse/plugin/3.3/zips/gpe-e33-1.2rc1.zip";>http://dl.google.com/eclipse/plugin/3.3/zips/gpe-e33-1.2rc1.zip</a>
@@ -69,6 +79,11 @@
  GWT's <a  
href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/uibinder/client/UiBinder.html";>!UiBinder</a>
  
now allows you to create  user interfaces mostly declaratively. Previously,  
widgets had to be created and assembled programmatically, requiring lots of  
code. Now, you can use XML to declare your UI, making the code more  
readable, easier to maintain, and faster to develop. The Mail sample has  
been updated to show a practical example of using !UiBinder.
  </dd>

+<dt>New Layout Panels for Fast and Predictable Layout</dt>
+<dd>
+A number of new panels were added, which together form a stable basis for  
fast and predictable application-level layout. The official doc is still in  
progress, but for an overview please see <a  
href="http://code.google.com/p/google-web-toolkit/wiki/LayoutDesign";>Layout  
Design</a> on the wiki. The new set of panels includes <a  
href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/client/ui/RootLayoutPanel.html";>RootLayoutPanel</a>,
  
<a  
href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/client/ui/LayoutPanel.html";>LayoutPanel</a>,
  
<a  
href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/client/ui/DockLayoutPanel.html";>DockLayoutPanel</a>,
  
<a  
href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/client/ui/SplitLayoutPanel.html";>SplitLayoutPanel</a>,
  
<a  
href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/client/ui/StackLayoutPanel.html";>StackLayoutPanel</a>,
  
and <a  
href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/client/ui/TabLayoutPanel.html";>TabLayoutPanel</a>.
+</dd>
+
  <dt>Bundling of Resources via <a  
href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/resources/client/ClientBundle.html";>!ClientBundle</a></dt>
  <dd>
  GWT introduced <a  
href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.0/com/google/gwt/user/client/ui/ImageBundle.html";>!ImageBundle</a>
  
in 1.4 to provide automatic spriting of images. !ClientBundle generalizes  
this technique, bringing the power of combining and optimizing resources  
into one download to things like text files, CSS, and XML. This means fewer  
network round trips, which in turn can decrease application latency --  
especially on mobile applications.
@@ -145,6 +160,13 @@
  You can open any number of additional browsers to ensure your application  
behaves properly across browsers.

  === Breaking changes and known issues/bugs/problems ===
+  * Windows users who have previously installed the Google Web Toolkit  
Developer Plugin for IE will have to uninstall the old version. Use the  
following steps:
+    1 From the Windows "Start" Menu, open "Control Panel"
+    1 Select "Add/Remove Programs"
+    1 Select "Google Web Toolkit Developer Plugin for IE" then  
click "Uninstall"
+    1 Run Internet Explorer and browse to <a  
href="http://gwt.google.com/samples/MissingPlugin";>http://gwt.google.com/samples/MissingPlugin</a>
  
to install the new version of the plugin.
+  * The -portHosted Development Mode flag has been renamed to  
-codeServerPort.
+  * The release notes included with RC2 contain one inaccuracy: the  
Image.onload event still does not fire on Internet Explorer when image is  
in cache.  See issue <a  
href="http://code.google.com/p/google-web-toolkit/issues/detail?can=2&q=863";>863</a>
  
for more details.
    * Prior to 2.0, GWT tools such as the compiler were provide in a  
platform-specific jar (that is, with names like `gwt-dev-windows.jar`). As  
of 2.0, GWT tools are no longer platform specific and they reside in  
generically-named `gwt-dev.jar`. You are quite likely to have to update  
build scripts to remove the platform-specific suffix, but that's the extent  
of it.
    * The development mode entry point has changed a few times since GWT  
1.0. It was originally called `GWTShell`, and in GWT 1.6 a replacement  
entry point called `HostedMode` was introduced. As of GWT 2.0, to reflect  
the new "development mode" terminology, the new entry point for development  
mode is `com.google.gwt.dev.DevMode`. Sorry to keep changing that on ya,  
but the good news is that the prior entry point still works. But, to really  
stay current, we recommend you switch to the new `DevMode` entry point.
    * Also due to the "development mode" terminology change, the name of the  
ant build target produced by `webAppCreator` has changed from `hosted` to  
`devmode`. In other words, to start development mode from the command-line,  
type `ant devmode`.
@@ -152,4 +174,3 @@
    * Versions of Google Plugin for Eclipse prior to 1.2 will only allow you  
to add GWT release directories that include a file with a name like  
`gwt-dev-windows.jar`. You can fool it by sym linking or copying  
gwt-dev.jar to the appropriate name.
    * The way arguments are passed to the GWT testing infrastructure has  
been revamped. There is now a consistent syntax to support arbitrary "run  
styles", including user-written, with no changes to GWT itself. For  
example, `-selenium FF3` has become `-runStyle selenium:FF3`. This change  
likely does not affect typical test invocation scripts, but if you do use  
`-Dgwt.args` to pass arguments to GWTTestCase, be aware that you may need  
to make some changes.
    * When using !ClientBundle, be aware that images using alpha  
transparency do not appear transparent in IE6. The Mail sample application  
included in the GWT distribution currently suffers from this limitation  
(that is, the images have opaque backgrounds when viewed on IE6).
-  * Users of the Google Plugin for Eclipse that are running Google App  
Engine projects in development mode may see errors like "Unable to  
find 'myapp.gwt.xml' on your classpath; could be a typo, or maybe you  
forgot to include a classpath entry for source?". (Note that the app name  
has been cast to lowercase, that's a symptom.) This is due to an  
unfortunate interaction between weak references to module definitions and  
garbage collection kicked off by the App Engine.

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

Reply via email to