It looks to me like the Media class managing the files stores JS files in a Python list, so order should be remembered. I can see the issue though if a *widget* has critical "core" media, which isn't rendered until after other bits of media already went out the hatch.
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. On Nov 25, 12:43 pm, Todd Blanchard <tblanch...@mac.com> wrote: > The latest is that the media collection strategy apparently has no concept of > order dependence when specifying or loading javascript and in my form it > seems to be sticking core.js somewhere in the middle which contains addEvent > which is required by something being loaded sooner and thus it results in > failure. > > Is there some way to specify order dependency in js files using this > mechanism? Otherwise I think it is worthless. > > -Todd Blanchard -- 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.
