[
Lists Home |
Date Index |
Thread Index
]
Very much so. I edit most of my XML in PFE. Just old school.
But then I get something like X3D where the XML isn't a doing
a lot but those eversolarge strings of numbers are inscrutable.
Now I very much want WYSIWYG and dialogs plus a fast treeview.
Aggregates are where it becomes complicated. If my task is
to create an IETM which combines troubleshooting diagrams,
a real time 3D illustration for parts breakdowns, assemblies
and so forth, but table editing for parts lists, now I am
editing in multiple namespaces that when presented, must
interact seamlessly. So eventually, one is either working
with multiple tools, or has an editor with many facilities.
Some X3D editors (notably Vizx3D) are already polyglot
editors because they have to combine editing of multiple
kinds of X3D objects, eg, h-amin, geovrml, etc. where even
though the X3D is the same, the mental operations for
creating objects are rather different.
len
From: Elliotte Rusty Harold [mailto:elharo@metalab.unc.edu]
At 8:27 AM -0400 4/8/04, Mark Schmeets wrote:
>Well yes, maybe. I think it depends a lot on what *kind* of XML you
>are working with. Certainly when there is a lot more text than
>structure you want something closer to a text editor. When there is
>a lot more structure than text you want something closer to a form
>based editor. The fact that there is this range of application makes
>producing a good *general purpose* XML editor very difficult.
Yes, but I don't think most XML-specific tools go far enough. I'm a
man of extremes. I either want to edit my XML by hand in a text
editor (with maybe a little help from syntax coloring and tag
completion, though I won't miss it if it isn't there; and I certainly
wouldn't accept poor performance in order to have these features.) or
I want an application specific editor such as Word or Adobe
Illustrator that completely shields me from the native XML. I
encounter little need for anything in between these two positions.
|