Edwin Dankert wrote:
> Thank you very much for the comment.
> 
> An XML Hammer project can be either of the 5 types of projects
> (XML Parser, XPath Search, XSL Transform, Schema Validator or
> Stylesheet Validator) which can be created using either the
> file -> new menu-option or the toolbar button.

It wasn't obvious to me how I would check a file for well-formedness or 
validity, when there is no File | Open action. I think I may have 
misunderstood what this tool is for.

> Do you think it is confusing to use a generic name for these
> projects?

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.

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 couldn't get the radiobutton for SAX to work, 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.

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.

///Peter