| Summary: | How to include dependencies of header and footer commands in each page | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John Arthorne <john.arthorne> |
| Component: | Client | Assignee: | Simon Kaegi <simon_kaegi> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | simon_kaegi, susan |
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
John Arthorne
Just to document here, to fix the "Open Resource" problem I had to add a couple of dojo requires on each page, and ensure the dojo module page had the scripts required by the header:
var djConfig = {
isDebug : true,
modulePaths : {'widgets': '/js/widgets'},
parseOnLoad : true
};
Multiply by about ten pages...
For this specific case, I consider this bug to be a symptom of the bigger problem described in bug 340019. Rather than have us focus on dependency management to solve this problem, I'd like to see us come up with a real story for including one set of html/js in all the pages. This is fixed by Simon's changes for require js. The js files for the global header and footer now explicitly state their dependencies, so the dependency on Open Resource Dialog is stated in globalCommands.js (Just now OpenResource was broken when invoked from the editor because dijit.form.TextBox was missing as a requirement. Added it as a requirement of open resource dialog. Now it works. Cool.) |