Thank you. I was once thinking about doing something similar.
But then I realize that keeping another set of documentation is likely
to have it not-synced with the rapidly changing core manual.

Moreover, as a beginner, I find that the existing core manual has
inadequate information and examples to follow, ambiguous and
incomplete in some areas, and inconsistent for both content and
layout.

So I propose that the core documentation to be rebuilt from scratch,
probably in XML, so that different views of the manual (normal view
as well as quickref and index) could be generated in a unified manner
(thru XSLT and CSS.), for both core docs and third-party docs.
The information in the XML may also be useful for some Ant build file
editor. An online (or offline) searchable manual is also a very good
helper. There should be a repository of the documentation of all commonly
used tasks, including core and third party tasks.

May be there should be an Ant-doc subproject?

I sincerely hope that there will be a more complete, well written Ant
documentation which could benefit to all of us, both experienced or
beginners.

Kenneth


----- Original Message -----
From: "O'brien, Tim" <[EMAIL PROTECTED]>
To: "'Ant Users List'" <[EMAIL PROTECTED]>
Sent: Saturday, January 04, 2003 2:15 AM
Subject: Ant Core Task Quick Reference


I compiled a simple Ant quick reference from the existing Ant documentation.
I kept on forgetting attribute names, etc...

http://www.discursive.com/articles/2003/01/ant_core_ref.html

There are probably typos, and problems.  If anyone has any suggestions
please send them my way.  I figure that one could probably trim this down to
4 pages by removing some of the less-used tasks and consolidating some of
the repeated task examples.

It would be interesting for someone to do a frequeny analysis of Ant tasks.
Which tasks get used the most, etc?

Since the work is a copy of existing doc I gave credit to all Ant doc
writers at the end.




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to