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 >
