Hi Allahbaksh, GXP files are templates for producing dynamic HTML content, much like JSP. From a .gxp file, the GXP compiler produces a Java class that a servlet can invoke (supplying parameters declared in that .gxp file) in order to produce an HTML response for an HTTP request. Advantages over HTML files include the content being dynamic (in the WIAB case, session data and flag values are injected into the page), and also page content can be modularized. Advantages over plain Java code include being smaller and easier to read, and also guaranteed well-formedness of HTML responses.
See http://code.google.com/p/gxp/ for more info. Can you be more specific about what parts of the system you're interested in? There is a range of documentation, at varying degrees of detail, but not all parts are covered. -Dave On Fri, Jan 28, 2011 at 5:37 PM, Allahbaksh Asadullah < [email protected]> wrote: > Hi David and Yuri, > I tried debugging it as mentioned in the document and your email. It > worked. > Thanks for the quick reply. > > What are these gxp files. I think they are html files but is their any > advantage of keeping it separately. Is their any good documentation on code > like what element corresponds to what. > > Warm Regards, > Allahbaksh > > On Fri, Jan 28, 2011 at 11:14 AM, Yuri Z <[email protected]> wrote: > > > I could debug the full client using hosted-gwt. You need to have the > server > > running (For some reason I had to compile it with compile-gwt, if I used > > compile-gwt-dev it didn't work), then you run the hosted-gwt. Aftr that > you > > open web client, log in and then insert the code server url parameter, > > i.e. ?gwt.codesvr=127.0.0.1:9997 so your URL looks like > > > > > http://example.com:9898/?gwt.codesvr=127.0.0.1:9997#example.com/w+9j9ERgNH-MN > > < > > > http://vegalabz.com:9898/?gwt.codesvr=127.0.0.1:9997#vegalabz.com/w+9j9ERgNH-MN > > > > > > > < > > > http://vegalabz.com:9898/?gwt.codesvr=127.0.0.1:9997#vegalabz.com/w+9j9ERgNH-MN > > >Regarding > > (1) - I don't think you can debug it as like you would debug a regular > GWT > > program created with GWT eclipse plugin. In any way - for most cases the > > Wiab harness debug mode is sufficient as David said. > > > > 2011/1/28 Allahbaksh Asadullah <[email protected]> > > > > > 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 > > > > > >
