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. | + | * Programming languages (oep.designer.proglang or oep.designer.language) |
** C++ | ** C++ | ||
| − | *** Profile (oep.designer. | + | *** Profile (oep.designer.language.cpp.profile, in general oep.designer.language.<langName>.profile) |
| − | *** Model libraries (oep.designer. | + | *** Model libraries (oep.designer.language.cpp.library) |
While some libraries are specific for a programming language (e.g. due to embedded opaque behaviors), many are not. | 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. | We have another place for programming language independent libraries below. | ||
| − | *** Code generators (oep.designer. | + | *** Code generators (oep.designer.language.cpp.codegen |
*** Editor support (e.g. integrated CDT editor) | *** Editor support (e.g. integrated CDT editor) | ||
*** Reverse/roundtrip support | *** Reverse/roundtrip support | ||
| Line 22: | Line 22: | ||
** ... | ** ... | ||
| − | * model libraries (oep.designer.library | + | * programming language independent model libraries (oep.designer.library |
| + | I prefer the short name compared to oep.designer.language.common.library | ||
| − | * Component based designer (oep.designer. | + | * Component based designer (oep.designer.component) |
** 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 | ||
** M2M transformation core | ** M2M transformation core | ||
| − | ** model libraries with container services and interaction components (oep.designer. | + | ** model libraries with container services and interaction components (oep.designer.component.library) |
| − | Option: include these libraries in one of the library places above (oep.designer.language.library or oep.designer.library) | + | Option: include these libraries in one of the library places above (oep.designer.language.<langName>.library or oep.designer.library) |
Revision as of 11:29, 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.proglang or oep.designer.language)
- C++
- Profile (oep.designer.language.cpp.profile, in general oep.designer.language.<langName>.profile)
- Model libraries (oep.designer.language.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.language.cpp.codegen
- Editor support (e.g. integrated CDT editor)
- Reverse/roundtrip support
- C
- Java
- ...
- programming language independent model libraries (oep.designer.library
I prefer the short name compared to oep.designer.language.common.library
- Component based designer (oep.designer.component)
- 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.component.library)
Option: include these libraries in one of the library places above (oep.designer.language.<langName>.library or oep.designer.library)