W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2003

RE: iterator implemented in DOMConfiguration

From: Sander Bos <sander@x-hive.com>
Date: Tue, 12 Aug 2003 09:25:10 +0200
Message-ID: <41D11F414A26E942912B7E7696DC8E22848264@JAKARTA.xhive.archipel>
To: "W3-DOM" <www-dom@w3.org>

> Would an iterator make sense in the DOMConfiguration?  That would
> allow the properties to be discovered dynamically, instead of
> hardwiring strings like "canonical-form" in applications.  Or perhaps
> a getNextProperty()?

+1 for getting a list of property names, instead of a getNextProperty or
Iterator I guess the DOM way would be something like
	DOMStringList getPropertyNames();

In our application the use case is that we have a graphical tool that on
loading/ saving XML files shows all the DOM Load/ Save properties with
checkboxes, everything about that form is dynamic apart from determining
the list of properties. Once you have a property name you can determine
whether it's a boolean property, default value and what is supported

Kind regards,

Received on Tuesday, 12 August 2003 03:25:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:11 UTC