blob: eaf96de81a949723a1e0eb8f38bd6532252e8165 [file] [log] [blame]
<!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="img24.html"><img src="left.png" border=0 alt="Précédent"></a> <a href="img26.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="text25.html"><img src="text.png" border=0 alt="Texte"></a></center><br>
<img src="img25.png" alt="" style="float:left"/>
<p><p style="direction:ltr;">We are eager to integrate Mylyn Tasks and Intent.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">A first step will be to <b>embed Intent Document inside Mylyn contexts</b>. The major benefit compared to textile files
is that you will only embed the documentations parts that are <b>actually related to your tasks</b>, and not the whole file.
This integration seems quite easy as in fact, an Intent Document is stored as a model, and not a textual file. So we can use the Mylyn bridge for modeling.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">We would also like to be able to <b>reference Mylyn Tasks inside Intent documents</b>.
That would allow to apply validation rules on any tasks : for example, a bugzilla issue should not be closed if the test has not been written.</p>
</p>
</body>
</html>