Thanks, Fleeky, that's useful feedback. I, too, tried to use Wave as a document development tool and it's powerful in some ways, but the raw interface didn't always adapt itself well for final presentations. It was doable, though. For example, I gave a talk at a conference about Wave using Wave as the slide set - I just advanced from one blip to another to turn slides. Not ideal, but it worked. So put that same data paradigm behind a slide presentation UI, and use one tool to talk about ideas, collaborate on them and then present them through an OpenOffice slide presenter. And so on.
I think that there are at least a few UIs that we can use for an open Wave UI set: - native demo interface - exercise all of Wave's features for PC Web and mobile Web environments - Email replacement - use presentation-layer adapters on Wave protocol to provide native-like email support but which can also view the underlying data via more powerful UIs - OpenOffice for Wave - productivity tools for print-oriented presentation - Blogging - root blip for rich text posts, trailing blips for comments, with formatting a la other blogging environments - Chat/Hangout - person-to-person text streams - again, as with other UIs, you can use other UIs on the same data set to collaborate more richly - Collaborative tool replacement - a bit like Kune.cc, perhaps, though I think that their metaphors are quite limited Obviously we have to walk before we can run, but hopefully this stimulates some thinking. Best, John On Sat, Jun 15, 2013 at 12:34 PM, 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 > > >
