Announcing GWT 2.0 Milestone 1 - Google Web Toolkit

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Announcing GWT 2.0 Milestone 1
Received-SPF: pass (google.com: domain of joe.arcene...@gmail.com designates 209.85.210.178 as permitted sender) client-ip=209.85.210.178;
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=KVurHYkoVQb1QJkfKzFHNeBIbyUAfaq4zZk+Lz7hycTTwOm3+RCQ8TRuJmK0BgfFvs
         IOjkjIKJJ69Gu3jiJIzvQNIWMZtATYsAXXYufZg1sqRqd2BusjV41WicfQdtw6I11KsA
         xEeTcJwHzjeJak4tHO7SQNoExe/QMF0+UPP2w=
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="000e0cd5d0a285c33804755af50e"
In-Reply-To: <86bab137-8859-4fc2-87d6-6165b1586...@o9g2000prg.googlegroups.com>
References: <86bab137-8859-4fc2-87d6-6165b1586...@o9g2000prg.googlegroups.com>
Date: Wed, 7 Oct 2009 09:37:13 -0700
Message-ID: <6bbe977d0910070937lb87b704s432b2b86cea81...@mail.gmail.com>
Subject: Re: Announcing GWT 2.0 Milestone 1
From: Joseph Arceneaux <joe.arcene...@gmail.com>
To: google-web-toolkit@googlegroups.com

--000e0cd5d0a285c33804755af50e
Content-Type: text/plain; charset=UTF-8

May we presume that the Snow Leopard issue is now history?
Thanks,
Joe

On Mon, Oct 5, 2009 at 4:43 PM, Amit Manjhi <amitman...@google.com> wrote:

>
> Hi everyone,
>
> We are excited to release the first milestone build for GWT 2.0 today.
> This milestone provides early access (read: known to still be
> unfinished and buggy) to the various bits of core functionality that
> will be coming in GWT 2.0. Please download the bits from:
>
>
> http://code.google.com/p/google-web-toolkit/downloads/list?can=1&q=2.0+Milestone+1
>
>
> Things that are changing with GWT 2.0 that might otherwise be
> confusing without explanation
> * Terminology changes: We're going to start using the term
> "development mode" rather than the old term "hosted mode." The term
> "hosted mode" was sometimes confusing to people, so we'll be using the
> more descriptive term from now on. For similar reasons, we'll be using
> the term "production mode" rather than "web mode" when referring to
> compiled script.
>
> * Changes to the distribution: Note that there's only one download,
> and it's no longer platform-specific. You download the same zip file
> for every development platform. This is made possible by the new
> plugin approach used to implement development mode (see below). The
> distribution file does not include the browser plugins themselves;
> those are downloaded separately the first time you use development
> mode in a browser that doesn't have the plugin installed.
>
>
> Functionality that will be coming in GWT 2.0
> * In-Browser Development Mode: Prior to 2.0, GWT hosted mode provided
> a special-purpose "hosted browser" to debug your GWT code. In 2.0, the
> web page being debugged is viewed within a regular-old browser.
> Development mode is supported through the use of a native-code plugin
> for each browser. In other words, you can use development mode
> directly from Safari, Firefox, IE, and Chrome.
>
> * Code Splitting: Developer-guided code splitting allows you to chunk
> your GWT code into multiple fragments for faster startup. Imagine
> having to download a whole movie before being able to watch it. Well,
> that's what you have to do with most Ajax apps these days -- download
> the whole thing before using it. With code splitting, you can arrange
> to load just the minimum script needed to get the application running
> and the user interacting, while the rest of the app is downloaded as
> needed.
>
> * Declarative User Interface: GWT's UiBinder 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 use the new declarative UI.
>
> * Bundling of resources (ClientBundle): GWT has shipped with
> ImageBundles since GWT v1.4, giving developers 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.
>
> * Using HtmlUnit for running GWT tests: GWT 2.0 no longer uses SWT or
> the old mozilla code (on linux) to run GWT tests. Instead, it uses
> HtmlUnit as the built-in browser. HtmlUnit is 100% Java. This means
> there is a single GWT distribution for linux, mac, and windows, and
> debugging GWT Tests in development mode can be done entirely in a Java
> debugger.
>
>
> Known issues
> *  If you are planning to run the webAppCreator, i18nCreator, or the
> junitCreator scripts on Mac or Linux, please set their executable bits
> by doing a 'chmod +x *Creator'
> * Our HtmlUnit integration is still not complete. Additionally,
> HtmlUnit does not do layout. So tests can fail either because they
> exercise layout or they hit bugs due to incomplete integration. If you
> want such tests to be ignored on HtmlUnit, please annotate the test
> methods with @DoNotRunWith({Platform.Htmlunit})
> * The Google Eclipse Plugin 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.
>
>
> Breaking changes
> * The way arguments are passed to the GWT testing infrastructure has
> been revamped. There is now a consistent syntax to support arbitrary
> "runstyles", including user-written with no changes to GWT.  Though
> this does not affect common launch configs, some of the less common
> ones will need to be updated. For example, '-selenium FF3' has become
> '-runStyle selenium:FF3'
>
>
> As always, remember that GWT milestone builds like this are use-at-
> your-own-risk and we don't recommend it for production use. Please
> report any bugs you encounter to the GWT issue tracker (http://
> code.google.com/p/google-web-toolkit/issues/list) after doing a quick
> search to see if your issue has already been reported.
>
> -- Amit Manjhi, on behalf of the Google Web Toolkit team
> >
>

