Community
Participate
Working Groups
Looking at the M2 build, there are a lot of code templates under Preferences > EGL > Editor > Templates that are not applicable in the EDT IDE. At a minimum, we should remove the templates that are completely invalid for EDT IDE ("transfer to program"). It seems code templates should be contributed by the UI plug-in of a generator or compiler (?) since some are tied to a specific compiler/generator. Others are "basic", and possibly should be included by Core. (There needs to be some discussion on this, if there hasn't been discussion already)
Created attachment 201417 [details] EDT M2+CDL build Code template preference page
Another example: "Rich UI widget" is not applicable in the case of an IDE that does not have the JavaScript generator installed into it.
there was a bug 354459 to review the existing code templates, correct or removing staff that does not apply to EDT language. I have assigned this to the language component cause this is more a language thing. The other problem you mentioned is to make the code template extensible，I think it is good idea to link code template to compilers. I would suggest to make this enhancement an 1.0 item.
Sorry - I didn't see bug 354459 when I opened this one. Feel free to mark this as a duplicate. Regardless of who owns the work, someone needs to at least remove VAG/RBD-specific feature templates before 0.7 ships.
I'd like to keep this open to address the extensibility problem. bug 354459 does need to be in 0.7, besides the templates that does not apply to EDT, many template are not correct now because of the language changes. For example Record myrec type BasicRecord now needs to be Record myrec
Now we have most of the templates in "egl-core" context, and two in "egl-rui" context. In RBD, context maps to Project Natural which does not apply to EDT. As a short term fix (to avoid confusion of what "egl-rui" is), I would like to put all templates into "egl-core" for 0.7. From the concept of EDT, templates really need to be organized by Compilers. And only the templates for the enabled compiler should be activated. (Should it be compiler or generator? ). I would consider this as a 1.0 feature unless somebody think it is very important.
Created attachment 202775 [details] merge egl-rui into egl-core context
Tony, I agree that organizing the templates by compiler or generator should be done in 1.0 not 0.7.
Triage this to future.
