Hi Rob,
On 11/30/06, RobG <[EMAIL PROTECTED]> wrote:
> The developers of Prototype have made some contentious architectural
> decisions. Users should be aware of those and accept the limitations
> that they enforce - lack of namespacing and extension of built-in
> objects being two of the better known ones, I'd also add the
> evalScripts method to the list (I think the concept is fundamentally
> flawed). And yes, I think Peter is wrong to support it.
Can you please elaborate? I am not completely fixed on this method but
because of the problems that Safari causes (can't set the text
property of a script element), eval may be the cross browser way to go
and insure other unknown browsers can handle it as well. Instead of
evaluating
function foo(){}
you can write
window.foo = function(){}
to ensure the evaluated code really does go in the global space where intended.
Thanks,
Peter
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
