Hi Anthony, you say the code in sandbox is the same as the one released to public. Can you explain me please following things?
1. The code released to public uses websocket communication, but the current browsers (e.g. Internet Explorer) don't support it. So if the code behind wavesandbox is the same as the one released to public, how can it work in current browsers? A answer to this could be that you use the "flash library" workaround for using websocket communication in current browsers in sandbox. However, there's no evidence of any "flash related" activity when using the editor in wavesandbox. Do I just detect the flash activity in a wrong way? Or do you use any other websocket workaround (which one?) Or did you modify the code of the editor and related components, so it doesn't actually match the code released to public? 2. Advanced formatting - i wasn't able to find any place in the code released to public, where things like bullet lists, or indentation were implemented. However, those features are supported in sandbox. If these two versions of editors are actually the same code, how is that possible? Do I just search bad in the code released to public? Or did you modify the code used in wavesandbox. All-in-all I would like to know, how can it be that the editor in sandbox can do so much more in comparsion to the one released to public? Where's the key difference? I hope my comments/questions just demonstrate the interest I have in the Wave related technologies, and don't insult you in any way. With regards, LittleWaver On 18 čvn, 10:06, 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]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
