| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" |
| "http://www.w3.org/TR/html4/transitional.dtd"> |
| <html> |
| <head> |
| <meta HTTP-EQUIV=CONTENT-TYPE CONTENT="text/html; charset=utf-8"> |
| <title>Create Useful Documentation with Mylyn Intent : transcript</title> |
| <link rel="stylesheet" type="text/css" href="talk.css"> |
| </head> |
| <body text="#000000" bgcolor="#FFFFFF" link="#000080" vlink="#0000CC" alink="#000080"> |
| <center> |
| <a href="img0.html"><img src="first.png" border=0 alt="Première page"></a> <a href="img25.html"><img src="left.png" border=0 alt="Précédent"></a> <a href="img27.html"><img src="right.png" border=0 alt="Suivant"></a> <a href="img29.html"><img src="last.png" border=0 alt="Dernière page"></a> <a href="Intent_ece2011.htm"><img src="home.png" border=0 alt="Résumé"></a> <a href="text26.html"><img src="text.png" border=0 alt="Texte"></a></center><br> |
| <img src="img26.png" alt="" style="float:left"/> |
| |
| <p><p style="direction:ltr;">One other major concern of Intent is <b>collaboration</b>, which is in the heart of the documentation process. </p> |
| <p style="direction:ltr;"></p> |
| <p style="direction:ltr;">I did not have time to talk about it, but in fact intent relies on a <b>distributed architecture</b>. We have a central repository, in which we store the Intent document as a model, and many other useful information (like all the compilation and synchronization issues or traceability informations).</p> |
| <p style="direction:ltr;"></p> |
| <p style="direction:ltr;">Each feature of Intent is managed by a client of this repository : the eclipse editor is just one among many. The synchronizer, compiler, indexer, doc exporter are also clients, that communicate through a notification mechanism ensured by the Repository. We can perfectly imagine an Orion-based Editor connected to such a repository.</p> |
| <p style="direction:ltr;"></p> |
| <p style="direction:ltr;">This repository concept is totally abstract, and can be developed with <b>many concrete back-ends</b>. For now, our repositry is an hidden folder in the eclipse workspace, but we would also like to define a CDO-based Intent Repository. If you do not know CDO, you should not have came here as it is being presented right now by Eike Stepper. In a nutshell, CDO allows live sharing of models, with real-times updates and lock management to avoid conflicts.</p> |
| <p style="direction:ltr;"></p> |
| <p style="direction:ltr;">With a CDO back-end, many users would be able to read and edit a same document, |
| and collaborate in real-time (a bit like Google doc). We could use a pessimist locking approach to avoid any conflict on the documentation.</p> |
| <p style="direction:ltr;"></p> |
| <p style="direction:ltr;">We have many other ideas in mind, and we would be glad to discuss with you to determine which would fit your needs.</p> |
| |
| </p> |
| </body> |
| </html> |
