Return-Path: <metasim@apache.org>
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 7015 invoked by uid 500); 24 Jan 2001 19:59:43 -0000
Delivered-To: apmail-jakarta-ant-cvs@apache.org
Received: (qmail 7006 invoked by uid 1209); 24 Jan 2001 19:59:42 -0000
Date: 24 Jan 2001 19:59:42 -0000
Message-ID: <20010124195942.7005.qmail@apache.org>
From: metasim@apache.org
To: jakarta-ant-cvs@apache.org
Subject: cvs commit: jakarta-ant/src/antidote/docs design-overview.html
 new-module-howto.html

metasim     01/01/24 11:59:42

  Modified:    src/antidote/docs design-overview.html new-module-howto.html
  Log:
  Updates to reflect some design changes.
  
  Revision  Changes    Path
  1.5       +15 -33    jakarta-ant/src/antidote/docs/design-overview.html
  
  Index: design-overview.html
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/src/antidote/docs/design-overview.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- design-overview.html	2000/12/19 21:02:22	1.4
  +++ design-overview.html	2001/01/24 19:59:40	1.5
  @@ -106,21 +106,17 @@
       to see an event before others, and in the case of <TT>AntEvent</TT
       objects, keep the event from propogating onward. The
       <TT>EventBus</TT> class defines the interrupt level constants
  -    <TT>MONITORING=1</TT>, <TT>VETOING=5</TT>, and <TT>RESPONDING=10</TT> to
  +    <TT>VETOING=1</TT>, <TT>MONITORING=5</TT>, and <TT>RESPONDING=10</TT> to
       help define categories of members. The implied purpose being that:
       <UL>
   
  -      <LI><TT>MONITORING</TT>: Just listens for events, like a logger
  -      or status monitor.</LI>
  -
         <LI><TT>VETOING</TT>: Listens for certain types of events, and
         may process them in a non-default manner to determine if the
         event should be cancelled before being dispatched to the
  -      <TT>RESPONDING</TT> group. An example of this might be to handle
  -      a <I>SaveAs</I> event, whereby a <TT>VETOING</TT> member will
  -      check to see if the file exists, and ask the user if they are
  -      sure they want to overwrite the existing file. The <I>SaveAs</I>
  -      event could then be cancelled before the operation is executed.</LI>
  +      <TT>RESPONDING</TT> group. 
  +
  +      <LI><TT>MONITORING</TT>: Just listens for events, like a logger
  +      or status monitor.</LI>
   
         <LI><TT>RESPONDING</TT>: Process events in a default manner,
         knowing that the event has passed any <TT>VETOING</TT> members.</LI>
  @@ -190,30 +186,16 @@
   
       <H2>Data Model and Views</H2>
   
  -    <P>The data model is mainly defined by the Ant application,
  -    primarily through the <TT>Project</TT>, <TT>Target</TT>, and
  -    <TT>Task</TT> classes.<P> However, Antidote defines the class
  -    <TT>ProjectProxy</TT> to act not only as a proxy to the real
  -    <TT>Project</TT> class, but also as creator of GUI <I>views</I> of
  -    the <TT>Project</TT>. A <I>view</I> is essentially a flyweight or
  -    data proxy; it provides an orgainizational perspective on the actual
  -    <TT>Project</TT> structure. For example, to render a
  -    <TT>JTree</TT> version of the <TT>Project</TT>, one would call the
  -    method <TT>ProjectProxy.getTreeModel()</TT>. Similarly, to get a
  -    <TT>Document</TT> version of the <TT>Project</TT>, the
  -    <TT>ProjectProxy,getDocument()</TT> method is used.</P>
  -
  -    <P><I>NB: This part of the architecture is not fleshed out very
  -    well. There needs to be a discussion of the degree to which the
  -    Antidote development should be able to impose changes on the Ant
  -    data model, and to what level that model should be mirrored in the
  -    Antidote code base. The coupling between them should be kept low,
  -    and at the same time changes to one should affect the other
  -    minimally. Still, features like property change events and bean
  -    introspection (or BeanInfo) may be needed to be added to the Ant
  -    data model. Having each view into the data go to the ProjectProxy
  -    for its data model may not be the best approach. In other words,
  -    lots of thought needs to occur here.</I></P>
  +    <P><I>NB: This part of the architecture is not fleshed out very well. There
  +    needs to be a discussion of the degree to which the Antidote development
  +    should be able to impose changes on the Ant data model, and to what level
  +    that model should be mirrored in the Antidote code base. The coupling
  +    between them should be kept low, and at the same time changes to one should
  +    affect the other minimally. Still, features like property change events and
  +    bean introspection (or BeanInfo) may be needed to be added to the Ant data
  +    model. Right now the data model is encapsulated in the package
  +    <TT>org.apache.tools.ant.gui.acs</TT> (where "<TT>acs</TT>" stands for "Ant
  +    Construction Set").</I></P>
   
       <H2>Application Context</H2>
   
  
  
  
  1.3       +5 -1      jakarta-ant/src/antidote/docs/new-module-howto.html
  
  Index: new-module-howto.html
  ===================================================================
  RCS file: /home/cvs/jakarta-ant/src/antidote/docs/new-module-howto.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- new-module-howto.html	2000/12/19 21:02:22	1.2
  +++ new-module-howto.html	2001/01/24 19:59:41	1.3
  @@ -26,7 +26,7 @@
       <P>NB: <I>Please submit updates and criticisms to this, particularly
       areas that were unclear, missing, or difficult to follow.</I></P>
   
  -    <H2>1) Specialize <TT>org.apache.tools.ant.gui.AntModule</TT></H2>
  +    <H2>1) Specialize <TT>org.apache.tools.ant.gui.core.AntModule</TT></H2>
   
       <P>All modules must inherit from the <TT>AntModule</TT>
       class. This will probably irritate some of you, but it essentially
  @@ -69,6 +69,10 @@
       name of your module appropriately. If multiple modules are listed
       for a single property (via a comma delimited list), then each
       module will have it's own tab in a <TT>javax.swing.JTabbedPane</TT>.
  +
  +    <P>NB:<I>This goofy way of constructing the main screen will probably 
  +    change to something much more general (but not as general as, say 
  +    <A HREF="http://www.alphaworks.ibm.com/tech/bml">BML</A>).</P>
   
       <H2>Run it!</H2>
       <P>That should be all you need to do, at least to get your module