W3C home > Mailing lists > Public > www-svg@w3.org > December 2007

Fwd: Re: Feedback on getEnclosureList and getIntersectionList DOM methods

From: Erik Dahlström <ed@opera.com>
Date: Mon, 17 Dec 2007 20:10:27 +0100
To: "David H Elrod" <dhelrod@rivendell.com>
Cc: "www-svg@w3.org" <www-svg@w3.org>
Message-ID: <op.t3ht7phqgqiacl@gnorps.palace.opera.no>


Thanks for the feedback (now forwarded to www-svg).


------- Forwarded message -------
From: "David H Elrod" <dhelrod@rivendell.com>
To: "Erik Dahlström" <ed@opera.com>
Subject: Re: Feedback on getEnclosureList and getIntersectionList DOM  
Date: Mon, 17 Dec 2007 17:10:38 +0100


You are welcome to CC/Forward my reply, if you like, I can send it again
to you and the rest of the list.


Erik Dahlström wrote:
> Hi David,
> Do you mind if I CC the www-svg list with your reply?
> SVG 1.1 supports MutationEvents which lets you monitor the tree for  
> changes, though that doesn't cover the cases where the tree changes but  
> no change occurs in the intersectionlist.
> Note that the re-evaluation can be costly, which is another reason to  
> keep the list static.
> /Erik
> On Mon, 17 Dec 2007 16:10:20 +0100, David H Elrod  
> <dhelrod@rivendell.com> wrote:
>> Erik,
>> I'm new to SVG, but have done graphics development off and on for more
>> than 30 years.
>> In my experience, dynamic data structures need a notification method so  
>> users
>> can be aware they changed OR the list should be static.
>> It is nice, even with static data structures, to be able to register  
>> for change
>> notification, or to be able to poll for some incrementing 'version'  
>> number so
>> that users of the data structure can discover that the it is no longer  
>> accurate.
>> Reviewing the suggested correction, it makes sense to me to make this  
>> change.
>> David
>> Erik Dahlstrom wrote:
>>> Hello www-svg!
>>> The SVG WG is looking for feedback on changing the SVG 1.1 DOM methods  
>>> 'getIntersectionList' and 'getEnclosureList' to return static  
>>> NodeLists [1].
>>> The current situation is that only one implementation supports these  
>>> methods, and that the returned values are static. This means that if  
>>> the elements change in the tree the list is not re-evaluated  
>>> automatically, the method just returns the list of elements that were  
>>> intersected at the time the method was called. Should an updated list  
>>> be needed the method can be called again.
>>> The expectation is that with the change from live NodeLists to static  
>>> NodeLists there will be more implementations that support these  
>>> methods.
>>> Cheers
>>> /Erik, on behalf of the SVG WG (ACTION-1738)
>>> [1]  
>>> http://www.w3.org/2003/01/REC-SVG11-20030114-errata#liveness-getintersectionlist-getenclosurelist

Erik Dahlstrom, Core Technology Developer, Opera Software
Received on Monday, 17 December 2007 19:12:59 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:12 UTC