ad Anthony) You say that the source code of the editor released by google is the same as the one in wave preview/wave sandbox. If that's true, then I'm a bit confused about following things:
1. The editor released by google uses websocket communiction between browser and FedOne. However, current browsers don't support websocket communication. Does the wavesandbox code use any kind of websocket communication workaround to enable it in current browsers (e.g. flash library workaround)? If so, which workaround does google use? I couldn't track any sign of unusual activity indicating any kind of workaround when working with the wavesandbox editor. I saw just AJAX requests fired to server. 2. What about the formatting things like lists or indentation? I couldn't find it in the released code, but obviously wavesandbox version of editor does support it. Do I look bad or is there any difference between those two codes? All-in-all what I want to know is: If you say that the source code is the same, what makes the difference between the fully working editor used in preview/sandbox and the demo toy released to public? I'm asking these questions, because I want to focus on the business use of wave technology, but instead I have spend countless hours with handling of dozens of events just to ensure correct functionality of the editor. The clipboard, spellcheckers and related stuff is really awful topic to master. I would really appreciate, If someone from google could bring a bit of light into the editor issue and its future. With regards, LittleWaver On 21 čvn, 15:52, Dan Peterson <[email protected]> wrote: > Hi Alona, > > The rich text editor is a fundamental component of the Google Wave UI and > we're looking forward to releasing more components in the future. > > Hope you find it useful. > > Cheers, > -Dan > > On Mon, Jun 21, 2010 at 11:21 PM, alona.oz <[email protected]> wrote: > > I've asked Google team at one of Google waves and as I undestood they > > don't plan to release Google Wave UI to open source > > > On Jun 18, 11:06 am, Anthony Baxter <[email protected]> wrote: > > > On Fri, Jun 18, 2010 at 16:05, LittleWaver <[email protected]> > > wrote: > > > > Hi, > > > > Few days ago, I came across source codes of the real-time RTF wave > > > > editor released by Google. > > > > > The editor provides some basic real-time editing of blips with really > > > > basic support for formatting (italics, bold … not much more). From > > > > what I’ve seen so far, it is a huge mess of really complex handling of > > > > dozens of events fired by various browsers in various situations. > > > > > It is something completely different from the editor Google actually > > > > uses in its Google Wave preview or Wave sandbox. > > > > Actually, it's exactly the same code as used in wavesandbox and > > > wave.google.com. There is only one version of the code now. > > > > -- > > > Anthony Baxter, [email protected] > > > -- > > You received this message because you are subscribed to the Google Groups > > "Wave Protocol" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<wave-protocol%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/wave-protocol?hl=en. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
