Oh yeah I didn't see that. I can't remember to be honest - I haven't actively worked in the wave codebase since 2010, and I've avoided GWT since then. I remember it working, but I can't remember how. There was an eclipse project file sitting in the root directory of the wiab project with most stuff set up, but I wouldn't be surprised if GWT had evolved and moved on since it was made.
-J On Fri, Dec 27, 2013 at 3:47 PM, Frank R. <renfeng...@gmail.com> wrote: > Hi Joseph, > > I guess you didn't notice the previous email was intended for you to read. > Do you think you share how you run the gwt web client in eclipse debug mode? > Thanks. > > Regards, > Frank > > ---------- Forwarded message ---------- > From: Frank R. <renfeng...@gmail.com> > Date: Sun, Dec 22, 2013 at 10:30 PM > Subject: Re: Setting up Wave for client development (my experience setting > up on WindowsXP) > To: wave <wave-dev@incubator.apache.org> > > > Can you show how you did that? Thanks~ > > > On Sun, Dec 22, 2013 at 7:43 AM, Joseph Gentle <jose...@gmail.com> wrote: >> >> I've certainly used eclipse's debugger to step through code in the >> client, but I'm not sure if I ever had a fast (or instant) change-run >> loop working. Most of the work I did was tests (or well tested code), >> and they ran in eclipse just fine. >> >> -J >> >> On Sun, Dec 22, 2013 at 10:35 AM, Thomas Wrobel <darkfl...@gmail.com> >> wrote: >> > -sigh- >> > Sadly I was wrong. While the client/server are all functional, the GWT >> > Development mode isnt going anything. It loads the URL, but has no >> > communication whatsoever. The normal realtime updates doesn't work. Even >> > the most trivial client change makes no difference without a real >> > compile. >> > In fact, closing the red GWT Development popup window doesnt even stop >> > the >> > client working -clearly its doing nothing beyond launching it. >> > >> > ** Can anyone on this list confirm if the GWT for Waves client has ever >> > worked for realtime(ish)development ? ** >> > >> > Am I pursuing something that no one has got working? >> > That is, the cycle of "run">>"look at client in browser">>"make client >> > code >> > changes">>"refresh browser">>"see changes" >> > >> > The notes in the build.xml seem to indicate it should ""Runs the hosted >> > mode server, for debugging the GWT >> > client in a JVM." implies running via Java, not java, not javascript. >> > That should be realtime. >> > >> > >> > also; >> > >> > On 20 December 2013 02:15, Frank R. <renfeng...@gmail.com> wrote: >> > >> >> You don't need this at all. >> >> >> >> <arg line="-startupUrl http://localhost:9898"/> >> >> >> >> >> >> On Tue, Dec 17, 2013 at 1:26 AM, Yuri Z <vega...@gmail.com> wrote: >> >> >> >> > Try to add the startupUrl like this: >> >> > >> >> > <target name="hosted-gwt" depends="compile" >> >> > description="Runs the hosted mode server, for debugging the GWT >> >> > client in a JVM."> >> >> > <java failonerror="true" fork="true" >> >> > classname="com.google.gwt.dev.DevMode"> >> >> > <classpath> >> >> > <pathelement location="${src.dir}"/> >> >> > <pathelement location="${gen.dir}/messages"/> >> >> > <path refid="libpath"/> >> >> > </classpath> >> >> > <jvmarg value="-Xmx512M"/> >> >> > <jvmarg value="-ea"/> >> >> > <jvmarg >> >> > >> >> > >> >> >> >> value="-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8001"/> >> >> > <arg value="-noserver" /> >> >> > <arg line="-bindAddress 0.0.0.0" /> >> >> > <arg line="${gwt.args}"/> >> >> > <arg line="-startupUrl http://localhost:9898"/> >> >> > <arg value="org.waveprotocol.box.webclient.WebClientProd"/> >> >> > >> >> > >> >> >> >> >> > >> > I just tested this again without <arg line="-startupUrl >> > http://localhost:9898"/>, and it definitely doesn't connect. >> > "No startup URLs supplied and no plausible ones found -- use >> > -startupUrl" >> > in the GWT Development popup window. >> > >> > Thanks as always for all the help, >> > Thomas > > >
