Can the changed lines/classes you're talking about be factored out into a separate "prototype-overrides.js" file which you can load into the docuement after prototype.js is loaded, thus overwriting (or Object.extending) the existing classes with your added functionality, but still allowing you to keep a core prototype file that matches the official trunk?
...just a thought.
On 7/19/06,
Maninder, Singh <[EMAIL PROTECTED]> wrote:
Todd,
Your solution works perfect for me (from the first round of testing that I have done).
There is just one small issue -
Currently, I have made changes to my prototype file.
But, this means that tomorrow if new version of prototype comes out, it's going to be a pain maintaining it.
What do you suggest - should we extend and add these lines (which would mean duplicating a lot and still no guarantee of not making changes in the future)?
I wish Sam would incorporate this.
Thanks,
Mandy.
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
