[Prototype-core] Re: ie try to load 'http://:/' right after prototype 1.6.x loaded

2008-04-10 Thread DK
Why not use about:blank url? On Apr 9, 2:12 pm, John-David Dalton [EMAIL PROTECTED] wrote: This was originally used to allow this method to not have to pull down a real file and to avoid https issues in IE. This ticket:http://dev.rubyonrails.org/ticket/9394 Patches it to use a different

[Prototype-core] Re: Can the Enumarable iterators be changed to accept scope as the first param (optionally)

2008-02-10 Thread DK
Enumerable.addMethod(myFunction) that takes care of all the classes that implement or extend it. Hmmm. We have Class#addMethods() already which makes exactly what you're talking about. Everything would be as simple as calling: Enumerable.addMethods(my_hash_of_methods); if Enumerable was

[Prototype-core] Starting noconflict support - putting $() into a namespace [reposted from Spinoffs group]

2008-02-03 Thread DK
Changing topic :-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL

[Prototype-core] Re: Hide / show bug

2007-11-25 Thread DK
On Nov 23, 4:18 pm, Mislav Marohnić [EMAIL PROTECTED] wrote: [...] If CSS is hiding it, you must show it by explicitly setting style.display to block. 'block' if it should be a block, 'inline' if it should be an inline element, bixy, You better not think about other choices and listen

[Prototype-core] tests fail in trunk head revision?

2007-08-08 Thread dk
of the trunk expected to have all tests succeed. -dk --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from

[Prototype-core] Re: Inheritance: your thoughts?

2007-07-01 Thread DK
On Jun 29, 8:22 pm, Tobie Langel [EMAIL PROTECTED] wrote: How is Class a constructor ? Constructor in JavaScript is a function, which called with var someObject = new someFunction(); returns an object, which behaves similar to all objects created the same way. So in my implementation (as in

[Prototype-core] Re: Inheritance: your thoughts?

2007-07-01 Thread DK
On Jun 29, 8:22 pm, Tobie Langel [EMAIL PROTECTED] wrote: Properties applied to it's prototype aren't available on the instances. My implementation breaks this 'chain' (properties from 'prototype' accessible in objects created by 'new'), so I had to recreate it myself. PS. Sorry for my

[Prototype-core] Re: Inheritance: your thoughts?

2007-06-25 Thread DK
On Jun 25, 7:50 am, Andrew Dupont [EMAIL PROTECTED] wrote: On Jun 24, 7:48 pm, Tobie Langel [EMAIL PROTECTED] wrote: I personally prefer the following syntax: var Animal = new Class({ ... }); var Cat = new Class(Animal, { ... }); I abhor this syntax. I wish I could put

[Prototype-core] Re: $ function

2007-06-17 Thread DK
I agree with jdalton - performance hit. I agree also that you shouldn't use the same values for name's and id's. $() is made for one purpose - to find elements with given id. It should be VERY fast in every case as it's a base function of Prototype. IMO, if found' element's id isn't the same

[Prototype-core] Re: Event.element() oddity

2007-06-16 Thread DK
Hmm, maybe it's a little OT but I thought maybe sb doesn't already know, and would like to know :-) Apple Safari 3 public beta http://www.apple.com/safari/ Apple Safari will work on Windows too. On Jun 16, 3:57 pm, Thomas Fuchs [EMAIL PROTECTED] wrote: Note that IIRC the onload event for

[Prototype-core] Re: Empty catch blocks

2007-04-01 Thread DK
your callback from firing. Does anyone else in Core know more about this? IMO this is the only case to disscuss. Greetings DK --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To post

[Prototype-core] Ajax.Request - eval()'ing the responseText

2007-03-02 Thread DK
for JSON. Or maybe it's a prototype design mistake - returning JSON with responseText is OK and it shouldn't be evaluated automagically but only on user demand. Or the other way round - it should be evaluated but saved. I'm not sure. Giving it under discussion :-) Thanks for the great work :-) DK