The prototype library is getting heftier and heftier to load into every page (though, the cost of loading under a megabyte into a page is getting lower and lower at the same time). I'm refactoring a web application to, among many other things, leverage [wherever possible] ajax to inform more structured (and much more compact) interfaces and make business logic more accesible inline.
The issue I'm having is in cutting up the prototype library into constituent files and finding a good strategy for doing it. I already have a very good implementation of a dependency loader that loads script into the browser just-in-time (based on stated dependencies in the currently loading source file), and I want to push prototype into smaller files that leverage this to load up a custom environment of javascript based on the needs of the interface. Does anyone have any good suggestions/recommendations for pulling apart prototype.js beyond a base/ajax strategy? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
