On Oct 5, 9:02 pm, Peter Flynn <peter.n...@m.silmaril.ie> wrote:
> I think it is...a user is file-centered, and expects to open a file and
> then do something to it. Asking them to open the action first, and the
> file afterwards, is counter-intuitive.

I think I understand where you're coming from, the idea however was
that when you select the New -> XML Parser option, you wouldn't
really
specify an action, instead, I wanted people to see it as creating a
new 'project' which they can configure to their liking.

> When I open a new XML Parser (I think I am beginning to understand you
> now: you mean a new instance of a parser), it asks me to specify the
> input documents using a filter or a URI. Again, there is no File | Open
> action. I eventually managed to get it to validate the XML documents in
> a directory, but I'm not clear what advantage this program offers over
>
> $ for f in *.xml; onsgmls -wxml $f; done

I hope the advantages could be:
[1] Configure the same as above using a User Interface,
[2] The configuration can be saved and reused,
[3] Potentially allows to specify more options,
[4] Works with any JAXP 1.3 Processor,
[5] Added functionality like XML catalog support.
[6] Previously created configurations can be run from the
    command-line as well.

> I couldn't get the radiobutton for SAX to work,

I don't understand how the radio-button could not work?

Could it maybe look like it does not work because you expect
different options to appear?

SAX and DOM provide the same basic set of options, it however uses
a SAX or DOM Parser in the background when 'running' the 'project'.
(note: it is possible using the 'project properties', to specify more
specific DOM and SAX options as well)

> and there is no explicit option for "validate according to external
> DTD", although it clearly did the work correctly on the file group
> I specified.

Thanks for pointing this out ... 'Internal' was meant to represent:
the DTD specified by the DOCTYPE declaration in the XML document.
However I had forgotten about the meaning in the XML spec of
'internal' and 'external' DTD subsets, which makes my use of the
word very confusing.

I will change this.

> I think this is a very good tool for a certain class of developer. I'm
> just probably not in the target beam for it.

I hope people will find it handy.

Thanks,
Edwin
--
http://www.edankert.com/