Summary: | [Tooling] Filtering only applicable to UML-RT is confusingly done also on standard new child menu | ||
---|---|---|---|
Product: | [Modeling] Papyrus-rt | Reporter: | Peter Cigehn <peter.cigehn> |
Component: | tool | Assignee: | Project Inbox <papyrusrt-inbox> |
Status: | UNCONFIRMED --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | charles, papyrus-bugs, rschnekenburger |
Version: | 0.7.2 | Keywords: | ui |
Target Milestone: | Future | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=469677 | ||
Whiteboard: |
Description
Peter Cigehn
2016-03-31 09:41:16 EDT
I am not fully sure I agree with moving this to Target Milestone "Future". The use of UML-RT for building DSMLs on-top of Papyrus-RT, i.e. the target audience identified already for MVP1, i.e. the 0.8 release, could also be impacted by this issue. I would really like someone to take a look at this, at lest before 1.0, since I am afraid it also could impact what kind of customizations that DSML tool-smiths are able to do and not. Is this something that (implicitly) will be fixed by the new architecture and view point framework in Oxygen? RĂ©mi, from what you have seen so far when looking at this, do you think that this potentially will be "fixed by itself" when we migrate to Oxygen? Or do we still need to ensure that this does not happen by explicit changes on the Papyrus-RT side? |