Jan,
At 02:41 PM 6/30/2005, you wrote:
So you'd use oop to create a XmlSchemaDocument and lots of other
classes (like SchemaElement, SchemaElementCollection and so forth) to
get there (if you had to implement an intellisensing xml editor of
sorts)?
If I had to implement an intellisensing XML editor of sorts (if I couldn't
find what I needed off the shelf) ... I'd go head hunting. I'm not
qualified for the job (but I know people who are).
OOP is fine, and so far as I know it's still the state of the art for
developing applications with as much user interactivity as an editor. XSLT
was never designed for that kind of thing -- the fact that we think about
it at all is, I think, a testament to its power and versatility.
Sorry not to be more help --
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--