Community
Participate
Working Groups
The table on the EGL Templates preference page has a Context column that displays the capability that each template is associated with. Do we only have a single EGL capability (egl-core) in EDT? If so, this column should be removed. (Capabilities are listed under General preferences. I recall Justin saying in a scrum that he didn't see them in Linux. I do see them in Windows.)
Will, Do we need remove the 'Context' column, it seems egl-core is not the only EGL capability, I found another called egl-rui for widget and Rich UI handler
It seems like we're misusing the Context column today. If you look at the Java > Editor > Templates panel, you'll notice the "Context" column indicates which context (Javadoc, Java, Java type members, etc) a template is applicable for. We currently have "edt-core" and "egl-rui", but certainly some templates under edt-core can be used in the context of RUI. So, my thoughts ... 1) Keep the Context column since we may have EGLDoc someday soon (which would be another context) and because other vendors (i.e. generator providers) will be able to contribute code templates (that support new stereotypes/annotations they may have created). 2) Put all "core" templates under an "EGL Core" context (Tim can help with the name). These templates cover the base language features (FOR loops, if statements, etc). A second context would include all "extensions" (i.e. things we're adding support for on top of the base, for example: RUIHandler). Tim - can you add your thoughts on this since this ties into the separation you're trying to keep between the core and the extensions?
maybe we can use the context column to specify which compiler the template applies to. Only available templates can be used for the selected compiler. If we have a set of templates which apply to any compiler, we can make that egl-core.
fixed
Closing this defect.
