W3C home > Mailing lists > Public > www-dom-ts@w3.org > February 2002

RE: Help wanted: A xslt transform for tests to HTML

From: Manos Batsis <m.batsis@bsnet.gr>
Date: Mon, 25 Feb 2002 12:40:28 +0200
Message-ID: <E657D8576967CF448D6AF22CB42DD26908BE59@ermhs.Athens.BrokerSystems.gr>
To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
Cc: <www-dom-ts@w3.org>


Ok, here's a sample file. Check it out and I will be expecting input to
take care of details. There are some issues with namespace output and
validity (null xmlns declarations, I think it has to do with my msxml4)
but I was in a hurry; got some deadlines over my head today. 

In case you need serious web based representation of the test files, I
could modify some transformations from an on-going project of mine (a
DOM-DHTML based XML Editor) that produces a grid interface like XML
Spy's. I will need a couple of days to do this. Note that I intent to
release that editor under the GPL(or something like that anyway), but I
think there won't be any problem if I 'donate' some modificated XSLTs to
the list. The grid interface works in both Moz and IE.

Manos

> -----Original Message-----
> From: Manos Batsis 
> Sent: Monday, February 25, 2002 10:56 AM
> To: Arnold, Curt
> Cc: www-dom-ts@w3.org
> Subject: RE: Help wanted: A xslt transform for tests to HTML
> 
> 
> 
> Just saw this, gimme 10 minutes and I'll get back to you with a
> transform.
> 
> > -----Original Message-----
> > From: Arnold, Curt [mailto:Curt.Arnold@hyprotech.com] 
> > Sent: Friday, February 22, 2002 10:22 PM
> > To: 'www-dom-ts@w3.org'
> > Subject: Help wanted: A xslt transform for tests to HTML
> > 
> > 
> > If anyone else would like to take it upon themselves to write 
> > a little XSLT
> > transform that would produce a reasonable HTML representation 
> > of a test
> > definition in the next day or two, it would be appreciated.  
> > Not anything
> > remotely as complex as test-to-java.xsl.
> > 
> > Quick requirements:
> > 
> > Output should be valid HTML
> > 
> > Should be compatible with styles already used for test matrix, etc.
> > 
> > Assertion elements should be addressable using a URL 
> > fragment, for example, 
> > 
> > <assertEquals id="nameEqual" actual="name" expected='"newname"'/>
> > 
> > Should be converted into something like:
> > 
> > <a id="nameEqual">&lt;assertEquals id="nameEqual"...&gt;</a>
> > 
> > Metadata links should have hyperlinks:
> > 
> > 		<subject
> > resource="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/l
> > evel-one-core#
> > ID-35CB04B5"/>
> > 
> > Should be converted to:
> > 
> > &lt;subject resource="<a href="http://...">http:...</a>"/&gt;
> > 
> > You'd probably want to lift the de-Xpointerizing logic from 
> > test-matrix.xsl
> > so that exception clause references point to the attribute or 
> > method and not
> > an Xpointer that would not be interpreted by current browsers.
> > 
> > I may try to write a simple test page harness this weekend 
> > and having this
> > transform would make it easy to link to the appropriate 
> > assertion failure in
> > the test definition and give me one less thing to do.
> > 
> > 
> 
> 


Received on Monday, 25 February 2002 05:37:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:04 UTC