"Cheap-but-brittle way: Make the change to the CSS and get on with it. That's what I do and I believe it's pretty common practice. When you upgrade versions, it's brittle, shatters into a million pieces, but it's easy to spot. "
Thank you. I will go with this route, already have. I can see that Mr. Yahuda Katz has his work cut out for him for Rails 3.0. After all, he is the jQuery man :) I hope he makes jQuery a first class Rails citizen instead of the rather unwelcome guest which it currently is in Rails world. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
