I'm going to spend the two weeks remaining before WikiSym trying to get CoTor into a mature alpha stage so that we can demonstrate it at WikiSym. I'm calling for help with this BarnRaising? effort from any interested coders. My first order of business is to set up http://CoTor.org as the locus of development for CoTor. I've decided to use TinyMCE as the WYSIWYG component and treehouse chat for the chat window. I'm planning to create:
for each interested developer. Each developer will have a darcs repository on the server that they can push patches to. Anybody can pull patches from anybody else's darcs repository. The darcs repository on the server will also contain the "live" code for that developer. More here as this effort develops.
Brandon, you rock!
cotor.org now has a database with pages, CRUD for modifying the database and the tinymce editor is plugged in. Still to do …
The current version of CoTor has just about everything disabled as I am struggling to get the location of the cursor within the WYSIWYG text and wanted to speed up the development loop (hence limit complexity). More here as I figure out how to get the position of the caret.
Technically I hardly ever follow. Anyhow. I passed the url to armin of gobby and he reacted: Das ist dann einfach kollaboratives Editieren im Browser(?) - that would simply be collaborative editing in the browser(?)
I don't understand why he said so, pretty sure there is a reason, but the idea is gigantic. You edit a wiki in a browser, so why not collaboratively do it in a browser?
Mattis that is exactly correct. CoTor is a collaborative editor in your browser. As such it doesn't require any download or setup. Just browse to the page and you are in live edit mode. The closest thing I've run across so far is the non-open writely
I added the WYSIWYG back into http://CoTor.org. I'm not going to try and add the chat in before WikiSym. My focus at the moment is on getting the revision history worked out. I'm using something similar to the darcs theory of patches. Relates to BranchingWiki.
I wonder why you will start another effort while SynchroEdit is going to be released soon.
Thomas, one answer is that I need the functionality yesterday. Another is that I don't really have a good answer. I've learned a lot working on this project so far … the experience has been good.
And, I think that I should spend some time reading through their source before I do any more on CoTor. Thanks for the kick in the pants Thomas :)
SynchroEdit is more focused on simultaneous editing than I would like. Simultaneous editing necessary but not sufficient. CoTor will eventually move toward allowing disconnected editing and distributed serving. This means that the focus of development is different from SynchroEdit. The darcs-ish "theory of patches" revision history I'm implementing turns the history into a graph rather than a single linear progression (see BranchingWiki). You can be working on your own local fork in the graph without requiring connection to others who are also working on the document.
Right now I'm planning on simultaneous editing out of the box (no download/install required) and disconnected editing requiring an install. The install is a caching proxy webserver that stores local copies of the revision history graph for each page that you visit. This eventually leads to distributed serving.