search

bmaggi / library-training

:mortar_board: :books: The Library Training Material (Incoming Eclipse Papyrus Photon Year 2018-2019)
Eclipse Public License 1.0
12 stars 5 forks source link

The "new Relationship" menu remains hidden in UML architecture context #29

Closed vlimmerm closed 6 years ago

vlimmerm commented 6 years ago

Hello Benoit,

you hide the "new Relationship" menu in the /org.eclipse.papyrus.training.library.newchild activator. But this menu remains hidden when one creates a UML project.

I wonder why the visibility / availabilty of a new child menu is not linked to the architecture context, in analogy with the palette?

Kind regards,

Marc

bmaggi commented 6 years ago

Hi,

1) The code in HideNewChildEdgeUtil is a trick to hide the UML menu when creating an Enterprise Product. You may also hide the menus using the preferences, some people also used home made code to switch these preferences when changing viewpoints but nothing is currently integrated in Papyrus core.

2) Mostly for historic reason, most framework were created before the architecture one. Ideally, everything should be done using the architecture model, that's the golden goal but for the moment most of the frameworks work quite independently.

=> Goal : New Child, Drop, Palette, css, assistant... should all be ruled by the architecture model

/Benoit

vlimmerm commented 6 years ago

OK Benoit,

Thanks for the info.

Kind regards,

Marc

Marc Van Vlimmeren Research engineer Flanders Make vzw Oude Diestersebaan 133 B-3920 Lommel

Tel.: +32 11 79 05 77 Mobile: +32 491 61 18 27 www.flandersmake.behttp://www.flandersmake.be/ Volg ons op LinkedInhttps://www.linkedin.com/company/9277885

From: Benoit Maggi [mailto:notifications@github.com] Sent: dinsdag 9 januari 2018 14:45 To: bmaggi/library-training library-training@noreply.github.com Cc: Marc Van Vlimmeren marc.vanvlimmeren@flandersmake.be; Author author@noreply.github.com Subject: Re: [bmaggi/library-training] The "new Relationship" menu remains hidden in UML architecture context (#29)

Hi,

  1. The code in HideNewChildEdgeUtilhttps://github.com/bmaggi/library-training/blob/master/org.eclipse.papyrus.training.library.newchild/src/org/eclipse/papyrus/training/library/newchild/internal/HideNewChildEdgeUtil.java is a trick to hide the UML menu when creating an Enterprise Product. You may also hide the menus using the preferences, some people also used home made code to switch these preferences when changing viewpoints but nothing is currently integrated in Papyrus core.
  2. Mostly for historic reason, most framework were created before the architecture one. Ideally, everything should be done using the architecture model, that's the golden goal but for the moment most of the frameworks work quite independently.

=> Goal : New Child, Drop, Palette, css, assistant... should all be ruled by the architecture model

/Benoit

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/bmaggi/library-training/issues/29#issuecomment-356287567, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AekexiwGK2EROMJrC07pnd4dDIGaspfkks5tI21UgaJpZM4RX0Ik.