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.proglang or oep.designer. | + | * Programming languages (oep.designer.proglang or oep.designer.languages) |
+ | ** common issues: oep.designer.languages.common | ||
** C++ | ** C++ | ||
− | *** Profile (oep.designer.language.cpp.profile, in general oep.designer. | + | *** Profile (oep.designer.language.cpp.profile, in general oep.designer.languages.<langName>.profile) |
− | *** Model libraries (oep.designer. | + | *** Model libraries (oep.designer.languages.cpp.library) |
− | + | ||
− | + | ||
*** Code generators (oep.designer.language.cpp.codegen | *** Code generators (oep.designer.language.cpp.codegen | ||
*** Editor support (e.g. integrated CDT editor) | *** Editor support (e.g. integrated CDT editor) | ||
Line 22: | Line 21: | ||
** ... | ** ... | ||
− | |||
− | |||
− | * Component based designer (oep.designer. | + | * Component based designer (oep.designer.components) |
** Existing plugins of qompass designer with the new prefix above | ** 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 (oep.designer.components.fcm.profile) |
− | ** M2M | + | ** M2M transformations |
− | ** | + | *** core (oep.designer.components.transformation.core) |
− | + | *** programming language specific (oep.designer.components.transformation.<lang.name> | |
+ | ** model libraries with container services and interaction components (oep.designer.components.modellibs) |
Latest revision as of 05:50, 8 February 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.proglang or oep.designer.languages)
- common issues: oep.designer.languages.common
- C++
- Profile (oep.designer.language.cpp.profile, in general oep.designer.languages.<langName>.profile)
- Model libraries (oep.designer.languages.cpp.library)
- Code generators (oep.designer.language.cpp.codegen
- Editor support (e.g. integrated CDT editor)
- Reverse/roundtrip support
- C
- Java
- ...
- 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 (oep.designer.components.fcm.profile)
- M2M transformations
- core (oep.designer.components.transformation.core)
- programming language specific (oep.designer.components.transformation.<lang.name>
- model libraries with container services and interaction components (oep.designer.components.modellibs)