blob: 8718d224985fdbd0557400325cd4d894ecea146a [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="img5.html"><img src="left.png" border=0 alt="Précédent"></a> <a href="img7.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="text6.html"><img src="text.png" border=0 alt="Texte"></a></center><br>
<img src="img6.png" alt="" style="float:left"/>
<p><p style="direction:ltr;">That is exactly why the main prupose of Intent is to keep your doc synchronized with your technical artifacts.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">Let's take a simple example : when you make a change the API of a Java plugin, the JDT automatically detects that a change occurred,
recompile the plugins that use the changed API and indicates with error markers the files in which this change lead to issues.</p>
<p style="direction:ltr;"></p>
<p style="direction:ltr;">Well we want the exact same thing with documentation : when you make a change in code (or models) that impacts the documentation,
Intent will detect that a change occurred, and place synchronization errors in the documentation parts that are related to the changed artifacts.</p>
<p style="direction:ltr;"></p>
</p>
</body>
</html>