|
|
@@ -88,6 +88,22 @@ |
|
|
|
sections describe some of the many things which still need to be done to |
|
|
|
achieve that goal. This list is currently under construction.</p> |
|
|
|
<table border="0" cellspacing="0" cellpadding="2" width="100%"> |
|
|
|
<tr><td bgcolor="#828DA6"> |
|
|
|
<font color="#ffffff" face="arial,helvetica,sanserif"> |
|
|
|
<a name="Rethink Notification/Event scheme"><strong>Rethink Notification/Event scheme</strong></a> |
|
|
|
</font> |
|
|
|
</td></tr> |
|
|
|
<tr><td> |
|
|
|
<blockquote> |
|
|
|
<p>We need to rethink the whole notificaiton scheme. Should tasks be able to |
|
|
|
raise events? Probably as long as we have <em>ContainerTasks</em>. Should tasks |
|
|
|
be able to query state of run? ie Can a task request "are we paused?" or "are we |
|
|
|
stopped?" ? Probably as that way long running tasks are given the opportunity |
|
|
|
to be gracefully halted by the end users (primarily aimed at IDE vendors here).</p> |
|
|
|
</blockquote> |
|
|
|
</td></tr> |
|
|
|
</table> |
|
|
|
<table border="0" cellspacing="0" cellpadding="2" width="100%"> |
|
|
|
<tr><td bgcolor="#828DA6"> |
|
|
|
<font color="#ffffff" face="arial,helvetica,sanserif"> |
|
|
|
<a name="XPath-like Locators for tasks"><strong>XPath-like Locators for tasks</strong></a> |
|
|
|