Community
Participate
Working Groups
In VE design/preview mode, we are loading the dependent JS files from the context by appending a contextKey to the URL. This approach is part of the cause of the performance issue described in Bug 360348 The contextKey is only necessary for parts that exists in the current file being displayed in VE. The handler js needs to have contextKey. And for example, a record was defined in the same file as the handler, that record needs to have a contextKey. Any other files, widgets from our widget project for example, don't need contextKey.
We probably should modify RUITemplate.generateDependentFilePath(). If the referenced part is in the same egl file as handler, then it needs contextKey, otherwise not. Be sure not to change the sequence of the dependent file list when adding this logic.
How this enhancement implemented depends on what decision we come out from Bug 368555 - Investigate modular loading in HTML generator. If the modular loading is going to be done, we won't have a list of all dependencies in the HTML. In such case, we need another way to tell the loader about the contextKey. It's also a question how does the loader handler the contextKey if it is a 3rd party AMD loader. I'm moving this bug back to the 0.8 backlog until we have a decision in Bug 368555.
We've decided to go forward to redesign modules using AMD API. HTMLGenerator needs to be changed to pass the contextKey to loader. Only parts that exists in the current file being displayed in VE needs to be loaded from context.
The context key is generated by HTML Generator, so change the owner to Ji Yong
Triage with Tony & Brian. We will only generate contextKey for current handler. Done as child of bug 363555
close
