Just a note - the rendering to static HTML is experimental and wasn't actually submitted to official Apache Wave repo since there was no agreement on the way on how this should implemented right without breaking static bindings when compiling from GWT to Javascript.
On Sat, Jun 15, 2013 at 10:05 PM, Zachary “Gamer_Z.” Yaro <zmy...@gmail.com>wrote: > @Fleeky, Yuri actually added some > code< > https://github.com/vega113/WaveInCloud/tree/master/src/org/waveprotocol/box/server/rpc/render > >to > WIAB for static HTML rendering, so that could be a solution to your > publishing problems. In addition, Google Wave, Rizzoma, and (I* *think) > WIAB (with Yuri's code) support exporting to HTML or PDF. Is that what you > were asking for? > > @John, I definitely like the idea of being able to log into a wave server > from OpenOffice and edit waves through it, but I think we need a > standardized wave client-server protocol first. > > > —Zachary “Gamer_Z.” Yaro > > > On 15 June 2013 12:34, Fleeky Flanco <fle...@gmail.com> wrote: > > > john, i was infact using wave as a google docs replacement for a while it > > worked pretty good the only problem i had with it was that i couldnt > > 'publish' static updates to a front facing page to share with people who > > didnt feel like registering on my wave server. > > > > an openoffice for wave would be extremely usefull, and could have an > > extremely large impact imo. wave is also already very very close to > having > > this funcitonality. etherpad lite sortof already does this, but i kept > > going back to wave because it was actually more responsive, featurefull, > > and actually crashed less. > > > > > > > > > > On Sat, Jun 15, 2013 at 9:29 AM, John Blossom <jblos...@gmail.com> > wrote: > > > > > I had the down-the-road thought just now that I wanted to put into > > > circulation before I forgot about it. > > > > > > One of the challenges that we will face in developing open source Wave > is > > > that Google and others - but mostly Google - are out there using > > > operational transform technologies also. So far the Google Drive > Realtime > > > API hasn't had much impact, but it's being "demoed" successfully in > Drive > > > apps like Docs and Presentations. > > > > > > The advantages of an open source Wave implementation are, of course, > that > > > people can own their own data and identity management without having to > > > rely on a specific vendor's infrastructure. But the flip side of that > is > > > that you have to look carefully at infrastructure that integrates OT > and > > > understand what you have to do similarly to showcase your technologies. > > > > > > That brings me to OpenOffice. At some point it will be beneficial to > > > consider how the Wave API can enable apps in the OpenOffice suite to > take > > > advantage of OT technologies in Wave and its other various features. In > > > fact, it's not unthinkable that an OpenOffice for Wave variant might > not > > be > > > feasible at some point, maintaining a familiar office automation > paradigm > > > as a user interface for those who relate to that sort of tool but > having > > > the power of Wave to drive collaborative document editing, comments, > > > embedded apps and so on, with Wave data structures underneath the OO > > > interface. > > > > > > Just idle thoughts for now, but if we make good progress over the next > > > several months, it's a sub-project that may help to attract more > > developers > > > to Wave technologies. > > > > > > All the best, > > > > > > John Blossom > > > > > >
