> Maybe the first step is to update the TODO list :-)Okay, a revised list is attached at the end of this message. Here's
the discussion:
> * Cleanup build.xml file; make antidote specific.Removed.
>
> This has been done already, right?I think so!
Removed.> * Rewrite ACSFactory to use it's own parser rather than
> the implementation
> specific com.sun.xml.tree.SimpleElementFactory class
> (only available
> in JAXP from Sun).
>
> Done? Still TODO?Has to be rececked, but generally it works fin IMHO
> * Add editors for defining file sets, and other "sets".I think you mean "partially"? Okay, modified TODO item.
>
> This has been done already, right?Particualry! IMHO there could be mor comfort in defining filesets, what
do you think!?!
> * Write wizzard framework.Modified TODO item.
>
> The framework is there, but there are currently no
> wizards, right?There is a "not working" example wizard for an entire build-file. IMO
the wizarg could be used to create targets in addition...
> * Implement a build progress reporter.Modified TODO item.
>
> What would that look like, compared to the console that
> currently exists?I thinks the console is ok, but Sim meant to write a log to a file in
addition. Obviously the log line formtting has to be definable
interactively and stored in preferences...
> * Implement a "Worker Thread" pattern that allows workers to haveModified TODO item.
> their work done in a thread property registered with
> Antidote, and
> provide support to that worker to provide progress updates via
> the GUI. Should also provide support for hour-glass cursor
> handling, and AWT event blocking until task is completed. This
> would be used for things such as loading files or other tasks
> that the user must wait for completion.
>
> Has this been done or is it still TODO? I think it is still TODO.It IS a to do! There is no way to stop Ant once it runs from Antidote!
Modified TODO item.
> * Add menu option to select the compiler to use, which then sets
> the "build.compiler" property. Better yet, create a generic menu
> building capability that allows the setting of a property from a
> list of options.
>
> Still TODO, right?It is a todo! I'd propose not just setting the complier, put the option
to set all Ant -D parameters from the gui and make them storable!
> * Add ability to put an "all" or "don't care" specifyerLeft this the same, since I don't really understand it :-)
> on the action
> "enableOn" and "disableOn" properties.
>
> Still TODO, right?It is not implemented IIRC! Additionally I am not really shure what it
should do...
> * Add ability to view task dependencies more fully.Modified TODO item.
>
> Describe this facility?It should say "target-dependency". It would be nice to be able to show a
grafic with all the tragets and arrows between them to show the
dependency (depends). Would be really a feature for many guys using Ant,
I know...
> * Add better editors for specific tasks.Modified TODO item.
>
> Examples?Not only for tasks, but properties in addition. We meant editors just
like the dependency choose!
> * Add a Progress Monitor for file loading (especially forLeft the same.
> slow boxen like
> mine) .
>
> Still TODO, right?Yes, it is! Progress for loading files and for the time the
introspection rus would be nice!
> * Implement some for of refid hyperlinking functionality.Left the same.
>
> Describe this facility?Not shure what Sim means... Yould someone else drop in here...!?!
> * Implement context sensitive menus for the consoleModified TODO item.
> window, allowing
> an error to be selected and invoked in IDE.
>
> "Jump-to" in Antidote itself?I think integration into IDEs is no BIG project aim anymore or at leas
ATM...
> * Write preferences framwork, including persistence support.It seems the nucleus of this is already there. e.g., in core/ProjectManager.java?
>
> Trivial, still TODO? I can borrow this from my own open
> source code.Would be nice, if the code is under an Apache compatible OSS License
(like Apache or FreeBSD) LGPL is NOT ok!!
I'd prefer a small, fast an clean implementation as always ;-).
Or should this be re-written? Like I said, I've got one of these things already
written in my "SoftWoehr Class Libraries" that I could modify and "Apachify".
> * Provide some sort of class path debugging support.Modified TODO item.
>
> Describe this facility?Not 100% shure, but displaying the Ant-build-classpath and introspect
the jars one by one... Search for Classes and multiple occurrences in
the classpath... And so on!
> * Add "syntax" colorization to the console window {done},Modified TODO item.
> with a preferences editor for setting up the styles {not-done}.
>
> Describe this facility?Just make the syntax highlighting in the console window configurable via
the Preferences window! Easy!
> * Figure out an approach to gracefully stopping a running build.Modified TODO item.
>
> Hmmm ... screech! crash! :-)As I said before... Uneasy to implement without hooks in Ant
itself...;-)
> * Add error handler for SAX parser to better reportLeft the same.
> loading errors.
>
> Still TODO?Yupp! Not done!
> * Project properties viewer, including the ability to viewModified TODO item.
> dependencies (local and cascading).
>
> Describe this facility?As said before: View and modify the Projekt Properties you can override
using -D with the Ant-Commandline! Cascading means from imported
build.xmls
> * Acquire or implement a logging facility.Modified TODO item.
>
> What, are we thinking JLog here?I'd prefer Log4J. Logkit would be another option... Or the jakarta
commons logging facility...
When you delete a target, the editor in which you were editing the
> * Eat more dog food.
>
> I'm using it! It's not easy to use yet, the editors are
> not much fun to use compared to merely typing things in
> NetBeans source editor!Yes: The editors have to be improved definately!
> Also, I'd add this usability feature:
>
> * When you are editing some task or property or target and
> you decide to delete that thing, the editor should disappear.Could you explain..
target "hangs around" in the editor window. The editor itself should
go away so that you don't think you are editing a target anymore,
because you are not doing so!
P.S.: Sorry for answering that late but ATM I am just online everyLikewise! See attached modified TODO.
second day!
-- Jack J. Woehr # You measure democracy by the freedom it Senior Consultant # gives its dissidents, not the freedom Purematrix, Inc. # it gives its assimilated conformists. www.purematrix.com # - Abbie Hoffman
TODO List:
* Improve editors for defining file sets, and other "sets".
* Begin to use wizard framework to develop useful wizards, such
as target creation.
* Implement a build progress reporter beyond the console
itself to write a log to a file in addition. Obviously
the log line formtting has to be definable interactively
and stored in preferences.
* Implement a "Worker Thread" pattern that allows workers to have
their work done in a thread property registered with Antidote, and
provide support to that worker to provide progress updates via
the GUI. Should also provide support for hour-glass cursor
handling, and AWT event blocking until task is completed. This
would be used for things such as loading files or other tasks
that the user must wait for completion. Currently there is no
way to stop Ant once it runs from Antidote!
* Add menu option to select the compiler to use, which then sets
the "build.compiler" property. Better yet, create a generic menu
building capability that allows the setting of a property from a
list of options, not just setting the complier, but allowing
the option to set all Ant -D parameters from the gui and make
them storable.
* Add ability to put an "all" or "don't care" specifyer on the action
"enableOn" and "disableOn" properties.
* Add ability to view task dependencies more fully. It would be
nice to be able to show a graphic with all the targets and
arrows between them to show the dependencies.
* Add better editors for specific tasks. Not only for tasks, but
properties in addition. We mean editors just like the dependency
chooser.
* Add a Progress Monitor for file loading (especially for slow boxen like
mine) .
* Implement some for of refid hyperlinking functionality.
DOWNGRADED: We think integration into IDEs is no BIG project aim
anymore or at least at the moment.
* Implement context sensitive menus for the console window, allowing
an error to be selected and invoked in IDE.
* Write preferences framwork, including persistence support.
* Provide some sort of class path debugging support, e.g.,
displaying the Ant-build-classpath and introspect the jars one
by one ... search for Classes and multiple occurrences in the
classpath ... and so on.
* Add "syntax" colorization to the console window {done},
with a preferences editor for setting up the styles {not-done},
to make the syntax highlighting in the console window
configurable via the Preferences window and persistent via
properties.
* Figure out an approach to gracefully stopping a running build.
"Uneasy to implement without hooks in Ant itself." - (Christoph
Wilhelms)
* Add error handler for SAX parser to better report loading errors.
* Project properties viewer, including the ability to view
dependencies (local and cascading). View and modify the project
properties you can override using -D with the Ant commandline
"Cascading" means from imported build.xml's.
* Acquire or implement a logging facility. C. Wilhelms would
prefer Log4J. Logkit would be another option, or the jakarta
common logging facility.
* Eat more dog food. E.g, When you delete a target, the editor in
which you were editing the target "hangs around" in the editor
window. The editor itself should go away so that you don't think you
are editing a target anymore, because you are not doing so!
(pending Ant 2.0)
* Need Ant API access to:
- Tasks within a Target
- The topo sorted task list to get flattened dependencies
- The build setup code to recduce code replication.
- Normalize the Ant data model to represent a more consistent
tree structure, and more bean-like API.
* Better define the data model architecture, and how it interfaces
with the Ant data model.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
