Reply | Original | Permalink | TweetYes, I should, but I never used that method, so I didn’t bother to do so. ;-)
Reply | Original | Permalink | TweetGAVIN SIGHTING
Reply | Original | Permalink | TweetYou are forgiven. :-)
Oh, we’ve got all kinds of plans for 2.0.
Reply | Original | Permalink | TweetAh, I see it now. Though your “recreating the wheel” remark is a bit asinine, since in order to do it the way MooTools has we’d need to adopt a lot of other magical conventions, as you must know. Our class system is lighter and handles things a lot differently than that of MooTools.
Reply | Original | Permalink | Tweet@sethaurus: True in both cases. That’s why
Object.deepExtendwould be safe to use only in narrow circumstances, and one major reason why I would not want to include this in Prototype.@Joran: I don’t know — what’s the use case? In my implementation, I chose to copy arrays by reference because they’re not object literals, and treating them as such would cause some bizarre side-effects.
Reply | Original | Permalink | Tweet@Thomas: As far as I can tell, MooTools’
Optionsmixin doesn’t handle inheritance. Please correct me if I’m wrong.
Reply | Original | Permalink | TweetIt wasn’t always the ghetto that got bulldozed to make room for the highway. In New Orleans, the proposed Vieux Carré Riverfront Expressway would have been (naturally) a loss for preservation and for history. Thankfully, the cult of personality around Robert Moses was, by then, beginning to dissipate.
Reply | Original | Permalink | Tweet"Maybe I’m just a gay dude and therefore not blinded by pussy like the majority of you straight guys, and can behave like a mature and thoughtful adult, but I think I side with the ladies here."
I think you're less concerned with persuading people to your point of view and more concerned with acting smug.
Reply | Original | Permalink | TweetAndrew Dupont wrote:
So how does this whole "reparations" thing work? You pay Jennifer in twelve easy $1,000 installments, and then when you're done you get some sort of certificate, or hand stamp, or something, that says you're all square?
If this signet ring is good for all of Africa, I'd say go for it. But check the fine print. It might apply only to Nigeria.
Reply | Original | Permalink | Tweeterik k, I’ll concede that it’s arguable that Chandler would be useless without Paul. But David West? Have you ever watched a Hornets game? Dude isn’t getting his points off of pick-and-rolls and alley-oops. He’s creating offense from a wide variety of post moves and a deadly mid-range jumper.
Reply | Original | Permalink | TweetActually, Josh, I looked over the raw XML once again and realized it gives me everything I need. I think I started screen-scraping in order to get vote breakdowns by party — that information isn’t in
votes.all.index.xml, nor in the XML file for an individual vote.But that was back when I was trying to avoid keeping track of senators individually. Once I started compiling senators’ voting records, party breakdown became trivial. When I get some time, I’ll rewrite that part of the code, which will make it a lot simpler. Thanks!
Reply | Original | Permalink | TweetRuby has shown us that a bit of syntactic flexibility can go a long way. For instance, Ruby has “getters” and “setters” simply because parentheses are optional in method calls.
Likewise, one can leave off the braces when passing a hash into a method (except where it would cause ambiguity), thus approximating named parameters. If we could likewise leave off the braces in JavaScript, we’d be 90% there.
Reply | Original | Permalink | TweetHeh, thanks. Credit there goes to Sam and Seth Dillingham. I can’t say for sure that they had this specifically in mind when they wrote it — looks more like a nice bonus.
We use
ondataavailablefor regular custom events; I endeavored to add support for non-bubbling custom events in the next version, but discovered we’d have to “borrow” an IE event that itself does not bubble. So we useonfilterchangefor that.If someone happens to be using either of these events in their apps outside of Prototype, that’s not a huge deal — we just check for our “fingerprints” on the event object and return early if it’s clear the event didn’t come from us.
Reply | Original | Permalink | TweetWe “support” it with timers only in that we use the timer to know when to fire the custom event (and even then we only use the timer in Safari). I wrote about our custom events support a while back; you can also check out the API for Element#fire.
Reply | Original | Permalink | TweetWait, what? We have supported custom events since 1.6. Here’s my demo page.

