Jul 17, 2012 at 7:36 PM
Edited Jul 17, 2012 at 9:36 PM
Scripts were overriden correctly in my case. As @TheMonarch pointed out, the theme isn't active in the admin dashboard which is the "module" from which I initially tried to override the TinyMCE config script. I haven't looked at
the code in a while, but I got it working and I think my solution was just placing the script in a module which was actually active whilst the Admin theme is applied.
If I use Script.Require() in module B, which depends on module A, I want to use the script that module A registered unless module B has overriden that with a more specific (more local) version. I believe this should continue to be determined by
If module B does override a script in A, I'm not sure I'd really want to enforce an implicit dependency of A on B.
If I wanted a view in module A to use the script defined in B, then I would override the shape (view) from A that references that script. This shape will use the most local script defined in module B.
Imagine the case of both modules B and C depending on A. Say both B and C seek to override a script that A defines. Which script would A then use?
What if C depends on B which depends on A and C overrides a script defined in A. Would both B and A now reference the script from C?