On Wed, 8 Feb 2006, Dale Harvey wrote:
windows support is pretty high priority in my project, I would really appreciate an update to where this is at and whats needed to get it working
I'm not sure if you've already done this, but there is an unofficial patch to loudmouth on Windows. My understanding is that it won't work at all without that patch, and that patch doesn't work all the time :) Hence the switching to a new jabber library.
One thing that I think is the most difficult (and probably could be a full
year in
itself) is the issue of undo/redo
the prototype i developed took quite a different approach, I used a lock mechanism that each user had to gain a lock on an object that they needed to edit before being allowed to edit / add objects, this way all edits were atomic and would solve the issue with undo, I planned a structure simliar to illustrators nested layers, to allow a user to gain a lock on a parent layer, so and edits to children wouldnt go through the time consuming procedure of gaining a lock. I still believe this way is possible using <svg:g and presence stanzas, I need to look further into the inkboard architecture for this though. I do believe somone in glasgow university is doing a paper on undo / redo in a conflict resolution envoiroment though
Well, I don't think locking really helps the situation. You still can only undo/redo your local changes. And you introduce many more problems. What happens if someone's computer crashes who has a lock on a section of the document? How do users communicate that they would like the lock? What if a slow user is the one doing the locking, does everyone suffer? What if one client doesn't get, or like the lock, does everyone reject the changes by that client?
I would be interested to see the paper from Glasgow U.
Also, Inkscape already provides the basic functionality, in that you can lock layers. But, there is no way to assign locks to a particular user, or a communication mechanism in Inkboard to support that.
--Ted