Oops - misread 'Thomas' as 'Torben' :)
On Wed, May 11, 2011 at 3:49 AM, Joseph Gentle <[email protected]> wrote: > Yeah - you should be able to do realtime collaborative editing in > pretty much any application, so long as you can describe the OT > semantics for your data. Plain text, rich text and JSON support should > cover 95% of applications out there. > > I'm really excited to see what people make with it. > > Brett - You're right about wavelets. It should be possible to compile > wave's OT code into javascript and pull that in to sharejs as another > data type. You could run the wave editor on top of sharejs with a bit > of work. > > Torben - is this compatible at all with the stuff you've been working > on? You gave me the idea to do OT for JSON - though I think my > implementation is quite different from yours. > > [On that note, I'd really appreciate comments about my spec for JSON > OT: https://github.com/josephg/ShareJS/wiki/JSON-Operations ] > > Do you think I should implement federation in sharejs? A classic > client-server model will work fine for most sharejs applications I can > think of, and I'm going to focus on that first. I really like the idea > of federation though - its a great way to authenticate users & deliver > notifications. > > -J > > > On Wed, May 11, 2011 at 1:34 AM, Thomas Wrobel <[email protected]> wrote: >> This is pretty darn cool. >> For our own project we pretty much need all of wave (at least, >> concurrent federated multiple editors each user having their own >> subscriptions to various waves, different users posting seperate >> wavelets with in it). >> >> Still, I can see *so* many uses for this. You could, for example, use >> it to concurrently edit 3d data stored in a xml like fornat (x3d for >> example) - multiplayer 3dsmax anyone? :P >> >> -Thomas >> >> >> ~~~~~~ >> Reviews of anything, by anyone; >> www.rateoholic.co.uk >> Please try out my new site and give feedback :) >> >> >> >> On 10 May 2011 17:18, Joseph Gentle <[email protected]> wrote: >>> Dear wave refugees! >>> >>> As many of you know, I really want wave's technology to be usable in >>> other situations. So I made ShareJS - a NodeJS server & javascript >>> client for doing concurrent editing with arbitrary data. >>> >>> Here's a simple concurrent wiki built on top of sharejs: >>> http://sharejs.org:8000/wiki/Main >>> Open it in a couple browser windows & you can do google wave style live >>> editing. >>> >>> Its wave's OT technology, rewritten in coffeescript. >>> >>> The software stack is type-agnostic. At the moment I'm working on >>> writing OT code for arbitary JSON objects, so you should be able to >>> whip up complex concurrent apps like route planners, spreadsheets, ... >>> or, whatever :) >>> >>> Its pretty early days for sharejs - there's currently no undo support, >>> no authentication and no rich text. You should help out. At ~2000 >>> lines of code (+ tests), sharejs has 100 times less code than wave in >>> a box. And its written in coffeescript (need I say more?) >>> >>> If you can think of anything particularly cool that you want to do >>> with sharejs, drop me an email. I'll tell you which features are >>> missing and how you can help write them. Lets make wave's legacy a >>> whole bunch of awesome software. >>> >>> Code: >>> https://github.com/josephg/ShareJS >>> >>> MOAR DEMOS: >>> http://sharejs.org:8000/ >>> >>> Cheers >>> Joseph >>> >> >
