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 3: | Line 3: | ||
Currently, the following structure is proposed | Currently, the following structure is proposed | ||
| − | Papyrus designer (oep.designer) | + | |
| + | '''Papyrus Architect (oep.architect)''' | ||
| + | * Schedulability analysis & Architecture exploration | ||
| + | |||
| + | |||
| + | '''Papyrus designer (oep.designer)''' | ||
* Code generators (oep.designer.codegen) | * Code generators (oep.designer.codegen) | ||
** C++ code generator | ** C++ code generator | ||
| Line 17: | Line 22: | ||
** Java library | ** Java library | ||
** ... | ** ... | ||
| − | |||
| − | |||
| − | |||
* Component based designer (oep.designer.components) | * Component based designer (oep.designer.components) | ||
Revision as of 08:49, 19 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)
- Code generators (oep.designer.codegen)
- C++ code generator
- Includes profile and model libraries? or in Programming language below?
- C code generator
- Java code generator
- ...
- C++ code generator
- Programming languages (oep.designer.proglang)
- C++
- Profile and model libraries
- C
- Java library
- ...
- C++
- Component based designer (oep.designer.components)
- existing plugins of qompass designer with new prefix, i.e.
- FCM profile (maybe UCM - Unified component model) in the future
- M2M transformation core
- model libraries with container services and interaction components