On Feb 20, 4:10 am, "Dan Webb" <[EMAIL PROTECTED]> wrote:
> The thing is is that there's loads of cross browser problems with
> setting attributes (as mentioned previously) and working around at
> least the common problems with a tool like this is essential otherwise
> your just going to end up
If you bleeding-edgers do an SVN update you'll notice that there's a
new selectors branch. The version of selector.js contained therein is
another major advancement from the previous version (attached to patch
#7658). Christophe's excellent code reviews and revisions have been
indispensible; now
Long live duck typing[1]!
If it has an each, it can probably enumerate. :)
Best,
Thomas
[1] http://en.wikipedia.org/wiki/Duck_typing
Am 20.02.2007 um 13:16 schrieb Christophe Porteneuve:
>
> Hey Mislav,
>
> Mislav Marohnić a écrit :
>> I would like to see a isEnumerable, but this can be a
Hey Dan,
Dan Webb a écrit :
> How would you implement this optionally?
A basic way:
each: function(iterator, useBreak) {
var index = 0;
if (!useBreak)
this._each(function(value) {
iterator(value, index++);
});
else
try {
this._each(functio
On 2/20/07, Christophe Porteneuve <[EMAIL PROTECTED]> wrote:
>
>
> > obj.each == Enumerable.each
>
> Hmmm, yeah, but is that really enough?
Yup.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" grou
> Well, we don't have $continue anymore, so no point in discussing that bit.
>
Ah yes, just noticed that. Good work!
About $break... I'm not sure whether this feature is good or just a
> performance/debugging hog, but I'm definitely sure I almost never use it
> myself (same in Ruby). When I ite
On 2/20/07, Dan Webb <[EMAIL PROTECTED]> wrote:
>
>
> I think it's really important to do something about this because as it
> stands Prototype overwrites JS 1.6 methods with incompatible versions. As
> more browser support these methods and more scripts depend on them its going
> to be a problem.
Hey Mislav,
Mislav Marohnić a écrit :
> I would like to see a isEnumerable, but this can be a problem: what
> should we test for? Enumerability, so far, is obtained through "mixing
> in" methods.
>
> obj.each == Enumerable.each
Hmmm, yeah, but is that really enough?
--
Christophe
On 2/19/07, Christophe Porteneuve <[EMAIL PROTECTED]> wrote:
>
>
> I would like to see a isEnumerable, but this can be a problem: what
> should we test for? Enumerability, so far, is obtained through "mixing
> in" methods.
obj.each == Enumerable.each
--~--~-~--~~~---
Hello,
Just thought I would try to start a discussion around this ticket (not
the exact solution, more just the comments on it):
http://dev.rubyonrails.org/ticket/6650
as, looking back through the list, theres been no discussion here so
far (although theres been a fair bit in the comments on th
>
> > Just casting my vote for the solution Martin proposed. Simple and to
> > the point.
>
Sorry for joining this discussion really late but after fielding all
the bug reports for DOMBuilder (and using it heavily myself) it has to
be said that this solution definitely isn't going to cut it. I
11 matches
Mail list logo
