| Summary: | Compiled javascript out of sync with scripts in html | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Andrew Niefer <aniefer> |
| Component: | Client | Assignee: | Project Inbox <e4.orion-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | susan |
| Version: | 0.2 | ||
| Target Milestone: | 0.2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Andrew Niefer
I updated the closure.xml with the changes for the navigator, but N2011022320 still has a broken editor. I have now added globalCommands.js to the compiled eas.js file so the next build should be good. I had to make some additional changes to coding.html, I created a new compiled block named coding-editor-container.js, and moved the globalCommands.js out of the eas.js block. sorry, Andrew. I knew to be paranoid about new bundles, but didn't realize/remember that the closure.xml had to be updated for script file changes. I thought it was derived from the file itself. (Do we have a page on the wiki about what kinds of structural changes matter and what needs to be updated when they are made?) (In reply to comment #3) > sorry, Andrew. I knew to be paranoid about new bundles, but didn't > realize/remember that the closure.xml had to be updated for script file > changes. I thought it was derived from the file itself. > > (Do we have a page on the wiki about what kinds of structural changes matter > and what needs to be updated when they are made?) Don't worry Susan, I forgot about this myself until it stopped working. I think we will need to come up with a better story here going forward. Sometime soon I will be attempting to compile dojo, we will see if that experience provides a more manageable way of compiling our own js. There is no wiki about this currently, I'll put it down on the list of things to do. |