Lists Home |
Date Index |
- From: email@example.com (Peter Wilson)
- To: firstname.lastname@example.org
- Date: Fri, 07 May 1999 07:49:26 -0700
Some time ago I wrote a structured editor where I parsed java source and
allowed the user to edit an action diagram. The editor looked after the
nesting of compound statements/methods etc. I allowed the user to free
type method calls, assignments and conditions. The problem was that I
could not reliably re-parse the source if it contained syntax errors. A
single } could unhinge the whole scheme.
The answer was to use XML to delimit the gross structure of the program
source and to let the user type whatever they wanted - but not structure
tags. Program source can then be reliably re-parsed.
I am still working towards this goal but have become stuck in the
XML/DOM tar pit.
I have been working on the idea of compiled XML but came to the
realization that the internal structure was not very different from DOM.
However, when making the conversion I discover that DOM has been
designed with desktop bloatware in mind. The NodeList requirement is
one of the worst.
The compile function idea still works. You get a binary representation
of a DOM tree. This occupies half the size of the original XML and
requires no parsing to re-load. The original XML is still recoverable.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)