--000e0cd5d0a285c33804755af50e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

May we presume that the Snow Leopard issue is now history?<div><br></div><d=
iv>Thanks,</div><div>Joe<br><br><div class=3D"gmail_quote">On Mon, Oct 5, 2=
009 at 4:43 PM, Amit Manjhi <span dir=3D"ltr">&lt;<a href=3D"mailto:amitman=
j...@google.com">amitman...@google.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><br>
Hi everyone,<br>
<br>
We are excited to release the first milestone build for GWT 2.0 today.<br>
This milestone provides early access (read: known to still be<br>
unfinished and buggy) to the various bits of core functionality that<br>
will be coming in GWT 2.0. Please download the bits from:<br>
<br>
<a href=3D"http://code.google.com/p/google-web-toolkit/downloads/list?can=
=3D1&amp;q=3D2.0+Milestone+1" target=3D"_blank">http://code.google.com/p/go=
ogle-web-toolkit/downloads/list?can=3D1&amp;q=3D2.0+Milestone+1</a><br>
<br>
<br>
Things that are changing with GWT 2.0 that might otherwise be<br>
confusing without explanation<br>
* Terminology changes: We&#39;re going to start using the term<br>
&quot;development mode&quot; rather than the old term &quot;hosted mode.&qu=
ot; The term<br>
&quot;hosted mode&quot; was sometimes confusing to people, so we&#39;ll be =
using the<br>
more descriptive term from now on. For similar reasons, we&#39;ll be using<=
br>
the term &quot;production mode&quot; rather than &quot;web mode&quot; when =
referring to<br>
compiled script.<br>
<br>
* Changes to the distribution: Note that there&#39;s only one download,<br>
and it&#39;s no longer platform-specific. You download the same zip file<br=
>
for every development platform. This is made possible by the new<br>
plugin approach used to implement development mode (see below). The<br>
distribution file does not include the browser plugins themselves;<br>
those are downloaded separately the first time you use development<br>
mode in a browser that doesn&#39;t have the plugin installed.<br>
<br>
<br>
Functionality that will be coming in GWT 2.0<br>
* In-Browser Development Mode: Prior to 2.0, GWT hosted mode provided<br>
a special-purpose &quot;hosted browser&quot; to debug your GWT code. In 2.0=
, the<br>
web page being debugged is viewed within a regular-old browser.<br>
Development mode is supported through the use of a native-code plugin<br>
for each browser. In other words, you can use development mode<br>
directly from Safari, Firefox, IE, and Chrome.<br>
<br>
* Code Splitting: Developer-guided code splitting allows you to chunk<br>
your GWT code into multiple fragments for faster startup. Imagine<br>
having to download a whole movie before being able to watch it. Well,<br>
that&#39;s what you have to do with most Ajax apps these days -- download<b=
r>
the whole thing before using it. With code splitting, you can arrange<br>
to load just the minimum script needed to get the application running<br>
and the user interacting, while the rest of the app is downloaded as<br>
needed.<br>
<br>
* Declarative User Interface: GWT&#39;s UiBinder now allows you to create<b=
r>
user interfaces mostly declaratively. Previously, widgets had to be<br>
created and assembled programmatically, requiring lots of code. Now,<br>
you can use XML to declare your UI, making the code more readable,<br>
easier to maintain, and faster to develop. The Mail sample has been<br>
updated to use the new declarative UI.<br>
<br>
* Bundling of resources (ClientBundle): GWT has shipped with<br>
ImageBundles since GWT v1.4, giving developers automatic spriting of<br>
images. ClientBundle generalizes this technique, bringing the power of<br>
combining and optimizing resources into one download to things like<br>
text files, CSS, and XML. This means fewer network round trips, which<br>
in turn can decrease application latency -- especially on mobile<br>
applications.<br>
<br>
* Using HtmlUnit for running GWT tests: GWT 2.0 no longer uses SWT or<br>
the old mozilla code (on linux) to run GWT tests. Instead, it uses<br>
HtmlUnit as the built-in browser. HtmlUnit is 100% Java. This means<br>
there is a single GWT distribution for linux, mac, and windows, and<br>
debugging GWT Tests in development mode can be done entirely in a Java<br>
debugger.<br>
<br>
<br>
Known issues<br>
* =C2=A0If you are planning to run the webAppCreator, i18nCreator, or the<b=
r>
junitCreator scripts on Mac or Linux, please set their executable bits<br>
by doing a &#39;chmod +x *Creator&#39;<br>
* Our HtmlUnit integration is still not complete. Additionally,<br>
HtmlUnit does not do layout. So tests can fail either because they<br>
exercise layout or they hit bugs due to incomplete integration. If you<br>
want such tests to be ignored on HtmlUnit, please annotate the test<br>
methods with @DoNotRunWith({Platform.Htmlunit})<br>
* The Google Eclipse Plugin will only allow you to add GWT release<br>
directories that include a file with a name like gwt-dev-windows.jar.<br>
You can fool it by sym linking or copying gwt-dev.jar to the<br>
appropriate name.<br>
<br>
<br>
Breaking changes<br>
* The way arguments are passed to the GWT testing infrastructure has<br>
been revamped. There is now a consistent syntax to support arbitrary<br>
&quot;runstyles&quot;, including user-written with no changes to GWT. =C2=
=A0Though<br>
this does not affect common launch configs, some of the less common<br>
ones will need to be updated. For example, &#39;-selenium FF3&#39; has beco=
me<br>
&#39;-runStyle selenium:FF3&#39;<br>
<br>
<br>
As always, remember that GWT milestone builds like this are use-at-<br>
your-own-risk and we don&#39;t recommend it for production use. Please<br>
report any bugs you encounter to the GWT issue tracker (http://<br>
<a href=3D"http://code.google.com/p/google-web-toolkit/issues/list" target=
=3D"_blank">code.google.com/p/google-web-toolkit/issues/list</a>) after doi=
ng a quick<br>
search to see if your issue has already been reported.<br>
<font color=3D"#888888"><br>
-- Amit Manjhi, on behalf of the Google Web Toolkit team<br>
<br>
</font></blockquote></div><br></div>

--000e0cd5d0a285c33804755af50e--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
