1 / 6

Comparative Analysis of GMF and Graphiti: Insights from the KPD Symposium

This summary highlights key discussions from the KPD Symposium featuring Andreas Rentschler, Christian Stritzke, Jóakim Gunnarson, Mario Wieser, and Misha Strittmatter. The presenters examined the strengths and weaknesses of Graphiti and GMF in terms of code maintainability, modularity, and extensibility. Notably, Graphiti is seen as more mature, surpassing GMF in understandability and maintainability. However, both approaches face challenges, such as manual routing and layout programming. The consensus favors Graphiti for future PCM editor implementations.

gafna
Télécharger la présentation

Comparative Analysis of GMF and Graphiti: Insights from the KPD Symposium

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GMF vs. Graphiti BOG Results KPD Symposium Andreas Rentschler, Christian Stritzke, JóakimGunnarson v. Kistowski Mario Wieser, Misha Strittmatter

  2. Erwartungen • Graphiti/Spray interestingfor Palladio Refactoring • forDiff Viewer • longterm: replacementof PCM Editors

  3. Requirements • Modularizable / Extensible • Reuseable • Graphiti: • morematurethan GMF • codebettertomaintain& betterunderstandability

  4. Graphiti (vs. GMF) • Con • Routing of Lines havetobeprogrammedmanually • Layouting • Coderedundancy • Pro • moremature • gefand draw2d encapsulated • bettermaintainability (customizations in GMF generatedcode)

  5. Spray (vs. Graphiti ohne Spray) • Pro: • Code generation • Codeparts canbecomfortablyexcludedfrom (re)generationtomakemanualcusomizations • Con: • Kein Zugriff auf Eigenschaften des Parent Shapes • Graphiti entwickelt sich schneller als Spray • Spray generiert noch in altes Feature Konzept • Tool nicht stabil • Generierte Editoren haben Abhängigkeiten zu Spray • DSL für Shapegenerierung ist nicht ausgereift • Spray vermutlich nicht für Editorfragmente geeignet

  6. Conclusions • Graphitigood • Spray bad • As mentioned in Chrisitans Talk: Sebastian Lehrigshouldimplement all PCM Editors withGraphiti

More Related