Hi, Asma,
We will need the xtUML-RT team to rename their preference node from “Umlrt” to something more descriptive of its pertaining to the xtUML-RT text editors and then move it under the new top-level page. I’m not sure how to do that, so I would raise an enhancement request for that in bugzilla once the new top-level preference page is in place.
On 2 June, 2016 at 09:24:14, SMAOUI Asma (asma.smaoui@xxxxxx) wrote:
Do we will end up with 2 different preference pages for UML RT ?
One named “UMLrt” and another “UML Real-Time”
To access the preference pages, users usually use completion to directly get the page, they can be disturbed if they find
2 matched pages when they enter umlrt
Otherwise +1
Asma
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Peter Cigéhn
Envoyé : jeudi 2 juin 2016 15:11
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] UML Real-Time preference pages
The only thing I can comment on is the name "UML Real-Time". I am not fully sure that we came to any conclusion in the Bugzilla that I wrote related to aligning terminology:
I am not sure if really should be spelled with a - "UML Real-Time", or combined "UML RealTime", or with space "UML Real Time". I could so far see all kinds being used. I think that this would
be a good opportunity to try to settle the terminology being used. Charles indicated (implicitly) though that it should be "UML Real Time" in the response he gave on that Bugzilla.
Can we please settle this, and document the decision on that Bugzilla?
On 2 June 2016 at 15:08, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
+1
Great idea! Setting up right now the preferences contributions would be great, as for the discussion about labels convention.
-------------------------------------------------------
I observe that, so far, Papyrus-RT contributes no preference pages apart from those that are generated by Xtext for the xtUML-RT language (labeled as “Umlrt" [sic] in the
preference dialog).
I have a need for addition of a new preference page, so I would like to discuss the presentation. In the refactoring of a simple state into a composite state, I want to
prompt the user for confirmation on double-clicking a state, with the usual “don’t ask again” check box. To that end, a preference will be needed to restore the prompting.
I propose a new preference page hierarchy as follows:
- UML Real-Time <— top-level page for all Papyrus-RT preference pages
For now, the top “UML Real-Time” preference page would have only the dialog settings button as in JDT:
except, of course, titled “UML Real-Time dialogs”. There would be a new API in which each dialog’s preference key is registered to be managed by this Clear button.
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
