On Tue, Jan 25, 2011 at 7:20 PM, Alex North <[email protected]> wrote: > +wave-dev again
Oops. I've been spoiled by google groups. > On 25 January 2011 02:30, Joseph Gentle <[email protected]> wrote: >> ... is this right? >> >> - Make a client-side WaveletData object >> - Wrap the WaveletData in an OpBasedWavelet, and make a sink through >> which the ops are sent to the server >> - Make a WaveView, and add the wavelet to it. >> - Build a WaveBasedConversationView out of the wave view >> >> WaveletBasedConversation.makeWaveletConversational(wavelet); >> conversation = conversationView.getRoot(); >> ConversationBlip blip = conversation.getRootThread().appendBlip(); >> LineContainers.appendToLastLine(blip.getContent(), >> XmlStringBuilder.createText(text)); >> ... >> >> Is there a way to make a conversation in a wavelet without the wave view? >> Hm. > > That all sounds right. Currently no, you need the view. > A. > Wonderful. I've got something working based on the search service code for making a wave and generating ops using a custom sink: https://gist.github.com/794716 I can compile that code to javascript and run it in a browser. The resultant (obfuscated) javascript that GWT produces is about 270kb. That'll grow a bit as I add more functionality - the module only includes referenced code. I'm going to export out two separate libraries - one which just does OT (basically, a server library), and one which includes some of the higher level wave abstractions (what you'd need in a client). -J
