kangax,
you showed how to correctly use a context in Prototype selectors and
still perform fast (without repeating the context).
Another problem, from what I understand, is that this will only work
if the user doesn't care about the order of elements being returned or
if the order is known before
On Apr 20, 7:42 am, Diego Perini wrote:
> kangax,
> you showed how to correctly use a context in Prototype selectors and
> still perform fast (without repeating the context).
>
> Another problem, from what I understand, is that this will only work
> if the user doesn't care about the order of ele
kangax,
knowledge of the tools one have at his disposal is important to be
able to reach the objectives.
It is clear I don't have that knowledge, therefore all those wrong
assumptions.
Thank you for remembering me about the Form.getElements().
(actually you already did it before in another post.
Turn $6 into $15,000 in only 30 days... here's how !
http://www.geocities.com/ksameera86/
--~--~-~--~~~---~--~~
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@g
Hi folks!
I'm happy to tell you, that I've just commited preview version of
prototype profiler tool, called pro2js (http://code.google.com/p/
pro2js/). It offers good selectors log and dom:onload profiling. Here
is the screenshot of the demo app:
http://img.skitch.com/20090418-fm3iaa8hta3wu4sk3my
