I couldn't agree more. And as Thomas himself has expressed here... optimization is the very last thing you need to worry about.On 8/15/06, Brandon Aaron
<[EMAIL PROTECTED]> wrote:
> 1 - Is every object that is extended by Enumerable going to have iterable> class names?Yes but it will probably be n
1 - Is every object that is extended by Enumerable going to have iterable
class names?
Yes but it will probably be necessary to overwrite the _each method so
that the Enumerable knows how to iterate through your collection. At
least this is my understanding.
2 - Just how much "baggage" is too
> It creates a new class/object representing the class names. The class
> is called Element.ClassNames and it is extended by Enumerable. That
> means you can iterate through the element's class names. Pretty cool.
"Extended by Enumerable". Thanks. Now I know where to look.
A good answer usually
Of Sam
Sent: Monday, August 14, 2006 10:55 AM
To: rails-spinoffs@lists.rubyonrails.org
Subject: [Rails-spinoffs] OK. I'm confused again.
Prototype.js can be humbling. Just when I think I've got a handle on how to
read inside-out, I find something I've never seen before and can&#
Behalf Of Sam
Sent: Monday, August 14, 2006 10:55 AM
To: rails-spinoffs@lists.rubyonrails.org
Subject: [Rails-spinoffs] OK. I'm confused again.
Prototype.js can be humbling. Just when I think I've got a handle on how to
read inside-out, I find something I've never seen before and ca
Prototype.js can be humbling. Just when I think I've got a handle on how to
read inside-out, I find something I've never seen before and can't get my
head around.
I am chasing down a bug in my code which uses Element.classNames, so I
wandered off in prototype.js to see how classNames worked.
Co
