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:
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
Fantastic.
Lots of great stuff there.
Particularly look forward to being able to use Firebug in
hos...development mode.
ClientBundle's sound cool, and should help speed up some stuff.
Although what I most want is the ability to dynamicaly load a bundle.
(so, for example, a client can change the whole theme of the a at
runtime by loading a single file)
Also, are Listeners still being used then? Or is it all Handlers now?
Because some widget libs haven't caught up yet. (Sliderbar on the
Incubator, for instance).
Cheers,
Thomas Wrobel
On Oct 6, 1:43 am, Amit Manjhi <amitman...@google.com> wrote:
> 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:
> 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
Congratulations! That was way faster than I expected, thanks for
getting this release out that early.
One remark: seems like the eclipse plugin is not accepting the current
release with the message after selecting the gwt-dev-ms1 folder that
gwt-dev-mac.jar (in my case) is missing. So I guess that a new eclipse
plugin version will have to handle that accordingly.
Domink
On 6 Okt., 12:49, Rakesh <rake...@gmail.com> wrote:
> Congratulations! That was way faster than I expected, thanks for
> getting this release out that early.
> One remark: seems like the eclipse plugin is not accepting the current
> release with the message after selecting the gwt-dev-ms1 folder that
> gwt-dev-mac.jar (in my case) is missing. So I guess that a new eclipse
> plugin version will have to handle that accordingly.
> Domink
> On 6 Okt., 12:49, Rakesh <rake...@gmail.com> wrote:
> > great release ... especially the declarative ui, download on demand
> > and multiple browsers piece!!! good going gwt team... you rock!!
as described in the link just copying gwt-dev.jar and renaming it to
gwt-dev-mac.jar tricks the eclipse plugin and let's you easily start
the OOPHM mode.
> On Tue, Oct 6, 2009 at 8:32 PM, Dominik Steiner <dominik.j.stei...@googlemail.com > > wrote:
> Congratulations! That was way faster than I expected, thanks for
> getting this release out that early.
> One remark: seems like the eclipse plugin is not accepting the current
> release with the message after selecting the gwt-dev-ms1 folder that
> gwt-dev-mac.jar (in my case) is missing. So I guess that a new eclipse
> plugin version will have to handle that accordingly.
> Domink
> On 6 Okt., 12:49, Rakesh <rake...@gmail.com> wrote:
> > great release ... especially the declarative ui, download on demand
> > and multiple browsers piece!!! good going gwt team... you rock!!
I just created an app with the M1 release and noticed that if you send
a Persistent Object up to the server save it, detach it and send it
back down, you don't get an error (This was admittedly a simple
object). Is this a new change in 2.0? If so, awesome and thanks. My
only question is why haven't I heard this was coming into 2.0
earlier?
Thanks,
Jeff
On Oct 6, 8:25 pm, Dominik Steiner <dominik.j.stei...@googlemail.com>
wrote:
> as described in the link just copying gwt-dev.jar and renaming it to
> gwt-dev-mac.jar tricks the eclipse plugin and let's you easily start
> the OOPHM mode.
> Dominik
> > Domink,
> > The post below may provide you with some information regarding this
> > issue:
> > On Tue, Oct 6, 2009 at 8:32 PM, Dominik Steiner <dominik.j.stei...@googlemail.com
> > > wrote:
> > Congratulations! That was way faster than I expected, thanks for
> > getting this release out that early.
> > One remark: seems like the eclipse plugin is not accepting the current
> > release with the message after selecting the gwt-dev-ms1 folder that
> > gwt-dev-mac.jar (in my case) is missing. So I guess that a new eclipse
> > plugin version will have to handle that accordingly.
> > Domink
> > On 6 Okt., 12:49, Rakesh <rake...@gmail.com> wrote:
> > > great release ... especially the declarative ui, download on demand
> > > and multiple browsers piece!!! good going gwt team... you rock!!
On Wed, Oct 7, 2009 at 10:21 AM, Power Bottom <larse...@gmail.com> wrote:
> I just created an app with the M1 release and noticed that if you send
> a Persistent Object up to the server save it, detach it and send it
> back down, you don't get an error (This was admittedly a simple
> object). Is this a new change in 2.0? If so, awesome and thanks. My
> only question is why haven't I heard this was coming into 2.0
> earlier?
> Thanks,
> Jeff
> On Oct 6, 8:25 pm, Dominik Steiner <dominik.j.stei...@googlemail.com>
> wrote:
> > Thanks Chris for the link,
> > as described in the link just copying gwt-dev.jar and renaming it to
> > gwt-dev-mac.jar tricks the eclipse plugin and let's you easily start
> > the OOPHM mode.
> > Dominik
> > > Domink,
> > > The post below may provide you with some information regarding this
> > > issue:
> > > On Tue, Oct 6, 2009 at 8:32 PM, Dominik Steiner <
> dominik.j.stei...@googlemail.com
> > > > wrote:
> > > Congratulations! That was way faster than I expected, thanks for
> > > getting this release out that early.
> > > One remark: seems like the eclipse plugin is not accepting the current
> > > release with the message after selecting the gwt-dev-ms1 folder that
> > > gwt-dev-mac.jar (in my case) is missing. So I guess that a new eclipse
> > > plugin version will have to handle that accordingly.
> > > Domink
> > > On 6 Okt., 12:49, Rakesh <rake...@gmail.com> wrote:
> > > > great release ... especially the declarative ui, download on demand
> > > > and multiple browsers piece!!! good going gwt team... you rock!!
> On Wed, Oct 7, 2009 at 10:21 AM, Power Bottom <larse...@gmail.com > <mailto:larse...@gmail.com>> wrote:
> I just created an app with the M1 release and noticed that if you send > a Persistent Object up to the server save it, detach it and send it > back down, you don't get an error (This was admittedly a simple > object). Is this a new change in 2.0? If so, awesome and thanks. My > only question is why haven't I heard this was coming into 2.0 > earlier?
> Thanks, > Jeff
> On Oct 6, 8:25 pm, Dominik Steiner > <dominik.j.stei...@googlemail.com > <mailto:dominik.j.stei...@googlemail.com>> > wrote: > > Thanks Chris for the link,
> > as described in the link just copying gwt-dev.jar and renaming > it to > > gwt-dev-mac.jar tricks the eclipse plugin and let's you easily > start > > the OOPHM mode.
> > Dominik
> > > Domink,
> > > The post below may provide you with some information regarding > this > > > issue:
> > > On Tue, Oct 6, 2009 at 8:32 PM, Dominik Steiner > <dominik.j.stei...@googlemail.com > <mailto:dominik.j.stei...@googlemail.com> > > > > wrote:
> > > Congratulations! That was way faster than I expected, thanks for > > > getting this release out that early.
> > > One remark: seems like the eclipse plugin is not accepting the > current > > > release with the message after selecting the gwt-dev-ms1 > folder that > > > gwt-dev-mac.jar (in my case) is missing. So I guess that a new > eclipse > > > plugin version will have to handle that accordingly.
> > > Domink
> > > On 6 Okt., 12:49, Rakesh <rake...@gmail.com > <mailto:rake...@gmail.com>> wrote: > > > > great release ... especially the declarative ui, download on > demand > > > > and multiple browsers piece!!! good going gwt team... you rock!!
> > On Wed, Oct 7, 2009 at 10:21 AM, Power Bottom <larse...@gmail.com
> > <mailto:larse...@gmail.com>> wrote:
> > I just created an app with the M1 release and noticed that if you send
> > a Persistent Object up to the server save it, detach it and send it
> > back down, you don't get an error (This was admittedly a simple
> > object). Is this a new change in 2.0? If so, awesome and thanks. My
> > only question is why haven't I heard this was coming into 2.0
> > earlier?
> > Thanks,
> > Jeff
> > On Oct 6, 8:25 pm, Dominik Steiner
> > <dominik.j.stei...@googlemail.com
> > <mailto:dominik.j.stei...@googlemail.com>>
> > wrote:
> > > Thanks Chris for the link,
> > > as described in the link just copying gwt-dev.jar and renaming
> > it to
> > > gwt-dev-mac.jar tricks the eclipse plugin and let's you easily
> > start
> > > the OOPHM mode.
> > > Dominik
> > > > Domink,
> > > > The post below may provide you with some information regarding
> > this
> > > > issue:
> > > > On Tue, Oct 6, 2009 at 8:32 PM, Dominik Steiner
> > <dominik.j.stei...@googlemail.com
> > <mailto:dominik.j.stei...@googlemail.com>
> > > > > wrote:
> > > > Congratulations! That was way faster than I expected, thanks for
> > > > getting this release out that early.
> > > > One remark: seems like the eclipse plugin is not accepting the
> > current
> > > > release with the message after selecting the gwt-dev-ms1
> > folder that
> > > > gwt-dev-mac.jar (in my case) is missing. So I guess that a new
> > eclipse
> > > > plugin version will have to handle that accordingly.
> > > > Domink
> > > > On 6 Okt., 12:49, Rakesh <rake...@gmail.com
> > <mailto:rake...@gmail.com>> wrote:
> > > > > great release ... especially the declarative ui, download on
> > demand
> > > > > and multiple browsers piece!!! good going gwt team... you rock!!
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:
> 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
I set GWT 2.0 as the SDK for my project and it changed to the new
Development Swing UI In-browser mode instead of the old hosted mode. I
placed the given URL in both FF3.5 and IE8 and neither auto installed
the required plugin. Since my app is already compiled it renders fine
but I cannot debug. I tried manually installing the correct plugins
from http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM yet
the server is either only serving the compiled files or something is
wrong with the plugin because I cannot debug; breakpoints are not hit.
Does anyone know what I am doing wrong?
On Oct 7, 11:37 am, Joseph Arceneaux <joe.arcene...@gmail.com> wrote:
> 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:
> > 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
There does not appear to be a nice URL I can point Eclipse 3.5 at in order
to install GWT 2.0 in the usual fashion. Nor, apparently, any instructions
about an alternate procedure.
It appears unclear on just where / how to merge the contents of the zip file
into an existing Eclipse integration; does anyone have a pointer to
documentation for this?
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:
> 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
> There does not appear to be a nice URL I can point Eclipse 3.5 at in order
> to install GWT 2.0 in the usual fashion. Nor, apparently, any instructions
> about an alternate procedure.
> It appears unclear on just where / how to merge the contents of the zip file
> into an existing Eclipse integration; does anyone have a pointer to
> documentation for this?
> 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:
> > 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
> On 7 Okt., 20:00, Joseph Arceneaux <joe.arcene...@gmail.com> wrote:
> > There does not appear to be a nice URL I can point Eclipse 3.5 at in
> order
> > to install GWT 2.0 in the usual fashion. Nor, apparently, any
> instructions
> > about an alternate procedure.
> > It appears unclear on just where / how to merge the contents of the zip
> file
> > into an existing Eclipse integration; does anyone have a pointer to
> > documentation for this?
> > 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:
> > > 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
I got some problem too with Eclipse and Snow Leopard. It's always asking me
to re-compile my application and I've done that a lot of times ! I was
trying to get it work with an active project.
On Thu, Oct 8, 2009 at 2:22 AM, Parvez Shah <parvezs...@gmail.com> wrote:
> Hi, I tried searching,but could not find any document regarding what all
> changes has been made in the API,
> do we get any new widget in 2.0
> any new annotation
> On Thu, Oct 8, 2009 at 7:38 AM, Dominik Steiner <
> dominik.j.stei...@googlemail.com> wrote:
>> Hi Jospeh,
>> did you consider to install the Google Plugin for eclipse?
>> You will even then run into problems, but reading through this post
>> On 7 Okt., 20:00, Joseph Arceneaux <joe.arcene...@gmail.com> wrote:
>> > There does not appear to be a nice URL I can point Eclipse 3.5 at in
>> order
>> > to install GWT 2.0 in the usual fashion. Nor, apparently, any
>> instructions
>> > about an alternate procedure.
>> > It appears unclear on just where / how to merge the contents of the zip
>> file
>> > into an existing Eclipse integration; does anyone have a pointer to
>> > documentation for this?
>> > 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:
>> > > 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
I created a new GWT web app with the Eclipse google plugin using GWT
2.0MS1 as the SDK. This is what most likely solved my problem. Simply
changing a project from GWT 1.7.1 to 2.0 must not be making all the
necessary changes to the auto generated files to be properly
compatible. Obviously this sort of thing will be ironed out for
release.
Then I needed to first launch (not a debug launch) the newly created
GWT web app (with the default app still intact). I tried this with a
browser that did not have the plugin installed (FF3.5) and when
navigating to the URL it auto directed me to the plugin install web
page and after installing the plugin the web app was rendered
correctly. Note that at this point I have not compiled the app so the
plugin is indeed doing its job! The java code is what is interacting
synchronously with the browser instead of the compiled JS!
Note that I had first attempted to launch the app in debug mode which
gave me 3 errors related to the Appengine
(com.google.apphosting.utils.jetty... yet eclipse could not resolve
com.google.apphosting.utils.jetty) but those errors went away as soon
as I did a non debug launch. In other words, the app was able to do a
debug launch only after doing a regular launch.
With the debug launch successful I was able to hit a breakpoint in the
onModuleLoad method of this default web app! I then copied all the
required files from my previous project into this new one. Once again
I was able to hit a breakpoint on the onModuleLoad method!
I am very excited to have this working!
On Oct 7, 8:32 pm, Sky <myonceinalifet...@gmail.com> wrote:
> I set GWT 2.0 as the SDK for my project and it changed to the new
> Development Swing UI In-browser mode instead of the old hosted mode. I
> placed the given URL in both FF3.5 and IE8 and neither auto installed
> the required plugin. Since my app is already compiled it renders fine
> but I cannot debug. I tried manually installing the correct plugins
> fromhttp://code.google.com/p/google-web-toolkit/wiki/UsingOOPHMyet > the server is either only serving the compiled files or something is
> wrong with the plugin because I cannot debug; breakpoints are not hit.
> Does anyone know what I am doing wrong?
> On Oct 7, 11:37 am, Joseph Arceneaux <joe.arcene...@gmail.com> wrote:
> > 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:
> > > 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
I have noticed that if you use Google Plugin to launch your project
with 2.0 jar. The development shell does not launch at all. You have
to launch it as a Java Application and set up some parameters by
yourself, then you are able to see that GWT Develop Mode popup shell
window. Is my observation correct?
On Oct 8, 1:33 pm, Sky <myonceinalifet...@gmail.com> wrote:
> I created a new GWT web app with the Eclipse google plugin using GWT
> 2.0MS1 as the SDK. This is what most likely solved my problem. Simply
> changing a project from GWT 1.7.1 to 2.0 must not be making all the
> necessary changes to the auto generated files to be properly
> compatible. Obviously this sort of thing will be ironed out for
> release.
> Then I needed to first launch (not a debug launch) the newly created
> GWT web app (with the default app still intact). I tried this with a
> browser that did not have the plugin installed (FF3.5) and when
> navigating to the URL it auto directed me to the plugin install web
> page and after installing the plugin the web app was rendered
> correctly. Note that at this point I have not compiled the app so the
> plugin is indeed doing its job! The java code is what is interacting
> synchronously with the browser instead of the compiled JS!
> Note that I had first attempted to launch the app in debug mode which
> gave me 3 errors related to the Appengine
> (com.google.apphosting.utils.jetty... yet eclipse could not resolve
> com.google.apphosting.utils.jetty) but those errors went away as soon
> as I did a non debug launch. In other words, the app was able to do a
> debug launch only after doing a regular launch.
> With the debug launch successful I was able to hit a breakpoint in the
> onModuleLoad method of this default web app! I then copied all the
> required files from my previous project into this new one. Once again
> I was able to hit a breakpoint on the onModuleLoad method!
> I am very excited to have this working!
> On Oct 7, 8:32 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > I set GWT 2.0 as the SDK for my project and it changed to the new
> > Development Swing UI In-browser mode instead of the old hosted mode. I
> > placed the given URL in both FF3.5 and IE8 and neither auto installed
> > the required plugin. Since my app is already compiled it renders fine
> > but I cannot debug. I tried manually installing the correct plugins
> > fromhttp://code.google.com/p/google-web-toolkit/wiki/UsingOOPHMyet > > the server is either only serving the compiled files or something is
> > wrong with the plugin because I cannot debug; breakpoints are not hit.
> > Does anyone know what I am doing wrong?
> > On Oct 7, 11:37 am, Joseph Arceneaux <joe.arcene...@gmail.com> wrote:
> > > 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:
> > > > 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
Ben, with 2.0 my projects launch the development shell when using the
Google plugin launch options. It launched for me even when I just
changed a project from 1.7.1 to 2.0, but you could try creating a
whole new project with 2.0 from the start and copy the files over from
the old project.
Make sure the google plugin and the appengine is fully up to date.
What version of Ecipse are you using? Try downloading the new 3.5.1
version.
Sorry I can't help any more than that. gl
On Oct 8, 3:50 pm, Ben <benzhe...@gmail.com> wrote:
> I have noticed that if you use Google Plugin to launch your project
> with 2.0 jar. The development shell does not launch at all. You have
> to launch it as a Java Application and set up some parameters by
> yourself, then you are able to see that GWT Develop Mode popup shell
> window. Is my observation correct?
> On Oct 8, 1:33 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > I got debugging to work!
> > I created a new GWT web app with the Eclipse google plugin using GWT
> > 2.0MS1 as the SDK. This is what most likely solved my problem. Simply
> > changing a project from GWT 1.7.1 to 2.0 must not be making all the
> > necessary changes to the auto generated files to be properly
> > compatible. Obviously this sort of thing will be ironed out for
> > release.
> > Then I needed to first launch (not a debug launch) the newly created
> > GWT web app (with the default app still intact). I tried this with a
> > browser that did not have the plugin installed (FF3.5) and when
> > navigating to the URL it auto directed me to the plugin install web
> > page and after installing the plugin the web app was rendered
> > correctly. Note that at this point I have not compiled the app so the
> > plugin is indeed doing its job! The java code is what is interacting
> > synchronously with the browser instead of the compiled JS!
> > Note that I had first attempted to launch the app in debug mode which
> > gave me 3 errors related to the Appengine
> > (com.google.apphosting.utils.jetty... yet eclipse could not resolve
> > com.google.apphosting.utils.jetty) but those errors went away as soon
> > as I did a non debug launch. In other words, the app was able to do a
> > debug launch only after doing a regular launch.
> > With the debug launch successful I was able to hit a breakpoint in the
> > onModuleLoad method of this default web app! I then copied all the
> > required files from my previous project into this new one. Once again
> > I was able to hit a breakpoint on the onModuleLoad method!
> > I am very excited to have this working!
> > On Oct 7, 8:32 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > > I set GWT 2.0 as the SDK for my project and it changed to the new
> > > Development Swing UI In-browser mode instead of the old hosted mode. I
> > > placed the given URL in both FF3.5 and IE8 and neither auto installed
> > > the required plugin. Since my app is already compiled it renders fine
> > > but I cannot debug. I tried manually installing the correct plugins
> > > fromhttp://code.google.com/p/google-web-toolkit/wiki/UsingOOPHMyet > > > the server is either only serving the compiled files or something is
> > > wrong with the plugin because I cannot debug; breakpoints are not hit.
> > > Does anyone know what I am doing wrong?
> > > On Oct 7, 11:37 am, Joseph Arceneaux <joe.arcene...@gmail.com> wrote:
> > > > 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:
> > > > > 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
Sky, thanks for you reply. I am using Eclipse 3.5.0 (I am not sure
updating to 3.5.1 matters) and my google eclipse plugin is uptodate.It
still throws that exception if I just use default google plugin launch
configuration.
On Oct 8, 5:39 pm, Sky <myonceinalifet...@gmail.com> wrote:
> Ben, with 2.0 my projects launch the development shell when using the
> Google plugin launch options. It launched for me even when I just
> changed a project from 1.7.1 to 2.0, but you could try creating a
> whole new project with 2.0 from the start and copy the files over from
> the old project.
> Make sure the google plugin and the appengine is fully up to date.
> What version of Ecipse are you using? Try downloading the new 3.5.1
> version.
> Sorry I can't help any more than that. gl
> On Oct 8, 3:50 pm, Ben <benzhe...@gmail.com> wrote:
> > I have noticed that if you use Google Plugin to launch your project
> > with 2.0 jar. The development shell does not launch at all. You have
> > to launch it as a Java Application and set up some parameters by
> > yourself, then you are able to see that GWT Develop Mode popup shell
> > window. Is my observation correct?
> > On Oct 8, 1:33 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > > I got debugging to work!
> > > I created a new GWT web app with the Eclipse google plugin using GWT
> > > 2.0MS1 as the SDK. This is what most likely solved my problem. Simply
> > > changing a project from GWT 1.7.1 to 2.0 must not be making all the
> > > necessary changes to the auto generated files to be properly
> > > compatible. Obviously this sort of thing will be ironed out for
> > > release.
> > > Then I needed to first launch (not a debug launch) the newly created
> > > GWT web app (with the default app still intact). I tried this with a
> > > browser that did not have the plugin installed (FF3.5) and when
> > > navigating to the URL it auto directed me to the plugin install web
> > > page and after installing the plugin the web app was rendered
> > > correctly. Note that at this point I have not compiled the app so the
> > > plugin is indeed doing its job! The java code is what is interacting
> > > synchronously with the browser instead of the compiled JS!
> > > Note that I had first attempted to launch the app in debug mode which
> > > gave me 3 errors related to the Appengine
> > > (com.google.apphosting.utils.jetty... yet eclipse could not resolve
> > > com.google.apphosting.utils.jetty) but those errors went away as soon
> > > as I did a non debug launch. In other words, the app was able to do a
> > > debug launch only after doing a regular launch.
> > > With the debug launch successful I was able to hit a breakpoint in the
> > > onModuleLoad method of this default web app! I then copied all the
> > > required files from my previous project into this new one. Once again
> > > I was able to hit a breakpoint on the onModuleLoad method!
> > > I am very excited to have this working!
> > > On Oct 7, 8:32 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > > > I set GWT 2.0 as the SDK for my project and it changed to the new
> > > > Development Swing UI In-browser mode instead of the old hosted mode. I
> > > > placed the given URL in both FF3.5 and IE8 and neither auto installed
> > > > the required plugin. Since my app is already compiled it renders fine
> > > > but I cannot debug. I tried manually installing the correct plugins
> > > > fromhttp://code.google.com/p/google-web-toolkit/wiki/UsingOOPHMyet > > > > the server is either only serving the compiled files or something is
> > > > wrong with the plugin because I cannot debug; breakpoints are not hit.
> > > > Does anyone know what I am doing wrong?
> > > > On Oct 7, 11:37 am, Joseph Arceneaux <joe.arcene...@gmail.com> wrote:
> > > > > 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:
> > > > > > 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
I did the same trick as Sky to get my project to work. But I still have to
problems.
First : When I lauch it in development mode, I can't close the development
mode hosted window without closing eclipse, that's anoying because I can't
switch to debug mode... So now, I just run it in debug without brake point
to make sure I'm able to stop it and close the development mode hosted
window.
Second : I have the new project html files instead of the one I'm using with
my project ! That's really weird, because on top of my application I have
everything from the new project html file, but my JS files, css files ar
linked correctly ! LOL
On Fri, Oct 9, 2009 at 1:36 PM, Ben <benzhe...@gmail.com> wrote:
> Sky, thanks for you reply. I am using Eclipse 3.5.0 (I am not sure
> updating to 3.5.1 matters) and my google eclipse plugin is uptodate.It
> still throws that exception if I just use default google plugin launch
> configuration.
> On Oct 8, 5:39 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > Ben, with 2.0 my projects launch the development shell when using the
> > Google plugin launch options. It launched for me even when I just
> > changed a project from 1.7.1 to 2.0, but you could try creating a
> > whole new project with 2.0 from the start and copy the files over from
> > the old project.
> > Make sure the google plugin and the appengine is fully up to date.
> > What version of Ecipse are you using? Try downloading the new 3.5.1
> > version.
> > Sorry I can't help any more than that. gl
> > On Oct 8, 3:50 pm, Ben <benzhe...@gmail.com> wrote:
> > > I have noticed that if you use Google Plugin to launch your project
> > > with 2.0 jar. The development shell does not launch at all. You have
> > > to launch it as a Java Application and set up some parameters by
> > > yourself, then you are able to see that GWT Develop Mode popup shell
> > > window. Is my observation correct?
> > > On Oct 8, 1:33 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > > > I got debugging to work!
> > > > I created a new GWT web app with the Eclipse google plugin using GWT
> > > > 2.0MS1 as the SDK. This is what most likely solved my problem. Simply
> > > > changing a project from GWT 1.7.1 to 2.0 must not be making all the
> > > > necessary changes to the auto generated files to be properly
> > > > compatible. Obviously this sort of thing will be ironed out for
> > > > release.
> > > > Then I needed to first launch (not a debug launch) the newly created
> > > > GWT web app (with the default app still intact). I tried this with a
> > > > browser that did not have the plugin installed (FF3.5) and when
> > > > navigating to the URL it auto directed me to the plugin install web
> > > > page and after installing the plugin the web app was rendered
> > > > correctly. Note that at this point I have not compiled the app so the
> > > > plugin is indeed doing its job! The java code is what is interacting
> > > > synchronously with the browser instead of the compiled JS!
> > > > Note that I had first attempted to launch the app in debug mode which
> > > > gave me 3 errors related to the Appengine
> > > > (com.google.apphosting.utils.jetty... yet eclipse could not resolve
> > > > com.google.apphosting.utils.jetty) but those errors went away as soon
> > > > as I did a non debug launch. In other words, the app was able to do a
> > > > debug launch only after doing a regular launch.
> > > > With the debug launch successful I was able to hit a breakpoint in
> the
> > > > onModuleLoad method of this default web app! I then copied all the
> > > > required files from my previous project into this new one. Once again
> > > > I was able to hit a breakpoint on the onModuleLoad method!
> > > > I am very excited to have this working!
> > > > On Oct 7, 8:32 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > > > > I set GWT 2.0 as the SDK for my project and it changed to the new
> > > > > Development Swing UI In-browser mode instead of the old hosted
> mode. I
> > > > > placed the given URL in both FF3.5 and IE8 and neither auto
> installed
> > > > > the required plugin. Since my app is already compiled it renders
> fine
> > > > > but I cannot debug. I tried manually installing the correct plugins
> > > > > fromhttp://code.google.com/p/google-web-toolkit/wiki/UsingOOPHMyet > > > > > the server is either only serving the compiled files or something
> is
> > > > > wrong with the plugin because I cannot debug; breakpoints are not
> hit.
> > > > > Does anyone know what I am doing wrong?
> > > > > On Oct 7, 11:37 am, Joseph Arceneaux <joe.arcene...@gmail.com>
> wrote:
> > > > > > 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:
> > > > > > > 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
> I did the same trick as Sky to get my project to work. But I still have to
> problems.
> First : When I lauch it in development mode, I can't close the development
> mode hosted window without closing eclipse, that's anoying because I can't
> switch to debug mode... So now, I just run it in debug without brake point
> to make sure I'm able to stop it and close the development mode hosted
> window.
> Second : I have the new project html files instead of the one I'm using with
> my project ! That's really weird, because on top of my application I have
> everything from the new project html file, but my JS files, css files ar
> linked correctly ! LOL
> Christian
> On Fri, Oct 9, 2009 at 1:36 PM, Ben <benzhe...@gmail.com> wrote:
> > Sky, thanks for you reply. I am using Eclipse 3.5.0 (I am not sure
> > updating to 3.5.1 matters) and my google eclipse plugin is uptodate.It
> > still throws that exception if I just use default google plugin launch
> > configuration.
> > On Oct 8, 5:39 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > > Ben, with 2.0 my projects launch the development shell when using the
> > > Google plugin launch options. It launched for me even when I just
> > > changed a project from 1.7.1 to 2.0, but you could try creating a
> > > whole new project with 2.0 from the start and copy the files over from
> > > the old project.
> > > Make sure the google plugin and the appengine is fully up to date.
> > > What version of Ecipse are you using? Try downloading the new 3.5.1
> > > version.
> > > Sorry I can't help any more than that. gl
> > > On Oct 8, 3:50 pm, Ben <benzhe...@gmail.com> wrote:
> > > > I have noticed that if you use Google Plugin to launch your project
> > > > with 2.0 jar. The development shell does not launch at all. You have
> > > > to launch it as a Java Application and set up some parameters by
> > > > yourself, then you are able to see that GWT Develop Mode popup shell
> > > > window. Is my observation correct?
> > > > On Oct 8, 1:33 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > > > > I got debugging to work!
> > > > > I created a new GWT web app with the Eclipse google plugin using GWT
> > > > > 2.0MS1 as the SDK. This is what most likely solved my problem. Simply
> > > > > changing a project from GWT 1.7.1 to 2.0 must not be making all the
> > > > > necessary changes to the auto generated files to be properly
> > > > > compatible. Obviously this sort of thing will be ironed out for
> > > > > release.
> > > > > Then I needed to first launch (not a debug launch) the newly created
> > > > > GWT web app (with the default app still intact). I tried this with a
> > > > > browser that did not have the plugin installed (FF3.5) and when
> > > > > navigating to the URL it auto directed me to the plugin install web
> > > > > page and after installing the plugin the web app was rendered
> > > > > correctly. Note that at this point I have not compiled the app so the
> > > > > plugin is indeed doing its job! The java code is what is interacting
> > > > > synchronously with the browser instead of the compiled JS!
> > > > > Note that I had first attempted to launch the app in debug mode which
> > > > > gave me 3 errors related to the Appengine
> > > > > (com.google.apphosting.utils.jetty... yet eclipse could not resolve
> > > > > com.google.apphosting.utils.jetty) but those errors went away as soon
> > > > > as I did a non debug launch. In other words, the app was able to do a
> > > > > debug launch only after doing a regular launch.
> > > > > With the debug launch successful I was able to hit a breakpoint in
> > the
> > > > > onModuleLoad method of this default web app! I then copied all the
> > > > > required files from my previous project into this new one. Once again
> > > > > I was able to hit a breakpoint on the onModuleLoad method!
> > > > > I am very excited to have this working!
> > > > > On Oct 7, 8:32 pm, Sky <myonceinalifet...@gmail.com> wrote:
> > > > > > I set GWT 2.0 as the SDK for my project and it changed to the new
> > > > > > Development Swing UI In-browser mode instead of the old hosted
> > mode. I
> > > > > > placed the given URL in both FF3.5 and IE8 and neither auto
> > installed
> > > > > > the required plugin. Since my app is already compiled it renders
> > fine
> > > > > > but I cannot debug. I tried manually installing the correct plugins
> > > > > > fromhttp://code.google.com/p/google-web-toolkit/wiki/UsingOOPHMyet > > > > > > the server is either only serving the compiled files or something
> > is
> > > > > > wrong with the plugin because I cannot debug; breakpoints are not
> > hit.
> > > > > > Does anyone know what I am doing wrong?
> > > > > > On Oct 7, 11:37 am, Joseph Arceneaux <joe.arcene...@gmail.com>
> > wrote:
> > > > > > > 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:
> > > > > > > > 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,
Is there a way i can try these? the documents i got along with the milestone
download doesn't contain anything about 2.0 Milestone 1 and its Features? i
was hoping if some one could point me to examples of Declarative UI and Code
Splitting examples?
On Tue, Oct 6, 2009 at 5:13 AM, 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:
> 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
> Is there a way i can try these? the documents i got along with the milestone
> download doesn't contain anything about 2.0 Milestone 1 and its Features? i
> was hoping if some one could point me to examples of Declarative UI and Code
> Splitting examples?
Check the mail sample for declarative UI, for runAsync(),
http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse... . The whole process is rather simple; call
GWT.runAsync(new RunAsyncCallback(){
onFailure(){Window.alert("Failed to load application");
onSuccess(){
GuiStuffOrWhatever.init();
//...
}
});
Whatever code that is referenced inside the GuiStuffOrWhatever class,
but NOT outside that class, will be chunked into a delayed download.
Using lots and lots of interfaces instead of full objects will make
your initial download full of basic prototype rules that all your
specific objects will share, and will not need to re-download / wait
for other implementations to be initialized. Basically, if you've
been careful to keep your specialized modules separated into unique
packages and reduced dependencies / use interfaces instead of full
object references, you should be able to take full advantage of this.
If all your code references all your other code over and over again,
you won't get much more use out of runAsync other than to have a nice
splash "loading" page while you do your monolithic onModuleLoad() code
inside a single runAsync(new RunAsyncCallback(){}); call.
Thx for the reply. since we are taking about async loading of script i
have one more question here, could it be possible that a module can load a
script asynchronously a calss from another module? im thinking more like an
interface will be defined the Module-A and and the implementation calss is
available in Module-B and the Module-A will be able to load the
implementation from Module-B?
> > Is there a way i can try these? the documents i got along with the
> milestone
> > download doesn't contain anything about 2.0 Milestone 1 and its Features?
> i
> > was hoping if some one could point me to examples of Declarative UI and
> Code
> > Splitting examples?
> Check the mail sample for declarative UI, for runAsync(),
> Whatever code that is referenced inside the GuiStuffOrWhatever class,
> but NOT outside that class, will be chunked into a delayed download.
> Using lots and lots of interfaces instead of full objects will make
> your initial download full of basic prototype rules that all your
> specific objects will share, and will not need to re-download / wait
> for other implementations to be initialized. Basically, if you've
> been careful to keep your specialized modules separated into unique
> packages and reduced dependencies / use interfaces instead of full
> object references, you should be able to take full advantage of this.
> If all your code references all your other code over and over again,
> you won't get much more use out of runAsync other than to have a nice
> splash "loading" page while you do your monolithic onModuleLoad() code
> inside a single runAsync(new RunAsyncCallback(){}); call.
|
