This one time, at band camp, Ben Bangert wrote: > >On Apr 30, 2006, at 6:38 PM, Jamie Wilkinson wrote: > >> This one time, at band camp, James Gardner wrote: >>> I've added two modules to webhelpers and incremented the version >>> number >>> to 0.1.1, so if you do make a release that would be cool. Are you >>> planning on implementing the scriptaculous command to copy the files >>> into the users Pylons directory or should I press ahead and write >>> middleware in webhelpers.middleware that can go after staticapp in >>> the >>> cascade and load the files straight from webhelpers? Which do you >>> think >>> is the better approach? If you don't want the scriptaculous >>> command we >>> should probably remove it. >> >> I vote for the latter, so that Pylons authors don't have to know or >> care >> about it. > >I'm somewhat more in favor of a command to copy them into your >current project, mainly since I don't want to keep adding bits of >function overhead constantly thats easily solved by a one-time copy >command. While one of these is unlikely to make a difference, it sets >a precedence for throwing middleware at a problem that PasteScript >handles well... copying resources into project directories.
Just out of curiousity's sake, how much does the Pylons template change between versions? (How much has it changed with the impending 0.9 release from 0.8?) See, it seems to me that there's going to be newer code in the template that uses newer features of Pylons, and that means looking at the template and merging that code into my own; if a newer webhelpers comes with some javascript that fixes bugs from a previous release, I'd like to have that just work with an upgrade rather than having to remember to copy it in. It's a separate library, not my own, so I don't think it belongs in my source tree. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss -~----------~----~----~----~------~----~------~--~---
