Erik, Thank you for your email.
As I mentioned, comments were "currently ignored", meaning it would be a future feature. This feature was not of important as importing the actual executable ant xml elements obviously. For the record, xml comments are now imported - SAX's LexicalHandler was utilised for this - and the gui updated to provide editing of the comment text. A new release will be uploaded soon. The XML layout has been on my mind since day one. I wondered whether people would prefer empty lines between <target>'s, and whateher attributes shuld be all on a single line, or listed one per line (current implementation - better for viewing /printing the file I might add). To this effect, I will be implementing a dialog for modifying the xml layout as to a user's preference. I heard about antidote only after I had finished much of the v1.0 developement on antacid back in May. Neither I or any of my peers had ever seen or used antidote. Since noone was aware of any GUI tool to simplify the use of ant, and given my (then) current boredom, a peer suggested that I develop one... :) I don't know what features antidote has. I've never used it. AntAcid has features that I am seeking from my own experience of using ant buildfiles in large projects. In my experience, for any software to be easily used, tested and evaluated, it should have a release package that is easily downloaded via http. (I only setup CVS at home for sourceforge utilisation last week). I am always open to critism, and RFE's. So fire them off :) Regards, T Master On Sun, 23 Jun 2002 07:56:48 Erik Hatcher wrote: > This is the depressing part from your feature list: > > N.B: Comments are currently ignored, and will not be imported. > > One of the things I *despise* about GUI's that work on build.xml files is > that they mangle the aesthetics. Eventually they'll improve just like > IDE's > that do automatic Java formatting, but having a tool nuke my very > valuable > comments means its a tool I would not use or recommend. > > I know its a hard problem to solve though. > > Also, I don't want a tool automatically laying out the XML - I like my > attributes lined up and in a specific order. How does is this handled? > > But, not to discourage you - I'm all for these types of tools. Keep up > the > good work. But, why did you not work on Antidote instead? What does > your > tool do that Antidote does not? > > Erik > > > ----- Original Message ----- > From: "Ultra Funkular" <[EMAIL PROTECTED]> > To: "Ant Users List" <[EMAIL PROTECTED]> > Sent: Sunday, June 23, 2002 5:07 AM > Subject: Re: Antidote > > > > I've actually made a front-end myself. Something i quickly put > together. > > It's http://antacid.sourceforge.net > > > > One more kink to work out on it, but it is usable. > > Check it out. > > > > > > T Master. > > > > > > On Sun, 23 Jun 2002 02:45:38 Conor MacNeill wrote: > > > Brian Ivey wrote: > > >> Is the gui front-end for Ant, called Antidote, a dead project? I've > > >> unable > > >> to find any current documentation (most of it's about a year old). > > > > > > I'd say it's on the operating table at the moment but it appears > someone > > > is about to apply 20kV to try and revive it. Let's see how that goes. > If > > > you want to join in, even if it's just to provide requirements from a > > > user view, it would be best to join that discussion on ant-dev. > > > > > > Conor > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
