Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/CodeGenerationAndDeployment"
< Papyrus
| Line 9: | Line 9: | ||
'''Papyrus designer (oep.designer)''' | '''Papyrus designer (oep.designer)''' | ||
| − | * | + | * Programming languages (oep.designer.proglangs or oep.designer.languages) |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
** C++ | ** C++ | ||
| − | *** Profile | + | *** Profile (oep.designer.languages.cpp.profile, in general oep.designer.languages.<langName>.profile) |
| + | *** Model libraries (oep.designer.languages.cpp.library) | ||
| + | While some libraries are specific for a programming language (e.g. due to embedded opaque behaviors), many are not. | ||
| + | We have another place for programming language independent libraries below. | ||
| + | *** Code generators (oep.designer.languages.cpp.codegen | ||
| + | *** Editor support (e.g. integrated CDT editor) | ||
| + | *** Reverse/roundtrip support | ||
** C | ** C | ||
| − | ** Java | + | ** Java |
** ... | ** ... | ||
| + | |||
| + | * model libraries (oep.designer.library) | ||
* Component based designer (oep.designer.components) | * Component based designer (oep.designer.components) | ||
| − | ** | + | ** Existing plugins of qompass designer with the new prefix above |
** FCM profile (maybe UCM - Unified component model) in the future | ** FCM profile (maybe UCM - Unified component model) in the future | ||
** M2M transformation core | ** M2M transformation core | ||
| − | ** model libraries with container services and interaction components | + | ** model libraries with container services and interaction components (oep.designer.components.library) |
| + | Option: include these libraries in one of the library places above (oep.designer.language.library or oep.designer.library) | ||
Revision as of 11:25, 22 January 2016
This page is there to discuss the naming of the plugins related to code generation, analysis and deployment.
Currently, the following structure is proposed
Papyrus Architect (oep.architect)
- Schedulability analysis & Architecture exploration
Papyrus designer (oep.designer)
- Programming languages (oep.designer.proglangs or oep.designer.languages)
- C++
- Profile (oep.designer.languages.cpp.profile, in general oep.designer.languages.<langName>.profile)
- Model libraries (oep.designer.languages.cpp.library)
- C++
While some libraries are specific for a programming language (e.g. due to embedded opaque behaviors), many are not. We have another place for programming language independent libraries below.
- Code generators (oep.designer.languages.cpp.codegen
- Editor support (e.g. integrated CDT editor)
- Reverse/roundtrip support
- C
- Java
- ...
- model libraries (oep.designer.library)
- Component based designer (oep.designer.components)
- Existing plugins of qompass designer with the new prefix above
- FCM profile (maybe UCM - Unified component model) in the future
- M2M transformation core
- model libraries with container services and interaction components (oep.designer.components.library)
Option: include these libraries in one of the library places above (oep.designer.language.library or oep.designer.library)