Thanks for the replies
As for where you begin: either is fine. I have been focusing my efforts on the rewrite, since getting Windows support is a really big deal, but it is not yet very complete. So starting out with the current Inkboard would also be great.
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
You may want to join the whiteboarding list http://mail.jabber.org/mailman/listinfo/whiteboarding
joined, thanks
I try to shoot helpful comments his way every now and then, but I haven't been all that successful with inkboard lately either
acspike has been really helpful trying to get this working cheers
Can you give some more detail on the problems you've been experiencing?
the configure goes through fine with inkboard enabled, ive built it from the current stable, and a package provided by acspike, (the latest svn gives me a syntax error with configure, but thats for another thread) which both install fine with inkboard enable, and they both have the same problems with the respective loudmouth install, I am going to try a quick reformat today and try again, to see if I have mucked up my loudmouth libs with multiple installs, the actual problem is
loudmouth .17 -> when I click connect to server, enter my details (I use my gristle.org account) when I click connect, the status bar changes to establishing connection, but then inkscape crashes, the dialogue does go away, when i move it the canvas behind stays black, eventually everything dissapears, after pressing ctr+c the following shows ( I ented Dale3@...896... in the dialogue, I assumed thats the right format) ** (inkscape:6265): WARNING **: Null recipient JID specified; not sending message.
loudmouth 1.0.1 -> I connect fine, when i choose invite user to share, inkscape crashes, with a generic "inkscape has encountered an internal problem and will close now" QPixmap: Invalid pixmap parameters QPainter::begin: Cannot paint null pixmap QPainter::setPen: Will be reset by begin() QPainter::setBrush: Will be reset by begin() QPainter::setBrush: Will be reset by begin() QPainter::setPen: Will be reset by begin()
Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Segmentation fault
is printed to shell
loudmouth 1.0 -> no crashes !, I click invite to user, enter the user, it says its sending it, but the message is discarded in the message_handler, i get 3 messages, "message recieved in invalid context, discarding message"
the consistency with the errors in different loudmouth installs leads me to think its a problem with loudmouth (or my install) and not with inkboard itself, although it should really be recovering
I am going to do a quick format later today, and try acspikes package again, then I will try some quick test with loudmouth without inkboard to see if thats working fine, (these are built on suse 9.2)
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
Thanks
Dale Harvey