Skip to main content
AgeCommit message (Collapse)AuthorFilesLines
2018-04-19Bug 527664 - [AFViewpoints] Architecture Model Editor removeMaged Elaasar1-4/+11
CreationCommandClass property value Converted the Creation/ConversionCommandClass properties in the architecture editor to be of type string instead of Class. They can now reference class names from the workspace (on their project's class path). Also added validation rules for that. Finally, I added a Browse... button in the property sheet to help put values for them. remove some reexport increase version to take in account API tool Change-Id: I6792449fbee70b089f83780c4935242fff72d50b Signed-off-by: Maged Elaasar <>
2018-04-04Bug 532299 - Add tooltips on properties in architecture frameworkMaged Elaasar1-14/+90
editor. Added descriptions on all properties that show in the architecture editor. Those descriptions appear in the status bar of the Eclipse window when the property is selected (not as toolips when hovering over properties). Also, some properties are categorized in the property sheet into sub categories to ease understanding. I also added the same descriptions as documentation of the AF model API. Change-Id: I2a4e928b177ae5434c6f38255ea1bba41c822416 Signed-off-by: Maged Elaasar <>
2017-05-10Bug 515235 - [Architecture Framework] Palette Configuration shall beBenoit Maggi1-1/+2
have a better integration to AF - add a property palettes in Meta model - remove old customePalette in Meta model - the palette application filter should be done with the name of the PapyrusDiagram defined in the architecture (currently the key, hopfully will be changed for an id field) Change-Id: I7a4163874bbb94f92bd76043d956ee8e79b4a6bb
2017-03-13Bug 510451 - Reimplement the ISO42010 specification to properly supportMaged Elaasar1-0/+70
architectural contexts and viewpoints Replaced the viewpoint configuration framework by a new architectural context/viewpoint framework. This involves defining architecture contexts and viewpoints in models and contributing them via extension points or via the preferences. Models reference an architecture context and a set of viewpoints at creation time, but can be switched later. Architecture contexts double as client contexts for which elementtypesetconfigurations can be registered. They also define viewpoints, which reference representation kinds (diagrams or tables). This contribution defines three architecture contexts: UML, Profile, and SysML corresponding to what Papyrus used to call diagram categories. Change-Id: I203b58d9e97afdffc45c2674683c0281eb8a7c5b Signed-off-by: Maged Elaasar <>

    Back to the top