[Prototype-core] Re: Source code style

2007-10-05 Thread Sven Klose
I actually did my first JavaScript coding in 1998, my first programming at all was in 1985. It's really the headache I get, and the time lost. Ryan Gahl wrote: > This is all stuff you learn to grok quickly as you gain javascript > experience. When you think in closures, only then can you attain

[Prototype-core] Re: Source code style

2007-10-05 Thread Thomas Fuchs
Hi Sven! We won't change the way the source code is formatted, as we like it the way it is. Most people take a short while to "switch over" from more traditional JavaScript source code formatting, but once you've made that step the code is pretty easy to read. The basic rules governing the

[Prototype-core] Re: Source code style

2007-10-05 Thread Richard Quadling
Are there any good JS prettifiers online? Maybe a link through for those needing a little visual help would benefit? On 05/10/2007, Thomas Fuchs <[EMAIL PROTECTED]> wrote: > > Hi Sven! > > We won't change the way the source code is formatted, as we like it > the way it is. Most people take a short

[Prototype-core] Re: Source code style

2007-10-05 Thread Mislav Marohnić
On 10/5/07, Richard Quadling <[EMAIL PROTECTED]> wrote: > > Are there any good JS prettifiers online? Yup http://prototypejs.org/assets/2007/3/13/mislav.jpg This guy is online in IRC right now! --~--~-~--~~~---~--~~ You received this message because you are subsc

[Prototype-core] Bug in the compressed and formatted code

2007-10-05 Thread xinze
files:protopacked_v2.16b.zip ->formatted prototype-1.5.2_pre0.js I found that the function "getElementsByClassName" in the compression and formatting code could not use in the Firefox Today, I download the file 'protopacked_v2.16b.zip', and replace prototype.js with the compressed code ,

[Prototype-core] Re: Error when using Prototype 1.6.0_rc0

2007-10-05 Thread Mislav Marohnić
On 10/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > I am having the exact same issue. The code just stops at > handler.call(event.target, event); without throwing an error. It > works fine in IE. You realize that there's nothing we can do unless you provide us with a minimal failin

[Prototype-core] Re: Error when using Prototype 1.6.0_rc0

2007-10-05 Thread [EMAIL PROTECTED]
I am having the exact same issue. The code just stops at handler.call(event.target, event); without throwing an error. It works fine in IE. On Aug 17, 3:13 am, Frederic Gaus <[EMAIL PROTECTED]> wrote: > Hi Guys, > > first of all I want to thank all of you for producing such a great > framew

[Prototype-core] bad link

2007-10-05 Thread Sébastien Gruhier
on online doc: http://prototypejs.org/api/element/writeattribute is a bad url (from left column "writeAttrbute" of Element Seb --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to th

[Prototype-core] Re: bad link

2007-10-05 Thread Mislav Marohnić
On 10/5/07, Sébastien Gruhier <[EMAIL PROTECTED]> wrote: > > on online doc: http://prototypejs.org/api/element/writeattribute is a bad > url (from left column "writeAttrbute" of Element > Fixed, thanks --~--~-~--~~~---~--~~ You received this message because you are

[Prototype-core] Re: Error when using Prototype 1.6.0_rc0

2007-10-05 Thread [EMAIL PROTECTED]
I figured it out. I had a custom function similar to prototype's new 'delay' function. Removing my function fixed the issue. The strange part, was that no errors were being thrown. Firefox just stopped at handler.call. All is well now. On Oct 5, 10:53 am, "Mislav Marohni " <[EMAIL PROTEC

[Prototype-core] Re: Error when using Prototype 1.6.0_rc0

2007-10-05 Thread Mislav Marohnić
On 10/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > I figured it out. I had a custom function similar to prototype's new > 'delay' function. Removing my function fixed the issue. The > strange part, was that no errors were being thrown. Firefox just > stopped at handler.call. Ye

[Prototype-core] Re: Bug in the compressed and formatted code

2007-10-05 Thread xinze
I figured the issue out. if (Prototype.BrowserFeatures.XPath) { document._getElementsByXPath = function(expression, parentElement) { var results = []; var query = document.evaluate(expression, $(parentElement) || document, null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null); f