Browse Source

*** empty log message ***

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@272133 13f79535-47bb-0310-9956-ffa450edef68
master
Peter Donald 23 years ago
parent
commit
cd18fd06e4
2 changed files with 26 additions and 0 deletions
  1. +16
    -0
      proposal/myrmidon/docs/todo.html
  2. +10
    -0
      proposal/myrmidon/src/xdocs/todo.xml

+ 16
- 0
proposal/myrmidon/docs/todo.html View File

@@ -88,6 +88,22 @@
sections describe some of the many things which still need to be done to sections describe some of the many things which still need to be done to
achieve that goal. This list is currently under construction.</p> achieve that goal. This list is currently under construction.</p>
<table border="0" cellspacing="0" cellpadding="2" width="100%"> <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"> <tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif"> <font color="#ffffff" face="arial,helvetica,sanserif">
<a name="XPath-like Locators for tasks"><strong>XPath-like Locators for tasks</strong></a> <a name="XPath-like Locators for tasks"><strong>XPath-like Locators for tasks</strong></a>


+ 10
- 0
proposal/myrmidon/src/xdocs/todo.xml View File

@@ -14,6 +14,16 @@
sections describe some of the many things which still need to be done to sections describe some of the many things which still need to be done to
achieve that goal. This list is currently under construction.</p> achieve that goal. This list is currently under construction.</p>


<subsection name="Rethink Notification/Event scheme">

<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>

</subsection>

<subsection name="XPath-like Locators for tasks"> <subsection name="XPath-like Locators for tasks">


<p>Most tasks are grouped into some sort of task container. The task containers <p>Most tasks are grouped into some sort of task container. The task containers


Loading…
Cancel
Save