Dear Florent, At 05:08 PM 9/26/2008, you wrote:
How about an XPath option that would work the same way? Currently I usually write myself a little Schematron to locate particular nodes, which isn't a big deal. But it would be nice not to have to when the search can be expressed simply in a one-line XPath.
Sounds like a great idea! If I can give my $0.02, I think it could even be generalized by providing an XQuery sandbox along with a few variables, functions or collections:
collection('prj:my-project?pattern=*.xsd') // xs:complexType/@name/data(.)
collection('file:///home/me/xslt?pattern=*.xsd') // xsl:template/@name[resolve-QName(., ..)[ namespace-uri-from-QName(.) eq 'http://my.ns' ]] / document-uri(.)
Augmented with a dialog box to set up the default collection by using a directory selection dialog box, project dropdown list and various options, as well as a saved history, I think that would be a powerful general purpose tool (while well integrated into oXygen yet.)
It would, and yes, I thought of something like this too, although it might not have been as fully worked out in my mind. :-) But I decided to ask just for XPath -- if only because that would make for a simple, one-line interface available from the context menu in the Project View. Not that the two features are incompatible, of course. Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.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 ======================================================================