I tend to find that Django's true potential bubbles up when all of the components work together in an interdependent manner. Normally that sounds like a bad idea (too much interdependency could make it hard to grasp the bigger picture), but for some reason, Django comes together very nicely as you figure out how all of these components can co- exist.
I hadn't realized that form media comes out of the queue after widget media. That does seem pretty backwards, since it's totally logical to place form-wide media dependencies on the form itself. If you're certain that that's what it's doing, you might consider making a simple bug report on it, with your reasoning for reporting it as such. The developers who go over the tickets are always looking for solid "real-world" problems that a bug report claims to exist. If it's only a preferential thing, it won't get much consideration. But if you can prove why changing it makes more sense, you'll have a case for making an improvement. Bugs will be the focus of version 1.2's development once January comes around. Anyway, I hope things are rolling for you now :) Tim On Nov 25, 4:00 pm, Todd Blanchard <tblanch...@mac.com> wrote: > Actually, a widget required a js file that required core.js, but did not > specify it. So I added core.js to the form's media list - but apparently it > renders the widget media, then the form media - so no good. > > Your second suggestion was the best - I now just include the jsi18n and > core.js on every page as part of the base template. > > So far so good. Hopefully I won't find any more widgets with surprise > dependencies. > > -Todd Blanchard > > On Nov 25, 2009, at 12:14 PM, Tim Valenta wrote: > > > > > Is it a widget that has the "core.js"? I'd suggest putting that on > > the form instead, if that's the case. Alternatively, if the page > > should always have this JS anyway, you could always insert it directly > > to the template, to avoid any ambiguity for any future eyeballs > > wondering how it all works. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
