On Tue, 7 Feb 2006, Dale Harvey wrote:
I am a student doing a 4th year project, studying the usability / workflow effects of a multi user vector graphics prorgam, at the time, I had not heard of inkboard, and planned on
This an interesting topic. I'd be interested in your paper. One thing that I think is the most difficult (and probably could be a full year in itself) is the issue of undo/redo. In Inkboard currently we're leaving undo/redo to the current user's edits. This is probably the simplest solution that makes sense, but I'm not sure it is the best. Probably what is best involves something to do with the user's loci of focus. If someone else changes the object they're working on, they want to be able to undo that easily. But, if they hit undo, they don't want someone else's edit that they can't see to change.
My plan is to take inkboard (either the rewrite or current release, depending on the rewrite state) and modify it to fit my requirements, due to the timescale on my project, and my lack of experience with open source development, I would not be looking to join inkscape development team immediately, if all goes well with my project, I would be happy to contribute my effort to inkboard after your review.
On the technical side, I would recommend using SVK. That way you can keep a local branch, and SVK will keep you up to date with the Inkscape main line. We've had divergence before with Inkboard, I'd hate to have that again.
Also, in general it is easier to review small patches. If you could send small features as you finish them, that would be much better than a thousand page patch when you are all done.
Welcome!
--Ted