Coins uses an XML Bindings file to define the mapping. I just completed the
documentation for Bindings, including examples (if not the entire web page):
http://www.jxml.com/coins/index.html
>Here are some general points which I think we need to address now.
>
> - how do we map elements onto classes. Property file? Regexps in PIs?
>Stylesheets? or a mixture
or XML? I would argue that the mapping should be separate, except when
doing object serialization
> - what are the *non-graphics* methods for an element , e.g.:
> doneParse()/processXML()
> isValid() [i.e. non-XML validation - type, values, etc.]
The SAX interface, DocumentHandler, works rather well for much of this.
> write() - recreate XML or other formats
If a document carries a reference to its source, and that source is
writable,
then UPDATE is vital--I explored this in coins v0.
> - what are the graphics methods
> onClick(count)
> redraw()/resize() etc.
I've been looking at graphical elements of late and this looks unnecessary.
Just use wrapper elements. But the key here is to support references between
the wrapped gui objects.
>Rather than try to list more I'd like to see coordinated discussion a la
>SAX. In that case David Megginson offered to take XML-DEVers through a
>series of questions which he then collated and re-offered. The initial pass
>took only a calendar month (including year-end). But he worked VERY hard.
>
>Can we have volunteers for this? It's one of the most critical aspects of
>XML at present that is not covered by other WG programs (if this is covered
>by DOM 2.0 can we wait for this? An XML-DEV API could be a valuable
>creation anyway).
I would be delighted to participate, though I should likely not be the one
to
chair this.
Bill