|Re: [mdt-papyrus.dev] Feedbacks about architecture framework|
In addition to previous feedback I’d like the architecture model editor to have:
· tooltips on fields that explain what the fields is needed to
· when the field is a reference (example : elementtype set) : to have a reference editor that allows reference to workspace resources
Développing the matrix framework, I fill these 2 bugs on AF :
516586: [AFViewpoints][Matrix] Architecture Framework should provide more informations
517986: [SysML 1.1][SysML 1.4][UML][AFViewpoints] declared architecture model should use a common pattern for naming
The last one is maybe fixed now.
Hi all committers and advanced users of papyrus,
For the oxygen version, the architecture framework has been developed and used.
I would like to know your feedbacks about this framework, to include , if needed, improvements in the road map of photon.
You can write that it is nice, why, we appreciate this kind of remarks.
You can also write remarks about:
- Needs improvements about developer points of view:
o Configuration about .architecture
o How to define something that you have difficulties to do.
o Maybe problems of performance that you have detected.
- Needs improvements about user points of view:
o Some behaviors that you have not understand…
Responses need to be clearly and precise in order to be managed.
Back to the top