Ideally speaking, you are spot on Matt, but in reality I just don't see that to be a feasible, scalable option. In a large project, such an approach has lead me (I used to be a stickler for such design patterns) down a prickly path of one-off solutions in hundreds of different places in my JavaScript.
It's much easier to manage, at least in my opinion, when it's all generated from the backend. -justin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
