[
Lists Home |
Date Index |
Thread Index
]
Yes.
As well as turning off validation. XML isn't the issue;
it is the domain of the information and the production
process. If an aggregate document type (what the IETMs
tend to be) is being edited, I may need several editors
or plugins, or one polyglot editor. XML doesn't force one into a
text editor; it always preserves that option, and sometimes,
it is the most productive one.
IME, I prefer text editors only because I get to define most
of my language world. In cases such as X3D, however,
it is very hard to do anything complex or compelling with
a text editor although I've seen it done on occasion.
This debate comes down to the application language,
the production pipeline, and the experience of the
author. XML Doesn't Care.
len
From: Bob Foster [mailto:bob@objfac.com]
Len, if I understood him correctly, suggested that an ideal
editor would be multi-modal, allowing visualization in all the
application-specific domains a document traverses.
|
