Hi,
If not removing it completely, I would go for a way (options, second version
etc) to turn it off. Sometimes I even think of a global flag for that. Have
been playing around with symfony now for a while. I guess Ruby includes it
same way. Shouldn't in the framework case the framework escape everything
while generating the Javscript code? So I would go further and say that
scriptaculous can even expect getting escaped text. But since there are
manual users who might need it I would like to have a switch for it, as it
is, like Colin mentioned, a big hit there.
.: Fabian
-----Original Message-----
From: Colin Mollenhour
Sent: Samstag, 6. Januar 2007 03:36
To: [email protected]
Subject: [Rails-spinoffs] Re: SAU/Prototype performance
So Marius debunked my "improvement" to escapeHTML but did prove that
other methods can be much faster.
However, what are your thoughts on removing the usage of escapeHTML from
_attributes altogether? I think Builder.node needs to be optimized for
speed as much as possible since it is something that could be called
thousands of times easily. I will be looking into the usage of cloneNode
to help alleviate this, but the code probably won't be as neat and I
won't always be able to use cloneNode.
Thanks,
Colin
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
