<div>Hello!</div>
<div> </div>
<div>We haven't see the question asked by Dag about our criteria for selecting things to do.</div>
<div>To answer this question it is easy! (or ISI as you wants :P)</div>
<div>We have studied the TODO list of KPlato on SVN and after clear it from all things which were done we have selected those which seems to be most important and easily realisable during our project.</div>
<div>We are studiing a another items to do, relative to the PERT method, it will consist to find a simple way to key PERT data and so to calculate particulary things of the PERT method without a graph.</div>
<div> </div>
<div>Best regards.</div>
<div><br> </div>
<div><span class="gmail_quote">2006/11/10, Gaël de Chalendar <<a href="mailto:Gael.de-Chalendar@cea.fr">Gael.de-Chalendar@cea.fr</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hello,<br><br>Le vendredi 10 novembre 2006 08:30, Dag Andersen a écrit:<br>> Torsdag 09 november 2006 18:34 skrev Kevin Ottens:
<br>> > I'm wondering about this one. I'm not 100% about the semantic of this<br>> > dependency. Could someone enlighten me?<br>><br>> task1 <--- task2.<br>> means task2 has to start before task1 can finish, so I suppose task2 should
<br>> be calculated first.<br>> I don't think there are many use cases for it, I can't pull one from the<br>> top of my head just now ;)<br>Maybe some specifications (like a file format) of task2 (that could be<br>
splitted in more detailed subtasks) should be finished to allow the final<br>implementation of task1 ?<br>This allows to have some tasks not too much detailed.<br><br>Regards,<br><br>Gaël<br>_______________________________________________
<br>kplato mailing list<br><a href="mailto:kplato@kde.org">kplato@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/kplato">https://mail.kde.org/mailman/listinfo/kplato</a><br></blockquote></div><br>