W3C home > Mailing lists > Public > www-dom-ts@w3.org > August 2001

RE: Wish list

From: Freek de Bruijn <freek@x-hive.com>
Date: Tue, 21 Aug 2001 09:44:56 +0200
To: "'Curt Arnold'" <carnold@houston.rr.com>, <www-dom-ts@w3.org>
Message-ID: <41D11F414A26E942912B7E7696DC8E2201FA01@JAKARTA.xhive.archipel>
The javadoc target for build.xml could look something like this:

<target name="run-javadoc" depends="init">
        <mkdir dir="${build.dir}/javadoc"/>
        <javadoc packagenames="org.w3c.domts.*"
                 sourcepath="java;java/junit;${java.build.dir}"
                 destdir="${build.dir}/javadoc"
                 author="true"
                 version="true"
                 use="true"
                 windowtitle="DOM Test Suite"
                 bottom="Copyright &#169; 2001 World Wide Web Consortium.
All Rights Reserved.">
                <group title="Test Suite Framework"
packages="org.w3c.domts"/>
                <group title="DOM Level 1 Core"
packages="org.w3c.domts.level1.core"/>
                <group title="DOM Level 2 Core"
packages="org.w3c.domts.level2.core"/>
                <!-- Other groups can be added... -->
        </javadoc>
</target>

---
Freek


-----Original Message-----
From: www-dom-ts-request@w3.org [mailto:www-dom-ts-request@w3.org]On Behalf
Of Curt Arnold
Sent: Tuesday 21 August 2001 8:04
To: www-dom-ts@w3.org
Subject: Wish list


There are a couple of small things that could help out.  If anyone wants to
take a shot of these, I would appreciate it.

1. A Javascript routine that creates a duplicate of a document.  Should work
with both Netscape/Mozilla 6 and MSXML 2+.

2. JavaDoc targets in build.xml for the generated tests and the support
classes.  Suggestions on changes to generated documentation comments in
tests.  Occassional reminders that I need to add more extensive comments to
adapter classes and abstract classes.

3. Either an example of how to kludge synchronous XML parsing in Netscape
(sleeping until the load event if dispatched or some other type of stall) or
a pretty definitive statement that it can't be done right now.

Using asychronous parsing for each load() statement would probably prevent
compatibility with JsUnit since it would expect the test to be over when
control is returned from runTest.  However, if the implementation of load
performs a clone of a previous (asychronously) loaded document (See 1
above), then end of the test and the return to the caller would be
coincidental.
Received on Tuesday, 21 August 2001 03:45:34 UTC

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