Hi Allahbaksh, Please see http://www.waveprotocol.org/code/client-development-environment-set-up. Debugging the full client is a last resort, because you need to build and run the WIAB server. Try and debug using the harnesses first. To answer your question about embedding, the 'org.waveprotocol.box.webclient.WebClientProd' module gets renamed to 'webclient' (see the rename-to), and WaveClientPage.gxp invokes 'webclient/webclient.nocache.js' with a <script> tag in its <head>.
1. The harnesses (wave panel and editor) can be debugged directly from Eclipse. The full client needs a server running, and you need to construct the URLs manually, and continually re-insert the gwt.hosted parameter, so it is more fiddly. 2. We recently upgraded to using GWT 2.1.1, and some of the widgets now used by the full client are not available in GWT 2.1. However, the wave panel and editor (and their harnesses) should work fine in GWT 2.1 and earlier. 3. Not quite. The "SmartScroller" in WIAB is simply a bunch of rules about how to move the viewport from one element to another with minimal perceived disruption (e.g., keep the same top alignment of focused elements or minimize scroll distance, etc). The full scrolling experience from Google Wave is not included in WIAB. Hope that helps, -Dave On Fri, Jan 28, 2011 at 2:35 PM, Allahbaksh Asadullah < [email protected]> wrote: > Hi, > I am pretty new to wave. I tried debugging wave client using ant hosted-gwt > but it didnot work. There is no file which is actually embed the script > from org.waveprotocol.box.webclient.WebClientProd module. > > Few more questions > > 1. Can I debug this directly using Eclipse GWT plugin and GWT 2.1 > 2. At what point of time we are moving to GWT 2.1 > 3. Whether SmartScroller is the same scroller which we see at > wave.google.com > > Any other information needed to setup a proper debug environment would be > appreciated. > Warm Regards, > Allahbaksh >
