Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Papyrus/CodeGenerationAndDeployment"

 
(One intermediate revision by the same user not shown)
Line 9: Line 9:
  
 
'''Papyrus designer (oep.designer)'''
 
'''Papyrus designer (oep.designer)'''
* Programming languages (oep.designer.proglangs or oep.designer.languages)
+
* Programming languages (oep.designer.proglang or oep.designer.languages)
 +
** common issues: oep.designer.languages.common
 
** C++
 
** C++
*** Profile (oep.designer.languages.cpp.profile, in general oep.designer.languages.<langName>.profile)
+
*** Profile (oep.designer.language.cpp.profile, in general oep.designer.languages.<langName>.profile)
 
*** Model libraries  (oep.designer.languages.cpp.library)
 
*** 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.
+
*** Code generators (oep.designer.language.cpp.codegen
  We have another place for programming language independent libraries below.
+
*** Code generators (oep.designer.languages.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 21:
 
** ...
 
** ...
  
* 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
 
** 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 transformation core
+
** M2M transformations
** model libraries with container services and interaction components (oep.designer.components.library)
+
*** core (oep.designer.components.transformation.core)
  Option: include these libraries in one of the library places above (oep.designer.language.library or oep.designer.library)
+
*** 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)

Back to the top