MIME-Version: 1.0
Received: by 10.101.67.1 with SMTP id u1mr313532ank.30.1255124204629; Fri, 09 
	Oct 2009 14:36:44 -0700 (PDT)
Date: Fri, 9 Oct 2009 14:36:44 -0700 (PDT)
In-Reply-To: <d9640da0910091101o5f0ffa6fn6d112fc05966e64b@mail.gmail.com>
X-IP: 74.212.168.122
References: <86bab137-8859-4fc2-87d6-6165b1586e54@o9g2000prg.googlegroups.com> 
	<6bbe977d0910070937lb87b704s432b2b86cea81142@mail.gmail.com> 
	<14461377-929a-4112-a382-5d7626fc8f1a@l34g2000vba.googlegroups.com> 
	<6adcad33-4157-42d2-b568-9a8910fe6811@k26g2000vbp.googlegroups.com> 
	<e781437d-f28f-418c-bf64-85a5a12b5cf4@j19g2000vbp.googlegroups.com> 
	<02518817-a79a-4022-ab13-c76592951738@e18g2000vbe.googlegroups.com> 
	<5f9b3ab8-4704-46cc-9fb7-2213d2b37c8f@o21g2000vbl.googlegroups.com> 
	<d9640da0910091101o5f0ffa6fn6d112fc05966e64b@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-us) 
	AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9,gzip(gfe),gzip(gfe)
Message-ID: <1c0df4a2-af7d-4113-b6d4-174729373d6d@p15g2000vbl.googlegroups.com>
Subject: Re: Announcing GWT 2.0 Milestone 1
From: Ben <benzhe...@gmail.com>
To: Google Web Toolkit <google-web-toolkit@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey, Guys,

Thanks for the reply. I just found out that it is an open bug for
OOPHM on Mac OS X. If you are curious, the bug is here:
http://code.google.com/p/google-web-toolkit/issues/detail?id=3D3923.

cheers
Ben

On Oct 9, 2:01=A0pm, Christian Goudreau <goudreau.christ...@gmail.com>
wrote:
> I did the same trick as Sky to get my project to work. But I still have t=
o
> problems.
>
> First : When I lauch it in development mode, I can't close the developmen=
t
> 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 poin=
t
> 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 w=
ith
> 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 fro=
m
> > > 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 hav=
e
> > > > 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 shel=
l
> > > > 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. Si=
mply
> > > > > changing a project from GWT 1.7.1 to 2.0 must not be making all t=
he
> > > > > 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 crea=
ted
> > > > > GWT web app (with the default app still intact). I tried this wit=
h 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 w=
eb
> > > > > 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 interact=
ing
> > > > > synchronously with the browser instead of the compiled JS!
>
> > > > > Note that I had first attempted to launch the app in debug mode w=
hich
> > > > > gave me 3 errors related to the Appengine
> > > > > (com.google.apphosting.utils.jetty... yet eclipse could not resol=
ve
> > > > > 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 i=
n
> > the
> > > > > onModuleLoad method of this default web app! I then copied all th=
e
> > > > > required files from my previous project into this new one. Once a=
gain
> > > > > 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 n=
ew
> > > > > > 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 render=
s
> > fine
> > > > > > but I cannot debug. I tried manually installing the correct plu=
gins
> > > > > > fromhttp://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM=
yet
> > > > > > the server is either only serving the compiled files or somethi=
ng
> > is
> > > > > > wrong with the plugin because I cannot debug; breakpoints are n=
ot
> > 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 functiona=
lity
> > that
> > > > > > > > will be coming in GWT 2.0. Please download the bits from:
>
> >http://code.google.com/p/google-web-toolkit/downloads/list?can=3D1&q=3D2=
....
>
> > > > > > > > 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 b=
e
> > 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 th=
e
> > new
> > > > > > > > plugin approach used to implement development mode (see bel=
ow).
> > 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 mod=
e
> > 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 brow=
ser.
> > > > > > > > Development mode is supported through the use of a native-c=
ode
> > plugin
> > > > > > > > for each browser. In other words, you can use development m=
ode
> > > > > > > > directly from Safari, Firefox, IE, and Chrome.
>
> > > > > > > > * Code Splitting: Developer-guided code splitting allows yo=
u 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 c=
an
> > arrange
> > > > > > > > to load just the minimum script needed to get the applicati=
on
> > 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 h=
ad
> > to be
> > > > > > > > created and assembled programmatically, requiring lots of c=
ode.
> > 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 wit=
h
> > > > > > > > ImageBundles since GWT v1.4, giving developers automatic
> > spriting of
> > > > > > > > images. ClientBundle generalizes this technique, bringing t=
he
> > power of
> > > > > > > > combining and optimizing resources into one download to thi=
ngs
> > like
> > > > > > > > text files, CSS, and XML. This means fewer network round tr=
ips,
> > which
> > > > > > > > in turn can decrease application latency -- especially on
> > mobile
> > > > > > > > applications.
>
> > > > > > > > * Using HtmlUnit for running GWT tests: GWT 2.0 no longer u=
ses
> > 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. Th=
is
> > means
> > > > > > > > there is a single GWT distribution for linux, mac, and wind=
ows,
> > and
> > > > > > > > debugging GWT Tests in development mode can be done entirel=
y in
> > a Java
> > > > > > > > debugger.
>
> > > > > > > > Known issues
> > > > > > > > * =A0If you are planning to run the webAppCreator, i18nCrea=
tor,
> > 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. Additiona=
lly,
> > > > > > > > HtmlUnit does not do layout. So tests can fail either becau=
se
> > they
> > > > > > > > exercise layout or they hit bugs due to incomplete integrat=
ion.
> > If you
> > > > > > > > want such tests to be ignored on HtmlUnit, please annotate =
the
> > test
> > > > > > > > methods with @DoNotRunWith({Platform.Htmlunit})
> > > > > > > > * The Google Eclipse...
>