Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 60935 invoked from network); 14 Nov 2000 02:06:19 -0000 Received: from w002.z208176150.sjc-ca.dsl.cnc.net (HELO mail.x180.com) (208.176.150.2) by locus.apache.org with SMTP; 14 Nov 2000 02:06:19 -0000 Received: from [129.144.124.187] ([127.0.0.1]) by mail.x180.com (Netscape Messaging Server 4.15) with ESMTP id G3ZS8C00.8P7 for ; Mon, 13 Nov 2000 18:00:12 -0800 User-Agent: Microsoft-Entourage/9.0.2509 Date: Mon, 13 Nov 2000 18:03:41 -0800 Subject: Re: Proposed Revolution: AntEater (a proposal for Ant Core 2.0) From: "James Duncan Davidson" To: Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On 11/13/00 5:38 PM, "Barrie Treloar" wrote: > What is wanted is for the xml file to be modified but to keep the same > structure as the user entered (whitespace included). As a heavy user of Dreamweaver which doesn't muck with existing HTML, I can understand the motivation behind that. However, are there other reasons? The need to have the user experience be seamless is important, but so is the need for a good data model that can be exported to tasks, scripts, guis, etc. There may be other ways of doing this than using DOM. Then again, maybe not. I'm going to reserve further comments until I hear more. > I think what you are proposing is more inline with a Java/XML binding, > which I believe is an easier way to manipulate the XML in a java > centric. That is compile XML into Java classes. > > You'll need to work out what is needed and how much of the original > XML needs to be kept when working on it. Obviously all of the original data represented by the XML has to be kept in some way. For example, comments have to be kept with their tasks/targets/elements whatever. -- James Duncan Davidson duncan@x180.com !try; do()