Rails spinoffs - Mar 2008 - getElementsByClassName

I know this is deprecated in 1.6, but my question is how do I properly
use the native browser implementation?  Do I need to change my code?
I''m having a difficult time finding examples on this.  Why is this
deprecated instead of incorporated into prototype?  Or did I answer my
own question...

Also, I want  to utilize the new document.querySelector. Has some one
implemented this inside prototype and I don''t have to change anything
to take advantage of it?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

it says why next to the exclamation point on that page!
http://www.prototypejs.org/api/element/getElementsByClassName

what''s more, its better to use the $$() function since I think it
transparently extends the prototype stuff in the elements returned with the
selector

...and if querySelector() does what it says i think it does in the spec...
http://www.w3.org/TR/selectors-api/#documentselector  couldn''t you you
just
use the prototype class selector $$() and get the first element? like
$$(''class'')[0]?



On Fri, Mar 21, 2008 at 12:50 PM, Namotco
<namotco-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> I know this is deprecated in 1.6, but my question is how do I properly
> use the native browser implementation?  Do I need to change my code?
> I''m having a difficult time finding examples on this.  Why is this
> deprecated instead of incorporated into prototype?  Or did I answer my
> own question...
>
> Also, I want  to utilize the new document.querySelector. Has some one
> implemented this inside prototype and I don''t have to change
anything
> to take advantage of it?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

The reason I''d prefer to be using the native implementations is
speed.  Yes, I know prototype already does these things, but in my
application I would like to have the additional performance provided
by the native implementations.

So my question is as a prototype user, how do I get the speed benefit
of these new native technologies?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Namotco,

JDD already worked on patching prototype to use querySelector [1]. The
problem is that there are some inconsistencies in the way $$ and
document.querySelector work. The support for native selectors might
make it''s way into 1.6.1 version of prototype.

[1] http://dev.rubyonrails.org/ticket/11085

- kangax

On Mar 22, 12:45 pm, Namotco
<namo...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> The reason I''d prefer to be using the native implementations is
> speed.  Yes, I know prototype already does these things, but in my
> application I would like to have the additional performance provided
> by the native implementations.
>
> So my question is as a prototype user, how do I get the speed benefit
> of these new native technologies?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---