Re: ACTION-87: Selectors API

2006-06-05 Thread Anne van Kesteren
On Wed, 31 May 2006 02:56:46 +0200, Jonas Sicking [EMAIL PROTECTED] wrote: What we could maybe do though is to return a real ECMAScript array. I actually like this idea a lot since that'll integrate much better with scripts than a StaticNodeList would. That makes a lot of sense. I support

Re: ACTION-87: Selectors API

2006-06-05 Thread Jonas Sicking
Anne van Kesteren wrote: On Wed, 31 May 2006 00:11:23 +0200, Jonas Sicking [EMAIL PROTECTED] wrote: I'm not in love with having match in the name, but I could live with matchAll() and matchOne(). I like these names. Having short names is nice and all, but having clear ones is even better.

Re: ACTION-87: Selectors API

2006-05-30 Thread Jonas Sicking
liorean wrote: On 13/05/06, Anne van Kesteren [EMAIL PROTECTED] wrote: On Sat, 13 May 2006 21:08:26 +0200, liorean [EMAIL PROTECTED] wrote: And StaticNodeList looks to me to be pretty array-like. Well, if StaticNodeList looks that way NodeList would look that way too and I'd therefore

Re: ACTION-87: Selectors API

2006-05-30 Thread Ian Hickson
On Tue, 30 May 2006, Jonas Sicking wrote: - Third, NodeLists being live means you cannot manually manipulate them. StaticNodeLists don't have this problem. Since they are not live, manipulation of them should not be a problem. This means array functionality such as sort, push, pop

Re: ACTION-87: Selectors API

2006-05-30 Thread Robin Berjon
On May 30, 2006, at 15:55, Ian Hickson wrote: On Tue, 30 May 2006, Jonas Sicking wrote: What we could maybe do though is to return a real ECMAScript array. I actually like this idea a lot since that'll integrate much better with scripts than a StaticNodeList would. That makes a lot of

Re: ACTION-87: Selectors API

2006-05-30 Thread Jonas Sicking
Robin Berjon wrote: On May 30, 2006, at 15:55, Ian Hickson wrote: On Tue, 30 May 2006, Jonas Sicking wrote: What we could maybe do though is to return a real ECMAScript array. I actually like this idea a lot since that'll integrate much better with scripts than a StaticNodeList would. That

Re: ACTION-87: Selectors API

2006-05-18 Thread Anne van Kesteren
On Wed, 17 May 2006 15:35:24 +0200, Jim Ley [EMAIL PROTECTED] wrote: The shortest name should represent the most efficient method imho. Crazy notion, names should be clear, not short for efficiency. The point was that if the more efficient one of the two actually had a longer name,

Re: ACTION-87: Selectors API

2006-05-17 Thread Anne van Kesteren
On Wed, 17 May 2006 06:29:54 +0200, liorean [EMAIL PROTECTED] wrote: * Several people have raised issues with naming the methods match and matchAll as those might suggest a boolean return value. Alternate suggestions have been select and selectAll. For ECMAScript, I think match is a

Re: ACTION-87: Selectors API

2006-05-17 Thread Anne van Kesteren
On Wed, 17 May 2006 15:19:46 +0200, Lachlan Hunt [EMAIL PROTECTED] wrote: I like match() too because it's much shorter than getElementsBySelector(), Right... :-) but I think the fact that it only returns a single node is confusing and that, in most cases, authors would want the whole

Re: ACTION-87: Selectors API

2006-05-15 Thread Anne van Kesteren
On Mon, 15 May 2006 01:22:21 +0200, liorean [EMAIL PROTECTED] wrote: I just have a look at the XPathNSResolver interface. In the Selectors spec, the selector elm is equivalent to *|elm in the case of a missing default namespace, but ns|elm where ns is the default namespace if a default

Re: ACTION-87: Selectors API

2006-05-14 Thread Anne van Kesteren
On Wed, 22 Mar 2006 15:45:21 +0100, Jim Ley [EMAIL PROTECTED] wrote: Fair enough, here are the requirements for the name: * short * simple Why are these requirements for the name, no other DOM names are short and simple, they're clear and unambiguous, I'd say they were the requirements.

Re: ACTION-87: Selectors API

2006-05-13 Thread Anne van Kesteren
On Sat, 13 May 2006 05:49:45 +0200, liorean [EMAIL PROTECTED] wrote: I've written some commentary on the Selectors API draft on WebGraphics. uri:http://web-graphics.com/2006/05/12/javascript-and-selectors/ 1. I'm aware how selectors work in browsers and that that's different from how

Re: ACTION-87: Selectors API

2006-05-13 Thread Anne van Kesteren
On Sat, 13 May 2006 21:08:26 +0200, liorean [EMAIL PROTECTED] wrote: I do think you're unnecessarily limiting the use of the Selectors API in the current draft by only allowing selector matching on the subtree of the document node though. The same way you might want to use getElementsByTagName

Re: ACTION-87: Selectors API

2006-05-13 Thread liorean
On 13/05/06, Anne van Kesteren [EMAIL PROTECTED] wrote: On Sat, 13 May 2006 21:08:26 +0200, liorean [EMAIL PROTECTED] wrote: And StaticNodeList looks to me to be pretty array-like. Well, if StaticNodeList looks that way NodeList would look that way too and I'd therefore suggest raising that

Re: ACTION-87: Selectors API

2006-05-12 Thread liorean
I've written some commentary on the Selectors API draft on WebGraphics. uri:http://web-graphics.com/2006/05/12/javascript-and-selectors/ -- David liorean Andersson uri:http://liorean.web-graphics.com/