BTW, you might want to take a look at the  http://sharejs.org/  project.

On Mon, Jun 25, 2012 at 12:24 AM, Svante Schubert <[email protected]
> wrote:

> Hi Michael and Yuri,
>
> Solved!My main obstacle was, I had been looking in the wrong place, ie.
> build/dist.
> Your hints lead me to the generated (and pretty printed) JS.
>
> Thanks for your help,
> Svante
>
> On 24.06.2012 21:19, Michael MacFadden wrote:
> > Svante,
> >
> > The javascript should be generated by calling.  It is being generated by
> GWT into the "war" directory that is created in the same directory as the
> ant build script.  GWT compiles all of the javascript from the various java
> sources in to one single JS file that is obfuscated (for compression).  So
> by default if you are looking for various javascript files that would
> correspond to the individual java classes being cross compiled, you won't
> find those (as they are all aggregated into a single file).  There are some
> options you can use with the GWT compiler to make things a little less
> obfuscated during development.
> >
> > How familiar are you with the overall GWT compilation process?
> >
> > ~Michael
> >
> >
> > On Jun 24, 2012, at 12:05 PM, Svante Schubert wrote:
> >
> >> Michael,
> >>
> >> thanks for the quick answer.
> >>
> >> I am wondering why there is no JavaScript being build after calling
> "ant".
> >> Did I miss something? Any documentation to read, I have overseen?
> >>
> >> PS: More questions might arise after I dived on Tuesday into the
> >> sources, did not expect an answer that fast ;)
> >>
> >> Thanks,
> >> Svante
> >>
> >>
> >> On 24.06.2012 16:31, Michael MacFadden wrote:
> >>> Svante,
> >>>
> >>> The OT concurrency control stack is compiled into JavaScript by the
> GWT compiler.
> >>>
> >>> The code for this particular piece is located here:
> >>>
> >>>
> https://svn.apache.org/repos/asf/incubator/wave/trunk/src/org/waveprotocol/wave/concurrencycontrol/client/
> >>>
> >>> Basically the client does most things in the browser, including client
> side concurrency control.  The client uses a websocket interface to send
> its operations to the server and to receive operations from other user from
> the server.  So the OT for the server happens in Java.  The OT for the
> client happens in JavaScript in the browser.
> >>>
> >>> Does this answer your question?
> >>>
> >>> ~Michael
> >>>
> >>>
> >>> On Jun 24, 2012, at 6:10 AM, Svante Schubert wrote:
> >>>
> >>>> Is the Google Web Toolkit only used in Wave for the front-end?
> >>>> I was somehow expecting that the OT functionality of a Java based
> server
> >>>> would be mirrored to the browser client by transforming it from Java
> to
> >>>> JavaScript.
> >>>> After a build "'ant' by command line" I could only find about 15 JS
> >>>> sources in the build/staging directory.
> >>>>
> >>>> Anyone able to give me insight on this topic?
> >>>>
> >>>> PS: I am asking as I am working on OT support for ODF, mapping
> currently
> >>>> the Apache Incubating ODF Toolkit to operations (still a private test
> >>>> branch atm)..
> >>>>
> >>>> Thanks in advance,
> >>>> Svante
> >>
>
>
>

Reply via email to