https://wiki.inkscape.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=DaleharveyInkscape Wiki - User contributions [en]2026-04-09T18:30:13ZUser contributionsMediaWiki 1.36.1https://wiki.inkscape.org/wiki/index.php?title=WhiteBoard&diff=12628WhiteBoard2007-01-16T13:10:05Z<p>Daleharvey: </p>
<hr />
<div><h3>Current Status (16/01/06)</h3><br />
<p>Can connect to both gristle.org and jabber.org using pedro, on establishing a whiteboard connection the reciever crashes</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=WhiteBoard&diff=12626WhiteBoard2007-01-16T13:08:58Z<p>Daleharvey: </p>
<hr />
<div><h3>Current Status</h3><br />
<p>Can connect to both gristle.org and jabber.org using pedro, on establishing a whiteboard connection the reciever crashes</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=WhiteBoard&diff=12624WhiteBoard2007-01-16T13:04:45Z<p>Daleharvey: </p>
<hr />
<div><h3>Current Status</h3></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=WhiteBoard&diff=12622WhiteBoard2007-01-16T13:04:32Z<p>Daleharvey: </p>
<hr />
<div><br />
<h2>Current Status</h2></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8260User:Daleharvey2006-09-04T21:34:37Z<p>Daleharvey: </p>
<hr />
<div><h2>Whiteboard</h2><br />
<br />
<p>I had intended on a working prototype at this point of the program, however an unexpected delay came up with a bug in server implementations which needs to be resolved, I am about to go on a holiday until the 27th and will not be able to undertake any more development until this time</p><br />
<br />
<p>Throughout the time of summer of code I had expected to complete a release worthy implementation of the whiteboard extension, however as I am yet to recieve the first payment from the program. I had to spend a significant time that i had planned on using on the whiteboard project in finding a job and working to get the money I had budgeted to recieve from google, which has seriously affected my timeline.</p><br />
<br />
<p>Following is a Todo list of the tasks I have yet to do, and a timescale in which i plan to implement them</p><br />
<br />
<h3>TODO</h3><br />
<ol><br />
<li>Finalise manually serialising incoming message - 2 days, 30th August</li><br />
<li>Apply incoming changes to the whiteboard - 5 days, 4th September</li><br />
<li>Finalise and implement MUC session establishment - 6 days, 9th September</li><br />
<li>implement conflict resolution - 5 days,14 September</li><br />
<li>I will give 2 weeks afterwards dedicated to making sure the whiteboard is release worthy</li><br />
</ol><br />
<br />
<p>Given this timescale I fully expect to have a release worthy implementation for October</p><br />
<br />
<h4>Progress</h4><br />
<ol><br />
<li>Serialising Incoming messages - done, jabber.org ensures the in-order processing</li><br />
<br />
<li>Apply Incoming Changes - 80% complete, need to handle special case nodes such as defs, and transformation matrices, plus ordering of objects</li><br />
<br />
<li>Conflict resolution - 90% complete, need to finalise rollbacks</li><br />
</ol><br />
<br />
<h3>Done</h3><br />
<ul><br />
<li>State and Session Handling<li><br />
<li>Peer to peer session establishment</li><br />
<li>Whiteboard clients broadcast all changes to the document</li><br />
<li>Developed a formal protocol in liason with joonas of the psi project location : http://debrowse.com/whiteboard/wb.xml</li><br />
</ul><br />
<br />
<p>Sorry to all who expected the whiteboard to be working at a time before this, for the reasons given above I have been unable to stick the the original schedule. However I fully plan on sticking to the timescale given and finishing the whiteboard. And of course after the whiteboard is complete I fully intend to carry on working on its, or other aspects of inkscapes future development</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8258User:Daleharvey2006-09-04T21:34:15Z<p>Daleharvey: </p>
<hr />
<div><h2>Whiteboard</h2><br />
<br />
<p>I had intended on a working prototype at this point of the program, however an unexpected delay came up with a bug in server implementations which needs to be resolved, I am about to go on a holiday until the 27th and will not be able to undertake any more development until this time</p><br />
<br />
<p>Throughout the time of summer of code I had expected to complete a release worthy implementation of the whiteboard extension, however as I am yet to recieve the first payment from the program. I had to spend a significant time that i had planned on using on the whiteboard project in finding a job and working to get the money I had budgeted to recieve from google, which has seriously affected my timeline.</p><br />
<br />
<p>Following is a Todo list of the tasks I have yet to do, and a timescale in which i plan to implement them</p><br />
<br />
<h3>TODO</h3><br />
<ol><br />
<li>Finalise manually serialising incoming message - 2 days, 30th August</li><br />
<li>Apply incoming changes to the whiteboard - 5 days, 4th September</li><br />
<li>Finalise and implement MUC session establishment - 6 days, 9th September</li><br />
<li>implement conflict resolution - 5 days,14 September</li><br />
<li>I will give 2 weeks afterwards dedicated to making sure the whiteboard is release worthy</li><br />
</ol><br />
<br />
<p>Given this timescale I fully expect to have a release worthy implementation for October</p><br />
<br />
<h2>Progress</h2><br />
<ol><br />
<li>Serialising Incoming messages - done, jabber.org ensures the in-order processing</li><br />
<br />
<li>Apply Incoming Changes - 80% complete, need to handle special case nodes such as defs, and transformation matrices, plus ordering of objects</li><br />
<br />
<li>Conflict resolution - 90% complete, need to finalise rollbacks</li><br />
</ol><br />
<br />
<h3>Done</h3><br />
<ul><br />
<li>State and Session Handling<li><br />
<li>Peer to peer session establishment</li><br />
<li>Whiteboard clients broadcast all changes to the document</li><br />
<li>Developed a formal protocol in liason with joonas of the psi project location : http://debrowse.com/whiteboard/wb.xml</li><br />
</ul><br />
<br />
<p>Sorry to all who expected the whiteboard to be working at a time before this, for the reasons given above I have been unable to stick the the original schedule. However I fully plan on sticking to the timescale given and finishing the whiteboard. And of course after the whiteboard is complete I fully intend to carry on working on its, or other aspects of inkscapes future development</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8082User:Daleharvey2006-08-15T20:23:14Z<p>Daleharvey: </p>
<hr />
<div><h2>Whiteboard</h2><br />
<br />
<p>I had intended on a working prototype at this point of the program, however an unexpected delay came up with a bug in server implementations which needs to be resolved, I am about to go on a holiday until the 27th and will not be able to undertake any more development until this time</p><br />
<br />
<p>Throughout the time of summer of code I had expected to complete a release worthy implementation of the whiteboard extension, however as I am yet to recieve the first payment from the program. I had to spend a significant time that i had planned on using on the whiteboard project in finding a job and working to get the money I had budgeted to recieve from google, which has seriously affected my timeline.</p><br />
<br />
<p>Following is a Todo list of the tasks I have yet to do, and a timescale in which i plan to implement them</p><br />
<br />
<h3>TODO</h3><br />
<ol><br />
<li>Finalise manually serialising incoming message - 2 days, 30th August</li><br />
<li>Apply incoming changes to the whiteboard - 5 days, 4th September</li><br />
<li>Finalise and implement MUC session establishment - 6 days, 9th September</li><br />
<li>implement conflict resolution - 5 days,14 September</li><br />
<li>I will give 2 weeks afterwards dedicated to making sure the whiteboard is release worthy</li><br />
</ol><br />
<br />
<p>Given this timescale I fully expect to have a release worthy implementation for October</p><br />
<br />
<h3>Done</h3><br />
<ul><br />
<li>State and Session Handling<li><br />
<li>Peer to peer session establishment</li><br />
<li>Whiteboard clients broadcast all changes to the document</li><br />
<li>Developed a formal protocol in liason with joonas of the psi project location : http://debrowse.com/whiteboard/wb.xml</li><br />
</ul><br />
<br />
<p>Sorry to all who expected the whiteboard to be working at a time before this, for the reasons given above I have been unable to stick the the original schedule. However I fully plan on sticking to the timescale given and finishing the whiteboard. And of course after the whiteboard is complete I fully intend to carry on working on its, or other aspects of inkscapes future development</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8080User:Daleharvey2006-08-15T20:21:36Z<p>Daleharvey: </p>
<hr />
<div><h2>Whiteboard</h2><br />
<br />
<p>I had intended on a working prototype at this point of the program, however an unexpected delay came up with a bug in server implementations which needs to be resolved, I am about to go on a holiday until the 27th and will not be able to undertake any more development until this time</p><br />
<br />
<p>Throughout the time of summer of code I had expected to complete a release worthy implementation of the whiteboard extension, however as I am yet to recieve the first payment from the program. I had to spend a significant time that i had planned on using on the whiteboard project in finding a job and working to get the money I had budgeted to recieve from google, which has seriously affected my timeline.</p><br />
<br />
<p>Following is a Todo list of the tasks I have yet to do, and a timescale in which i plan to implement them</p><br />
<br />
<h3>TODO</h3><br />
<ol><br />
<li>Finalise manually serialising incoming message - 2 days, 30th August</li><br />
<li>Apply incoming changes to the whiteboard - 5 days, 4th September</li><br />
<li>Finalise and implement MUC session establishment - 6 days, 9th September</li><br />
<li>implement conflict resolution - 5 days,14 September</li><br />
<li>I will give 2 weeks afterwards dedicated to making sure the whiteboard is release worthy</li><br />
</ol><br />
<br />
<p>Given this timescale I fully expect to have a release worthy implementation for October</p><br />
<br />
<h3>Done</h3><br />
<ul><br />
<li>State and Session Handling<li><br />
<li>Peer to peer session establishment</li><br />
<li>Whiteboard clients broadcast all changes to the document</li><br />
<li>Developed a formal protocol in liason with joonas of the psi project location :</li><br />
</ul><br />
<br />
<p>Sorry to all who expected the whiteboard to be working at a time before this, for the reasons given above I have been unable to stick the the original schedule. However I fully plan on sticking to the timescale given and finishing the whiteboard. And of course after the whiteboard is complete I fully intend to carry on working on its, or other aspects of inkscapes future development</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8078User:Daleharvey2006-08-15T20:09:11Z<p>Daleharvey: </p>
<hr />
<div><h2>Whiteboard</h2><br />
<br />
<p>I had intended on a working prototype at this point of the program, however an unexpected delay came up with a bug in server implementations which needs to be resolved, I am about to go on a holiday until the 27th and will not be able to undertake any more development until this time</p><br />
<br />
<p>Throughout the time of summer of code I had expected to complete a release worthy implementation of the whiteboard extension, however as I am yet to recieve the first payment from the program. I had to spend a significant time that i had planned on using on the whiteboard project in finding a job and working to get the money I had budgeted to recieve from google, which has seriously affected my timeline.</p><br />
<br />
<p>Following is a Todo list of the tasks I have yet to do, and a timescale in which i plan to implement them</p><br />
<br />
<h3>TODO</h3><br />
<ol><br />
<li>Manually serialise incoming message - 2 days, 30th August</li><br />
<li>Apply incoming changes to the whiteboard - 5 days, 4th September</li><br />
<li>Finalise and implement MUC session establishment - 6 days, 9th September</li><br />
<li>implement conflict resolution - 5 days,14 September</li><br />
<li>I will give 2 weeks afterwards dedicated to making sure the whiteboard is release worthy</li><br />
</ol><br />
<br />
<p>Given this timescale I fully expect to have a release worthy implementation for October</p><br />
<br />
<h3>Done</h3><br />
<ul><br />
<li>State and Session Handling<li><br />
<li>Peer to peer session establishment</li><br />
<li>Whiteboard clients broadcast all changes to the document</li><br />
<li>Developed a formal protocol in liason with joonas of the psi project location :</li><br />
</ul><br />
<br />
<p>Sorry to all who expected the whiteboard to be working at a time before this, for the reasons given above I have been unable to stick the the original schedule. However I fully plan on sticking to the timescale given and finishing the whiteboard. And of course after the whiteboard is complete I fully intend to carry on working on its, or other aspects of inkscapes future development</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8076User:Daleharvey2006-08-15T20:08:05Z<p>Daleharvey: </p>
<hr />
<div><h2>Whiteboard</h2><br />
<br />
<p>I had intended on a working prototype at this point of the program, however an unexpected delay came up with a bug in server implementations which needs to be resolved</p><br />
<br />
<p>Throughout the time of summer of code I had expected to complete a release worthy implementation of the whiteboard extension, however as I am yet to recieve the first payment from the program. I had to spend a significant time that i had planned on using on the whiteboard project in finding a job and working to get the money I had budgeted to recieve from google, which has seriously affected my timeline.</p><br />
<br />
<p>Following is a Todo list of the tasks I have yet to do, and a timescale in which i plan to implement them</p><br />
<br />
<h3>TODO</h3><br />
<ol><br />
<li>Manually serialise incoming message - 2 days, 30th August</li><br />
<li>Apply incoming changes to the whiteboard - 5 days, 4th September</li><br />
<li>Finalise and implement MUC session establishment - 6 days, 9th September</li><br />
<li>implement conflict resolution - 5 days,14 September</li><br />
<li>I will give 2 weeks afterwards dedicated to making sure the whiteboard is release worthy</li><br />
</ol><br />
<br />
<p>Given this timescale I fully expect to have a release worthy implementation for October</p><br />
<br />
<h3>Done</h3><br />
<ul><br />
<li>State and Session Handling<li><br />
<li>Peer to peer session establishment</li><br />
<li>Whiteboard clients broadcast all changes to the document</li><br />
<li>Developed a formal protocol in liason with joonas of the psi project location :</li><br />
</ul><br />
<br />
<p>Sorry to all who expected the whiteboard to be working at a time before this, for the reasons given above I have been unable to stick the the original schedule. However I fully plan on sticking to the timescale given and finishing the whiteboard. And of course after the whiteboard is complete I fully intend to carry on working on its, or other aspects of inkscapes future development</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8074User:Daleharvey2006-08-15T19:58:40Z<p>Daleharvey: </p>
<hr />
<div><h2>Whiteboard</h2><br />
<br />
<p>I had intended on a working prototype at this point of the program, however an unexpected delay came up with a bug in server implementations which needs to be resolved</p><br />
<br />
<p>Throughout the time of summer of code I had expected to complete a release worthy implementation of the whiteboard extension, however as I am yet to recieve the first payment from the program. I had to spend a significant time that i had planned on using on the whiteboard project in finding a job and working to get the money I had budgeted to recieve from google, which has seriously affected my timeline.</p><br />
<br />
<p>Following is a Todo list of the tasks I have yet to do, and a timescale in which i plan to implement them</p><br />
<br />
<h3>TODO</h3><br />
<ol><br />
<li>Manually serialise incoming message - 2 days, 30th August</li><br />
<li>Apply incoming changes to the whiteboard - 5 days, 3rd September</li><br />
<li>Finalise and implement MUC session establishment - 6 days</li><br />
<li>I will give 2/3 weeks afterwards dedicated to making sure the whiteboard is release worthy</li><br />
</ol><br />
<br />
<p>Given this timescale I fully expect to have a release worthy implementation for October</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8072User:Daleharvey2006-08-15T19:58:11Z<p>Daleharvey: </p>
<hr />
<div><h2>Whiteboard</h2><br />
<br />
<p>I had intended on a working prototype at this point of the program, however an unexpected delay came up with a bug in server implementations which needs to be resolved</p><br />
<br />
<p>Throughout the time of summer of code I had expected to complete a release worthy implementation of the whiteboard extension, however as I am yet to recieve the first payment from the program. I had to spend a significant time that i had planned on using on the whiteboard project in finding a job and working to get the money I had budgeted to recieve from google, which has seriously affected my timeline.</p><br />
<br />
<p>Following is a Todo list of the tasks I have yet to do, and a timescale in which i plan to implement them</p><br />
<br />
<h2>TODO</h2><br />
<ol><br />
<li>Manually serialise incoming message - 2 days, 30th August</li><br />
<li>Apply incoming changes to the whiteboard - 5 days, 3rd September</li><br />
<li>Finalise and implement MUC session establishment - 6 days</li><br />
<li>I will give 2/3 weeks afterwards dedicated to making sure the whiteboard is release worthy</li><br />
</ol><br />
<br />
<p>Given this timescale I fully expect to have a release worthy implementation for October</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8070User:Daleharvey2006-08-15T18:54:18Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8068User:Daleharvey2006-08-15T18:54:04Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
<br />
<br />
<br />
<h2>Notes</h2></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8066User:Daleharvey2006-08-15T18:53:50Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
<br />
<br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>5/07/06</em><br />
<p>graduation next week is interfering with the progression of the project, but i have managed to develop a system for reducing the undo history stack, and have decided on session establishment protocol,. I just really need to sort out the service discovery which needs input from other, finalised the protocol document up until that point</p><br />
<em>2/07/06</em><br />
<p>Still cant decide on a protocol for MUC session establishment, I think this will need to be voted, it has quite large effects on implementation. there has been talk about limiting the undo queue needed which is rather a large implementation detail. I am late with the first deliverable, but I think it was expected with how late I was starting the project, It has also been slowed down trying to get multiple parties to agree, It will certainly be ready in time along with the XML schema</p><br />
<em>1/07/06</em><br />
<p>Discussed some of the last issues with the JEP, MUC session establishment, I think we need to have another conference. Issue include service discovery, the sandbox and actual transfer of in band images</p><br />
<em>30/06/06</em><br />
<p>I actually wont need to patch ejabberd, somone has sent the patch, hopefully it will be introduced into latest stable, darcs is being incredibly annoying to install</p><br />
<em>29/06/06</em><br />
<p>Joonas and I have agreed on most protocol issues and decided to work on the same JEP. Some of the tradeoffs, I have agreed that &lt;new&gt; elements should be sent as raw svg, which means I have to compile change events to new svg elements. The other major one being that we will not use the id attribute to track elements, instead a whiteboard specific id given during the creation of an object</p><br />
<em>28/06/06</em><br />
<p>the first draft of the protocol used a revised version of the old inkboard session negotiation protocol, I think CAP / disco are more suitable for the initial stages of session establishment, so I am researching this to hopefully commit to a revised protocol soon<br /><br />
I also followed up the issue of presence stanzas being incorrectly ordered on ejabberd servers, it look like I would have to submit my own patch to resolve this</p><br />
<em>27/06/06</em><br />
<p>Dicussed with joonas about the integration of the jabber.org and my protocol, so far there are only 2 issues, address of elements, which I need to discuss with david yip, and the sending of native svg through the protocol. which is hopefully easy to resolve</p><br />
<em>26/06/06</em><br />
<p>Started my draft of the whiteboard protocol, for now I will keep an updated copy at http://debrowse.com/protocol.html<br /><br />
Jabber.org hosted a discussion on whiteboarding issues, it went quite well, as both peer to peer and muc with client side synchronisation are looking to be supported, with an option for muc with a server component</p><br />
<em>25/06/06</em><br />
<p>Have had a few problems integrating a jabber_whiteboard board specific gui to the pedro client, im going to put any development work on hold until I can get the protocol drafted</p><br />
<em>24/06/06</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/06</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/06</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/06</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=8064User:Daleharvey2006-08-15T18:53:33Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>5/07/06</em><br />
<p>graduation next week is interfering with the progression of the project, but i have managed to develop a system for reducing the undo history stack, and have decided on session establishment protocol,. I just really need to sort out the service discovery which needs input from other, finalised the protocol document up until that point</p><br />
<em>2/07/06</em><br />
<p>Still cant decide on a protocol for MUC session establishment, I think this will need to be voted, it has quite large effects on implementation. there has been talk about limiting the undo queue needed which is rather a large implementation detail. I am late with the first deliverable, but I think it was expected with how late I was starting the project, It has also been slowed down trying to get multiple parties to agree, It will certainly be ready in time along with the XML schema</p><br />
<em>1/07/06</em><br />
<p>Discussed some of the last issues with the JEP, MUC session establishment, I think we need to have another conference. Issue include service discovery, the sandbox and actual transfer of in band images</p><br />
<em>30/06/06</em><br />
<p>I actually wont need to patch ejabberd, somone has sent the patch, hopefully it will be introduced into latest stable, darcs is being incredibly annoying to install</p><br />
<em>29/06/06</em><br />
<p>Joonas and I have agreed on most protocol issues and decided to work on the same JEP. Some of the tradeoffs, I have agreed that &lt;new&gt; elements should be sent as raw svg, which means I have to compile change events to new svg elements. The other major one being that we will not use the id attribute to track elements, instead a whiteboard specific id given during the creation of an object</p><br />
<em>28/06/06</em><br />
<p>the first draft of the protocol used a revised version of the old inkboard session negotiation protocol, I think CAP / disco are more suitable for the initial stages of session establishment, so I am researching this to hopefully commit to a revised protocol soon<br /><br />
I also followed up the issue of presence stanzas being incorrectly ordered on ejabberd servers, it look like I would have to submit my own patch to resolve this</p><br />
<em>27/06/06</em><br />
<p>Dicussed with joonas about the integration of the jabber.org and my protocol, so far there are only 2 issues, address of elements, which I need to discuss with david yip, and the sending of native svg through the protocol. which is hopefully easy to resolve</p><br />
<em>26/06/06</em><br />
<p>Started my draft of the whiteboard protocol, for now I will keep an updated copy at http://debrowse.com/protocol.html<br /><br />
Jabber.org hosted a discussion on whiteboarding issues, it went quite well, as both peer to peer and muc with client side synchronisation are looking to be supported, with an option for muc with a server component</p><br />
<em>25/06/06</em><br />
<p>Have had a few problems integrating a jabber_whiteboard board specific gui to the pedro client, im going to put any development work on hold until I can get the protocol drafted</p><br />
<em>24/06/06</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/06</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/06</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/06</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7558User:Daleharvey2006-07-06T00:59:09Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>5/07/06</em><br />
<p>graduation next week is interfering with the progression of the project, but i have managed to develop a system for reducing the undo history stack, and have decided on session establishment protocol,. I just really need to sort out the service discovery which needs input from other, finalised the protocol document up until that point</p><br />
<em>2/07/06</em><br />
<p>Still cant decide on a protocol for MUC session establishment, I think this will need to be voted, it has quite large effects on implementation. there has been talk about limiting the undo queue needed which is rather a large implementation detail. I am late with the first deliverable, but I think it was expected with how late I was starting the project, It has also been slowed down trying to get multiple parties to agree, It will certainly be ready in time along with the XML schema</p><br />
<em>1/07/06</em><br />
<p>Discussed some of the last issues with the JEP, MUC session establishment, I think we need to have another conference. Issue include service discovery, the sandbox and actual transfer of in band images</p><br />
<em>30/06/06</em><br />
<p>I actually wont need to patch ejabberd, somone has sent the patch, hopefully it will be introduced into latest stable, darcs is being incredibly annoying to install</p><br />
<em>29/06/06</em><br />
<p>Joonas and I have agreed on most protocol issues and decided to work on the same JEP. Some of the tradeoffs, I have agreed that &lt;new&gt; elements should be sent as raw svg, which means I have to compile change events to new svg elements. The other major one being that we will not use the id attribute to track elements, instead a whiteboard specific id given during the creation of an object</p><br />
<em>28/06/06</em><br />
<p>the first draft of the protocol used a revised version of the old inkboard session negotiation protocol, I think CAP / disco are more suitable for the initial stages of session establishment, so I am researching this to hopefully commit to a revised protocol soon<br /><br />
I also followed up the issue of presence stanzas being incorrectly ordered on ejabberd servers, it look like I would have to submit my own patch to resolve this</p><br />
<em>27/06/06</em><br />
<p>Dicussed with joonas about the integration of the jabber.org and my protocol, so far there are only 2 issues, address of elements, which I need to discuss with david yip, and the sending of native svg through the protocol. which is hopefully easy to resolve</p><br />
<em>26/06/06</em><br />
<p>Started my draft of the whiteboard protocol, for now I will keep an updated copy at http://debrowse.com/protocol.html<br /><br />
Jabber.org hosted a discussion on whiteboarding issues, it went quite well, as both peer to peer and muc with client side synchronisation are looking to be supported, with an option for muc with a server component</p><br />
<em>25/06/06</em><br />
<p>Have had a few problems integrating a jabber_whiteboard board specific gui to the pedro client, im going to put any development work on hold until I can get the protocol drafted</p><br />
<em>24/06/06</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/06</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/06</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/06</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7557User:Daleharvey2006-07-06T00:57:53Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>5/06/05</em><br />
<p>graduation next week is interfering with the progression of the project, but i have managed to develop a system for reducing the undo history stack, and have decided on session establishment protocol,. I just really need to sort out the service discovery which needs input from other, finalised the protocol document up until that point</p><br />
<em>2/06/05</em><br />
<p>Still cant decide on a protocol for MUC session establishment, I think this will need to be voted, it has quite large effects on implementation. there has been talk about limiting the undo queue needed which is rather a large implementation detail. I am late with the first deliverable, but I think it was expected with how late I was starting the project, It has also been slowed down trying to get multiple parties to agree, It will certainly be ready in time along with the XML schema</p><br />
<em>1/06/05</em><br />
<p>Discussed some of the last issues with the JEP, MUC session establishment, I think we need to have another conference. Issue include service discovery, the sandbox and actual transfer of in band images</p><br />
<em>30/06/05</em><br />
<p>I actually wont need to patch ejabberd, somone has sent the patch, hopefully it will be introduced into latest stable, darcs is being incredibly annoying to install</p><br />
<em>29/06/05</em><br />
<p>Joonas and I have agreed on most protocol issues and decided to work on the same JEP. Some of the tradeoffs, I have agreed that &lt;new&gt; elements should be sent as raw svg, which means I have to compile change events to new svg elements. The other major one being that we will not use the id attribute to track elements, instead a whiteboard specific id given during the creation of an object</p><br />
<em>28/06/05</em><br />
<p>the first draft of the protocol used a revised version of the old inkboard session negotiation protocol, I think CAP / disco are more suitable for the initial stages of session establishment, so I am researching this to hopefully commit to a revised protocol soon<br /><br />
I also followed up the issue of presence stanzas being incorrectly ordered on ejabberd servers, it look like I would have to submit my own patch to resolve this</p><br />
<em>27/06/05</em><br />
<p>Dicussed with joonas about the integration of the jabber.org and my protocol, so far there are only 2 issues, address of elements, which I need to discuss with david yip, and the sending of native svg through the protocol. which is hopefully easy to resolve</p><br />
<em>26/06/05</em><br />
<p>Started my draft of the whiteboard protocol, for now I will keep an updated copy at http://debrowse.com/protocol.html<br /><br />
Jabber.org hosted a discussion on whiteboarding issues, it went quite well, as both peer to peer and muc with client side synchronisation are looking to be supported, with an option for muc with a server component</p><br />
<em>25/06/05</em><br />
<p>Have had a few problems integrating a jabber_whiteboard board specific gui to the pedro client, im going to put any development work on hold until I can get the protocol drafted</p><br />
<em>24/06/05</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7428User:Daleharvey2006-07-02T22:15:20Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>2/06/05</em><br />
<p>Still cant decide on a protocol for MUC session establishment, I think this will need to be voted, it has quite large effects on implementation. there has been talk about limiting the undo queue needed which is rather a large implementation detail. I am late with the first deliverable, but I think it was expected with how late I was starting the project, It has also been slowed down trying to get multiple parties to agree, It will certainly be ready in time along with the XML schema</p><br />
<em>1/06/05</em><br />
<p>Discussed some of the last issues with the JEP, MUC session establishment, I think we need to have another conference. Issue include service discovery, the sandbox and actual transfer of in band images</p><br />
<em>30/06/05</em><br />
<p>I actually wont need to patch ejabberd, somone has sent the patch, hopefully it will be introduced into latest stable, darcs is being incredibly annoying to install</p><br />
<em>29/06/05</em><br />
<p>Joonas and I have agreed on most protocol issues and decided to work on the same JEP. Some of the tradeoffs, I have agreed that &lt;new&gt; elements should be sent as raw svg, which means I have to compile change events to new svg elements. The other major one being that we will not use the id attribute to track elements, instead a whiteboard specific id given during the creation of an object</p><br />
<em>28/06/05</em><br />
<p>the first draft of the protocol used a revised version of the old inkboard session negotiation protocol, I think CAP / disco are more suitable for the initial stages of session establishment, so I am researching this to hopefully commit to a revised protocol soon<br /><br />
I also followed up the issue of presence stanzas being incorrectly ordered on ejabberd servers, it look like I would have to submit my own patch to resolve this</p><br />
<em>27/06/05</em><br />
<p>Dicussed with joonas about the integration of the jabber.org and my protocol, so far there are only 2 issues, address of elements, which I need to discuss with david yip, and the sending of native svg through the protocol. which is hopefully easy to resolve</p><br />
<em>26/06/05</em><br />
<p>Started my draft of the whiteboard protocol, for now I will keep an updated copy at http://debrowse.com/protocol.html<br /><br />
Jabber.org hosted a discussion on whiteboarding issues, it went quite well, as both peer to peer and muc with client side synchronisation are looking to be supported, with an option for muc with a server component</p><br />
<em>25/06/05</em><br />
<p>Have had a few problems integrating a jabber_whiteboard board specific gui to the pedro client, im going to put any development work on hold until I can get the protocol drafted</p><br />
<em>24/06/05</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7427User:Daleharvey2006-07-02T22:12:35Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>2/06/05</em><br />
<p>Still cant decide on a protocol for MUC session establishment, I think this will need to be voted, it has quite large effects on implementation. there has been talk about limiting the undo queue needed which is rather a large implementation detail</p><br />
<em>1/06/05</em><br />
<p>Discussed some of the last issues with the JEP, MUC session establishment, I think we need to have another conference. Issue include service discovery, the sandbox and actual transfer of in band images</p><br />
<em>30/06/05</em><br />
<p>I actually wont need to patch ejabberd, somone has sent the patch, hopefully it will be introduced into latest stable, darcs is being incredibly annoying to install</p><br />
<em>29/06/05</em><br />
<p>Joonas and I have agreed on most protocol issues and decided to work on the same JEP. Some of the tradeoffs, I have agreed that &lt;new&gt; elements should be sent as raw svg, which means I have to compile change events to new svg elements. The other major one being that we will not use the id attribute to track elements, instead a whiteboard specific id given during the creation of an object</p><br />
<em>28/06/05</em><br />
<p>the first draft of the protocol used a revised version of the old inkboard session negotiation protocol, I think CAP / disco are more suitable for the initial stages of session establishment, so I am researching this to hopefully commit to a revised protocol soon<br /><br />
I also followed up the issue of presence stanzas being incorrectly ordered on ejabberd servers, it look like I would have to submit my own patch to resolve this</p><br />
<em>27/06/05</em><br />
<p>Dicussed with joonas about the integration of the jabber.org and my protocol, so far there are only 2 issues, address of elements, which I need to discuss with david yip, and the sending of native svg through the protocol. which is hopefully easy to resolve</p><br />
<em>26/06/05</em><br />
<p>Started my draft of the whiteboard protocol, for now I will keep an updated copy at http://debrowse.com/protocol.html<br /><br />
Jabber.org hosted a discussion on whiteboarding issues, it went quite well, as both peer to peer and muc with client side synchronisation are looking to be supported, with an option for muc with a server component</p><br />
<em>25/06/05</em><br />
<p>Have had a few problems integrating a jabber_whiteboard board specific gui to the pedro client, im going to put any development work on hold until I can get the protocol drafted</p><br />
<em>24/06/05</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7426User:Daleharvey2006-07-02T22:04:37Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<br />
<em>1/06/05</em><br />
<p>Discussed some of the last issues with the JEP, MUC session establishment, I think we need to have another conference. Issue include service discovery, the sandbox and actual transfer of in band images</p><br />
<em>30/06/05</em><br />
<p>I actually wont need to patch ejabberd, somone has sent the patch, hopefully it will be introduced into latest stable, darcs is being incredibly annoying to install</p><br />
<em>29/06/05</em><br />
<p>Joonas and I have agreed on most protocol issues and decided to work on the same JEP. Some of the tradeoffs, I have agreed that &gt;new&lt; elements should be sent as raw svg, which means I have to compile change events to new svg elements. The other major one being that we will not use the id attribute to track elements, instead a whiteboard specific id given during the creation of an object</p><br />
<em>28/06/05</em><br />
<p>the first draft of the protocol used a revised version of the old inkboard session negotiation protocol, I think CAP / disco are more suitable for the initial stages of session establishment, so I am researching this to hopefully commit to a revised protocol soon<br /><br />
I also followed up the issue of presence stanzas being incorrectly ordered on ejabberd servers, it look like I would have to submit my own patch to resolve this</p><br />
<em>27/06/05</em><br />
<p>Dicussed with joonas about the integration of the jabber.org and my protocol, so far there are only 2 issues, address of elements, which I need to discuss with david yip, and the sending of native svg through the protocol. which is hopefully easy to resolve</p><br />
<em>26/06/05</em><br />
<p>Started my draft of the whiteboard protocol, for now I will keep an updated copy at http://debrowse.com/protocol.html<br /><br />
Jabber.org hosted a discussion on whiteboarding issues, it went quite well, as both peer to peer and muc with client side synchronisation are looking to be supported, with an option for muc with a server component</p><br />
<em>25/06/05</em><br />
<p>Have had a few problems integrating a jabber_whiteboard board specific gui to the pedro client, im going to put any development work on hold until I can get the protocol drafted</p><br />
<em>24/06/05</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7351User:Daleharvey2006-06-28T12:00:33Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>28/06/05</em><br />
<p>the first draft of the protocol used a revised version of the old inkboard session negotiation protocol, I think CAP / disco are more suitable for the initial stages of session establishment, so I am researching this to hopefully commit to a revised protocol soon<br /><br />
I also followed up the issue of presence stanzas being incorrectly ordered on ejabberd servers, it look like I would have to submit my own patch to resolve this</p><br />
<em>27/06/05</em><br />
<p>Dicussed with joonas about the integration of the jabber.org and my protocol, so far there are only 2 issues, address of elements, which I need to discuss with david yip, and the sending of native svg through the protocol. which is hopefully easy to resolve</p><br />
<em>26/06/05</em><br />
<p>Started my draft of the whiteboard protocol, for now I will keep an updated copy at http://debrowse.com/protocol.html<br /><br />
Jabber.org hosted a discussion on whiteboarding issues, it went quite well, as both peer to peer and muc with client side synchronisation are looking to be supported, with an option for muc with a server component</p><br />
<em>25/06/05</em><br />
<p>Have had a few problems integrating a jabber_whiteboard board specific gui to the pedro client, im going to put any development work on hold until I can get the protocol drafted</p><br />
<em>24/06/05</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7350User:Daleharvey2006-06-28T10:01:28Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>27/06/05</em><br />
<p>the first draft of the protocol used a revised version of the old inkboard session negotiation protocol, I think CAP / disco are more suitable for the initial stages of session establishment, so I am researching this to hopefully commit to a revised protocol soon</p><br />
<em>27/06/05</em><br />
<p>Dicussed with joonas about the integration of the jabber.org and my protocol, so far there are only 2 issues, address of elements, which I need to discuss with david yip, and the sending of native svg through the protocol. which is hopefully easy to resolve</p><br />
<em>26/06/05</em><br />
<p>Started my draft of the whiteboard protocol, for now I will keep an updated copy at http://debrowse.com/protocol.html<br /><br />
Jabber.org hosted a discussion on whiteboarding issues, it went quite well, as both peer to peer and muc with client side synchronisation are looking to be supported, with an option for muc with a server component</p><br />
<em>25/06/05</em><br />
<p>Have had a few problems integrating a jabber_whiteboard board specific gui to the pedro client, im going to put any development work on hold until I can get the protocol drafted</p><br />
<em>24/06/05</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7294User:Daleharvey2006-06-25T01:57:38Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>24/06/05</em><br />
<p>Managed to fix the windows build, it ignored makefiles_insert<br />
and compiled old code, there are issues with compilation against older <br />
versions of gtk.</p><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7289User:Daleharvey2006-06-23T20:48:57Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7288User:Daleharvey2006-06-23T20:48:12Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p><br />
<br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<br />
<br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7287User:Daleharvey2006-06-23T20:46:56Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p><br />
<em>23/06/05</em><br />
<p>I spent today merging the INKBOARD_PEDRO branch with the trunk, all works well on linux, I have disabled inkboard to be built on windows for the time being as there is some rather confusing compile errors, which I will hopefully fix tomorrow</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7248User:Daleharvey2006-06-22T18:04:02Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Notes</h2><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7247User:Daleharvey2006-06-22T18:02:30Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following</p><ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br />
<p>I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</p><br />
<em>22/06/05</em><br />
<p>After discussion with David Yip and Joonas of the jabber.org SoC project, A proposal has been set for conflict resolution, I have started extending the protocol document that can be found in the pedro branch. We are setting up a time convenient for a whiteboard related conference in the next week or so</p></div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7246User:Daleharvey2006-06-22T17:58:49Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following<ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br /><br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7245User:Daleharvey2006-06-22T17:58:07Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following<ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br /><br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7244User:Daleharvey2006-06-22T17:57:37Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following<ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br /><br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7243User:Daleharvey2006-06-22T17:56:44Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li><h3>Deliverable 3 - Friday 28th July</h3><br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following<ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li><h3>Final Deliverable - Monday 21th August</h3><br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br /><br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7242User:Daleharvey2006-06-22T17:55:35Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li>Deliverable 3 - Friday 28th July<br />
<p>A basic inkboard client developed using the perdo XMPP client, must be stable enough to be integrated with the trunk, that contains at least the following<ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li>Final Deliverable - Monday 21th August<br />
<p>End of Summer of Code project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
</li><br />
</ul><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br /><br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7241User:Daleharvey2006-06-22T17:53:32Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 14th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<li>Deliverable 3 - Friday 28th July<br />
<p>A basic inkboard client developed using the perdo XMPP client, that contains at least the following<ul><li>Initialisation and Destruction of multi user and peer to peer session</li><li>Basic communication of changes between documents</li></ul></li><br />
<li>Final Deliverable - Monday 21th August<br />
<p>End of Summer ofCode project, a fully stable inkboard intergrated into the inkscape trunk, ready for inclusion in the release of .45, features to include:<br />
<ul><li>Conflict Resolution</li><li>Local Undo mechanism</li></ul></p><br />
<li><br />
</ul><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br /><br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7240User:Daleharvey2006-06-22T17:41:22Z<p>Daleharvey: </p>
<hr />
<div><h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1 - Friday, 30th June</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating as much of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li>Specification for conflict resolution</li><br />
<li>Use Case for peer to peer and Multi User Chat session establishment</li><br />
<li>Use Case for communication of edits between sessions</li><br />
<li>Listing of valid message types</li><br />
<li>State transition diagram of Inkboard Clients</li><br />
</ul><br />
</li><br />
<li><h3>Deliverable 2 - Friday, 7th July</h3><br />
<p>Develop and finalise the XML schema that is implemented by the inkboard clients, this will define the valid message types that may be transferred</p><br />
</li><br />
<br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br /><br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7239User:Daleharvey2006-06-22T17:28:51Z<p>Daleharvey: </p>
<hr />
<div><ol><br />
<li>OverView</li><br />
<li>Predicted TimeLine</li><br />
<li>Notes</li><br />
<li>Project Log</li><br />
</ol><br />
<br />
<h2>OverView</h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<h2>Predicted TimeLine</h2><br />
<ul><br />
<li><h3>Deliverable 1</h3><br />
<p>Extend and finalise the initial draft of the protocol specification started<br />
by David Yip (/src/jabber_whiteboard/protocol/protocol.tex), intergrating some of the standard protocol underdevelopment at http://wiki.jabber.org/index.php/Psi_Whiteboarding which must include the following</p><br />
<ul><li><br />
<br />
<h2>Project Log</h2><br />
<em>21/06/05</em><br /><br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7238User:Daleharvey2006-06-22T17:23:46Z<p>Daleharvey: </p>
<hr />
<div><ol><br />
<li>OverView</li><br />
<li>Predicted TimeLine</li><br />
<li>Notes</li><br />
<li>Project Log</li><br />
</ol><br />
<br />
<h2><a name="OverView">OverView</a></h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<br />
<h2>Project Log</h2><br />
<br />
<em>21/06/05</em><br /><br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7237User:Daleharvey2006-06-22T17:22:27Z<p>Daleharvey: </p>
<hr />
<div><ol><br />
<li>[OverView]</li><br />
<li>Predicted TimeLine</li><br />
<li>Project Log</li><br />
<ol><br />
<br />
<h2><a name="OverView">OverView</a></h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<br />
21/06/05<br />
<br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7236User:Daleharvey2006-06-22T17:21:33Z<p>Daleharvey: </p>
<hr />
<div><ol><br />
<li>[[OverView]]</li><br />
<li>Predicted TimeLine</li><br />
<li>Project Log</li><br />
<ol><br />
<br />
<h2><a name="OverView">OverView</a></h2><br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<br />
21/06/05<br />
<br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7235User:Daleharvey2006-06-22T17:18:43Z<p>Daleharvey: </p>
<hr />
<div>With the recent worry about the lack of communication between soc<br />
participants and the inkscape team, and any worry about the obvious <br />
lack of progress on my part<br />
<br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<ul><br />
<li>Project Timeline</li><br />
</ul><br />
<br />
21/06/05<br />
<br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7114User:Daleharvey2006-06-21T04:12:10Z<p>Daleharvey: </p>
<hr />
<div>With the recent worry about the lack of communication between soc<br />
participants and the inkscape team, and any worry about the obvious <br />
lack of progress on my part<br />
<br />
I have decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
<br />
21/06/05<br />
<br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocol</div>Daleharveyhttps://wiki.inkscape.org/wiki/index.php?title=User:Daleharvey&diff=7113User:Daleharvey2006-06-21T04:00:34Z<p>Daleharvey: </p>
<hr />
<div>Ive decided to set up this page as my log for the google summer of <br />
code project, formalising the protocol for inkboard communication <br />
and converting the library to pedro.<br />
<br />
21/06/05<br />
I have finished uni and can start working full time on the protocol / lib<br />
conversion. We have decided to integrate the whiteboard gui into the pedro <br />
gui. I am starting my work with adding the whiteboard gui into pedro, and<br />
defining groupchat and peer to peer initialisation protocollll</div>Daleharvey