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

Papyrus/CodeGenerationAndDeployment

< Papyrus
Revision as of 05:50, 8 February 2016 by Ansgar.radermacher.cea.fr (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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