[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] About deactivation of viewpoinst inside Papyrus

Dear all,

 

One quick comment : if something is gray (i.e., visible but not usable/accessible in a particular context), users will want to know why it is âgrayâ and then not accessible otherwise (s)he will think it is a bug and not a featureâ ;-)

 

SÃb.

 

 

 

cid:image001.png@xxxxxxxxxxxxxxxxx

 

 

SÃbastien GÃrard

R&D Program Leader of the Knowledge Engineering Platform of the Department

CEA Research Director

Papyrus project Leader (www.eclipse.org/papyrus)

cid:image002.jpg@xxxxxxxxxxxxxxxxx

Commissariat à lâÃnergie atomique et aux Ãnergies alternatives

Institut List | CEA Saclay Nano-INNOV | BÃt. 862- PC174

F-91191 Gif-sur-Yvette Cedex

M. +33 6 88 20 00 47

T. +33 1 69 08 58 24

sebastien.gerard@xxxxxx  www-list.cea.fr

 

 

 

icone_youtube

  cid:image004.png@xxxxxxxxxxxxxxxxx  cid:image005.jpg@xxxxxxxxxxxxxxxxx   

 

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx <mdt-papyrus.dev-bounces@xxxxxxxxxxx> De la part de melaasar@xxxxxxxxx
Envoyà: mercredi 28 aoÃt 2019 17:31
à: Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] About deactivation of viewpoinst inside Papyrus

 

A couple of questions:

 

1. Wouldn't showing representations that are not in the active viewpoint grayed (points 1-3) still clutter the UI? How about hiding them?

2. If the representations that are not in the current viewpoint are grayed (or hidden), how would the user express "want to open" them such that Papyrus proposes to switch the viewpoint (point 5)? If they belong to multiple viewpoints, will Papyrus propose all relevant ones to switch to?

 

Maged

 

On Wed, Aug 28, 2019 at 3:05 AM TESSIER Patrick <Patrick.TESSIER@xxxxxx> wrote:

Hi everyones,

 

We noticed inconsistencies when deactivating a viewpoint in a given context. Activation is not a problem.

We propose the specification of the behavior of a deactivation of a viewpoint for the next release of papyrus.

 

Warning, this is not a specification of a context switch inside architecture framework. It is much more complex and impacting and need also to be specified.

If you have comments, they are welcome.

 

Viewpoint deactivation

1.       Invariant

         Language

o    Profiles are applied

o    ElementTypes are active

o    Graphical element types are active

o    New child

2.      Difference

         List of  possible tables/diagrams are not the same

3.      Which behavior

         Diagrams, Tables that are not listed in active viewpoint shall be visible in ModelExplorer with grayed icon.

         Diagrams, Tables that are not listed in active viewpoint shall be visible in WelcomePage with grayed icon.

         Diagrams, Tables that are not listed in active viewpoint shall be visible Hyperlink (and table of diagrams) with grayed icon .

         Model user shall not be able to open the Diagrams, Tables that are not listed in active viewpoint.

         When Model user want to open Diagrams, Tables that are not listed in active viewpoint,  papyrus shall propose to the model user to  activate the viewpoint that list wanted diagrams or tables.

         When the model user deactivates a viewpoint, papyrus shall close diagrams /table corresponding to this deactivated viewpoint  

         When the model user deactivates a viewpoint, papyrus shall refresh Menu new diagram/table corresponding to this activate viewpoint

 

Papyrus Team

 

 

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/mdt-papyrus.dev

PNG image

JPEG image

PNG image

PNG image

JPEG image