The proper group for discussing FedOne and WavePad is wave-protocol: http://groups.google.com/group/wave-protocol
Thanks, -joe -- Joe Gregorio Developer Relations, Google Wave On Thu, Jun 17, 2010 at 3:38 PM, LittleWaver <alfaomeg...@gmail.com> 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. > > Could someone competent from Google tell us, if they plan to release > some version of the editor that would actually be useful? > > I’m asking this, because the piece of code they released so far isn’t > much of a practical use. > > I know it is not Google’s fault that there are so many inconsistencies > in DOM, events, and all the related things among individual browsers. > > On the other hand, there is so much “big words” about federating, > openness, collaboration, etc. when speaking about wave… so wouldn’t it > be great, if they provided us with the source code of the editor they > use? > > I think companies trying to implement wave technology will have enough > problems with building their own federation server / extending the > FedOne prototype and integrating it with their business logic, and > shouldn’t spent hundreds of Man-Hours by implementing real-time RTF > wave editor working in all major browsers. > -------------------------------- > Don’t get me wrong, I think the wave idea is awesome!!! > > However, I’m a bit disgusted when I see what problems lie in front of > the early adopters of the idea. You have such a great concept in front > of you and are full of enthusiasm to get the technology working. But > as you get into the topic deeper and deeper you start to see that the > reality is not that good – two examples: > > 1. FedOne can’t do much for you these days – not even persistence of > waves is included (although Google already probably has it implemented > in the server behind Google Wave preview / Wave sandbox) > > 2. By building the RTF wave editor we’re actually raping the web … we > try to get from the web technologies something they’re not designed > for: We are trying to build RTF editor enabling concurrent real-time > editing by multiple participants. To accomplish that, we can use only > web technologies (i.e. HTML, CSS, Javascript) … not really the nicest > technologies for calculating cursor positions in text (HTML code in > the background) and applying changes to the text. Moreover, we have to > fight with the browser incompatibility hell all the time. > > I know that point 2 isn’t wave specific, but it demonstrates the fact > that we’re forcing the web to be something else as it was designed to > be. > > > With Regards, > LittleWaver > > -- > You received this message because you are subscribed to the Google Groups > "Google Wave API" group. > To post to this group, send email to google-wave-...@googlegroups.com. > To unsubscribe from this group, send email to > google-wave-api+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-wave-api?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
