Compatibility with subversion.

[ws]

I was thinking about a functionality that enables users to upload (or download) changes directly to a subversion repository, configured on the server. It would be possible to save different revision number, and restore them by a list like "documents list", or inside this list with a tree view when user select a document.

For example, when a user erase some datas on a document, they are lost. No way to restore them without this feature.

[anonymous]

This sounds like a very good idea. Some people have mentioned some kind of undo or versioning to be written for gobby. While an undo would be VERY nice (even just allowing each use to undo their OWN changes). But for versioning, simply letting the server chose an SVN server, then add a "commit", etc button to the clients would be very nice and probably not that hard to implement.

[armin]

Undo has already been implemented in Gobby 0.4.90.

The problem with the SVN part is not whether it is hard to implement or not. I think such a feature is beyond the scope of Gobby. Also, if we implement this for SVN, then people will request the same for git, bazaar, darcs, and others. I don't want to maintain all this.

Perhaps we will offer a plugin architecture some day, then stuff like SVN support (which do not belong to the "core" Gobby, but are still nice things to have for some people) can be added as a plugin.

[anonymous]

so... is it going to be a plugin architecture or an svn plugin? could make all the difference! You'd get lots of funky plugins from an architecture so I'd say separate tasks and do them both, but I'm not the programmer, just a potential user. I think SVN might be the thing to make gobby used at my workplace, but a plugin architecture could facilitate specialisation of people or teams towards web editing, games programming etc.