Antidote Design Overview

[Simeon Fitch <me...@yahoo.com>]

Antidites,

I have completed a rough overview of my thoughts
behind the architecture of the Antidote application, 
(attached below). It currently reflects the approach
that is defined by the current source code. I'm
interested in any thoughts or recommendations you
might have.

Of particular concern to me (in terms of getting a
discussion going) is the relationship between the GUI
and the Ant "data model", as defined by the Project,
Target, and Task classes. I believe that the GUI
should rely heavily on these rather than "mirroring"
them, but this gets into the issue of how much we
should allow the GUI levy requirements on the Ant data
model (or other Ant classes for that matter). For
example, a data model for a GUI often supports the
generation of "PropertyChangeEvent" objects whenever
one of the data object's properties/state values
changes. This allows multiple views to register
interest in a sigle data object, and be gauranteed to
be kept in sync with changes in the data. This is only
one example of potentially many where the GUI needs to
impose changes to the Ant data model, or instead
mirror the data model in its own code base. Obviously
there are pros and cons to both approaches, but that
is why there needs to be a discussion here at some
point on this.

Hopefully this document should aid in allowing others
to start contributing. The next thing I plan to do is
start a TODO doc that should help define what initial
efforts should focus on.

Conor: would you mind checking this document into the
jakarta-ant/src/antidote/docs directory?

Thanks,

Simeon

=====
Mustard Seed Software
mailto:simeon@fitch.net

__________________________________________________
Do You Yahoo!?