On Aug 2, 8:07 am, Christophe Porteneuve <[EMAIL PROTECTED]> wrote:
> Hey,
>
> I can't believe this thread is so long... There's just no way we won't
> extend prototypes on elements, I think. It's at the core of what we do.
Yes, there definitely is a way, in Firefox:
1) Create a page with an iframe. The page should import prototype.js.
2) Create a page to be loaded in the iframe. That page should *not*
import prototype.js.
3) Have the iframe page call
"parent.something(document.getElementById('x'))", such that the parent
"something" function calls $(arg) on its argument and then expects the
object to have all the Prototype element extensions.
4) Boom.
"That's silly", you may say, "just import prototype in your iframe
page." That is indeed the best approach to take, but it's a non-
trivial issue in an extensive application with hundreds of pages that
all use services on the "top" page. The "top" code cannot expect
using $() to extend correctly incoming (as parameters) elements until
all pages have been changed to import Prototype.
--~--~---------~--~----~------------~-------~--~----~
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
