 | + | |
|
-  |
+
|
+
| + | |
|
- |
+
|
+
| + | |
|
- |
+
|
+
| + | |
|
- |
+
|
+
| + | |
|
- |
+
|
+
To acheive this modularity, a high level of decoupling is +
To achieve this modularity, a high level of decoupling is necessary. The standard UI design approach of providing separation of view (presentation) from model (data) is applied, leveraging the built-in Ant data model where possible, as well as the - predifined Swing model interfaces. Furthermore, the architecture + predefined Swing model interfaces. Furthermore, the architecture is highly event driven, whereby modules communicate via a shared communications channel.
@@ -228,7 +228,7 @@ objects, as well as
AWTEvent objects can be posted (if desired). A
new class of events called AntEvent is defined for Antidote
specific events, which have the additional capability of being
- cancelled mid-dispatch.
+ canceled mid-dispatch.
Each BusMember must provide a BusFilter instance,
which is the members' means of telling the bus which
@@ -241,7 +241,7 @@
for dispatching EventObjects to BusMembers. The
purpose of this is to allow certain BusMember instances
to see an event before others, and in the case of AntEvent
- objects, keep the event from propogating onward. The
+ objects, keep the event from propagating onward. The
EventBus class defines the interrupt level constants
VETOING=1, MONITORING=5, and RESPONDING=10 to
help define categories of members. The implied purpose being that:
@@ -250,7 +250,7 @@
VETOING: 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
+ event should be canceled before being dispatched to the
RESPONDING group.
Within a specific interrupt level, the order in which members will
- receive events is undefied. A BusMember may be registered
+ receive events is undefined. A BusMember may be registered
at a level that is +/- of one of the defined levels, as long as it
follows the constraint MONITORING <= interruptLevel <=
MAX_INTERRUPT.
@@ -322,7 +322,7 @@
The purpose of this encapsulation is to allow the clean separation of making a request, and servicing a request. Due to - various conditions in the application state, the actualy response + various conditions in the application state, the actually response to a request may change, as well as who services it. This design approach facilitates that.
@@ -344,7 +344,7 @@| Application Context |
In order to keep the coupling amoung application modules to a +
In order to keep the coupling among application modules to a
minimum, a single point of reference is needed for coordination
and data sharing. The class AppContext is the catch-all
class for containing the application state. Most modules and
@@ -362,9 +362,9 @@
Full "i18n" support should be assumed in modern applications,
and all user viewable strings should be defined in a configuration
- file. For Antidote this configuraiton file is
+ file. For Antidote this configuration file is
antidote.properties, which is located (with other UI
- resources) in the subpackage "resources".
+ resources) in the sub-package "resources".
To aid in the lookup of text properties, as well as other
resources like icons, a class called ResourceManager is
@@ -373,7 +373,7 @@
values as easy as possible.
The organization of configuration properties is based on the
- fully qualifed path of the class that requires the property. For
+ fully qualified path of the class that requires the property. For
example, the "about" box contains a messages, so it looks for the
property "org.apache.tools.ant.gui.About.message" for the text
message it should display. Therefore, the ResourceManager
diff --git a/docs/projects/antidote/index.html b/docs/projects/antidote/index.html
index 56ec7e15f..42ffac1ce 100644
--- a/docs/projects/antidote/index.html
+++ b/docs/projects/antidote/index.html
@@ -154,10 +154,10 @@
... in fact it is the Ant GUI by the Apache Ant project itself, because, - as you might know, there are several other grafical user interfaces covering Ant. + as you might know, there are several other graphical user interfaces covering Ant. Most of them are integrated in IDEs such as NetBeans or Eclipse. To be honest Antidote - has started a long time ago (spring 2000) and was designed to become integratible into + has started a long time ago (spring 2000) and was designed to become integrable into IDEs by it's original Author Simeon H. K. Fitch, who did the most work on Antidote. Unfortunately the Antidote community never came really "to speed" and so the IDE-guys where faster with their integrations. @@ -166,13 +166,13 @@ interest in such a tool...
Anyways: The "sleeping beauty" Antidote has been awaken and is now being developed to - a full featured, stand alone, JFC/Swing-based Ant GUI to grafically create, edit and run + a full featured, stand alone, JFC/Swing-based Ant GUI to graphically create, edit and run build-files to be quite useful for the developer who do not use an IDE at all. So one of the goals of Antidote development is to make it small, fast and really neat :)!
| Get a glimps |
| Get a glimpse |
@@ -189,7 +189,7 @@
AntModule.contextualize() method has been called. Follow
the naming convention currently used in the properties file and
you should have to problems. This task should be done
- during development of your module. Under no cercumstances
+ during development of your module. Under no circumstances
should your module be submitted or committed without this task
being completed. Remember that Antidote has an international
audience.
diff --git a/docs/projects/index.html b/docs/projects/index.html
index 21b1a3e57..e1241a3e2 100644
--- a/docs/projects/index.html
+++ b/docs/projects/index.html
@@ -157,7 +157,7 @@
Web-Page for Ant sub-projects. In the first step Antidote,
the Ant GUI, is included, but some others may follow!
- To make shure you do not miss anything: Stay tuned and visit this page from time to time :)! +
To make sure you do not miss anything: Stay tuned and visit this page from time to time :)!
diff --git a/docs/resources.html b/docs/resources.html index 0728cd82c..d2d6dd116 100644 --- a/docs/resources.html +++ b/docs/resources.html @@ -50,14 +50,21 @@ | + | |
|
- |
+
|
+
| + | |
|
- |
+
|
+
To acheive this modularity, a high level of decoupling is +
To achieve this modularity, a high level of decoupling is necessary. The standard UI design approach of providing separation of view (presentation) from model (data) is applied, leveraging the built-in Ant data model where possible, as well as the - predifined Swing model interfaces. Furthermore, the architecture + predefined Swing model interfaces. Furthermore, the architecture is highly event driven, whereby modules communicate via a shared communications channel.
@@ -83,7 +83,7 @@ objects, as well asAWTEvent objects can be posted (if desired). A
new class of events called AntEvent is defined for Antidote
specific events, which have the additional capability of being
- cancelled mid-dispatch.
+ canceled mid-dispatch.
Each BusMember must provide a BusFilter instance,
@@ -98,7 +98,7 @@
for dispatching EventObjects to BusMembers. The
purpose of this is to allow certain BusMember instances
to see an event before others, and in the case of AntEvent
- objects, keep the event from propogating onward. The
+ objects, keep the event from propagating onward. The
EventBus class defines the interrupt level constants
VETOING=1, MONITORING=5, and RESPONDING=10 to
help define categories of members. The implied purpose being that:
@@ -107,7 +107,7 @@
VETOING: 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
+ event should be canceled before being dispatched to the
RESPONDING group.
Within a specific interrupt level, the order in which members will
- receive events is undefied. A BusMember may be registered
+ receive events is undefined. A BusMember may be registered
at a level that is +/- of one of the defined levels, as long as it
follows the constraint MONITORING <= interruptLevel <=
MAX_INTERRUPT.
@@ -180,7 +180,7 @@
The purpose of this encapsulation is to allow the clean separation of making a request, and servicing a request. Due to - various conditions in the application state, the actualy response + various conditions in the application state, the actually response to a request may change, as well as who services it. This design approach facilitates that.
@@ -198,7 +198,7 @@In order to keep the coupling amoung application modules to a +
In order to keep the coupling among application modules to a
minimum, a single point of reference is needed for coordination
and data sharing. The class Full "i18n" support should be assumed in modern applications,
and all user viewable strings should be defined in a configuration
- file. For Antidote this configuraiton file is
+ file. For Antidote this configuration file is
To aid in the lookup of text properties, as well as other
@@ -227,7 +227,7 @@
The organization of configuration properties is based on the
- fully qualifed path of the class that requires the property. For
+ fully qualified path of the class that requires the property. For
example, the "about" box contains a messages, so it looks for the
property " ... in fact it is the Ant GUI by the Apache Ant project itself, because,
- as you might know, there are several other grafical user interfaces covering Ant.
+ as you might know, there are several other graphical user interfaces covering Ant.
Most of them are integrated in IDEs such as NetBeans
or Eclipse. To be honest Antidote
- has started a long time ago (spring 2000) and was designed to become integratible into
+ has started a long time ago (spring 2000) and was designed to become integrable into
IDEs by it's original Author Simeon H. K. Fitch, who did the most work on Antidote.
Unfortunately the Antidote community never came really "to speed" and so the IDE-guys
where faster with their integrations.
@@ -25,13 +25,13 @@
interest in such a tool...
Anyways: The "sleeping beauty" Antidote has been awaken and is now being developed to
- a full featured, stand alone, JFC/Swing-based Ant GUI to grafically create, edit and run
+ a full featured, stand alone, JFC/Swing-based Ant GUI to graphically create, edit and run
build-files to be quite useful for the developer who do not use an IDE at all. So one of
the goals of Antidote development is to make it small, fast and really neat :)!
AppContext is the catch-all
class for containing the application state. Most modules and
@@ -214,9 +214,9 @@
antidote.properties, which is located (with other UI
- resources) in the subpackage "resources".
+ resources) in the sub-package "resources".
org.apache.tools.ant.gui.About.message" for the text
message it should display. Therefore, the ResourceManager
diff --git a/xdocs/projects/antidote/index.xml b/xdocs/projects/antidote/index.xml
index 839c12544..c471474f0 100644
--- a/xdocs/projects/antidote/index.xml
+++ b/xdocs/projects/antidote/index.xml
@@ -13,10 +13,10 @@
ANTidote is the GUI for Ant...
AntModule.contextualize() method has been called. Follow
the naming convention currently used in the properties file and
you should have to problems. This task should be done
- during development of your module. Under no cercumstances
+ during development of your module. Under no circumstances
should your module be submitted or committed without this task
being completed. Remember that Antidote has an international
audience.
diff --git a/xdocs/projects/index.xml b/xdocs/projects/index.xml
index 87396612a..abff7d027 100644
--- a/xdocs/projects/index.xml
+++ b/xdocs/projects/index.xml
@@ -16,7 +16,7 @@
Web-Page for Ant sub-projects. In the first step Antidote,
the Ant GUI, is included, but some others may follow!
- To make shure you do not miss anything: Stay tuned and visit this page from time to time :)! +
To make sure you do not miss anything: Stay tuned and visit this page from time to time :)!