This is a bit off topic, but what would be the ideal process of submitting patches for you guys? It seems to me that the trac bugtracker is pretty much ignored, so should I send patches to this ML. And should I send multiple patches, or one big patch from which you can pick what you feel would be a good addition?
On Nov 22, 1:20 pm, "Mislav Marohnić" <[EMAIL PROTECTED]> wrote: > On Nov 22, 2007 11:57 AM, Viktor Kojouharov <[EMAIL PROTECTED]> wrote: > > > > > I've made a ticket with an attached patch that adds a script insertion > > method a few months ago, right here: > >http://dev.rubyonrails.org/ticket/9871 > > Whoa, that's a lot of code. > > I think the problem with this sort of functionality being in core is that a > lot of people have different requirements for their apps and also optimize > their code and asset files differently. We must take into account that most > of our users might not use the feature at all, and that we may be > introducing bloat to the framework then. I would welcome a cross-browser > feature for dynamic script tag with callback only if it were a few lines > long. > > Rest of the core team, what are your opinions on any of this becoming a part > of the library? While dynamic script tag may not be so popular vs. bundling > scripts into one optimized, gzipped file, I still think CSS injection could > be a good addition. On the other hand, almost everything that can be > accomplished with CSS injection can also be done with classname switching... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" 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/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
