EA16 - browser showing diagram elements under {} package

[Dave_Bullet]

hello.

I've recently upgraded to EA 16.0 and now notes, boundaries and other diagram only elements are being packaged under a > ... {} "pseudo element" in the browser.

Is there a way to revert the browser to < 16.0 functionality, where the notes and other frippery are shown in-line in the same package as the diagram that contains them?

I've tried themes and going through the other smattering of options, settings, preferences, visual style but to no avail. thanks!

[Eve]

Is there a way to revert the browser to < 16.0 functionality, where the notes and other frippery are shown in-line in the same package as the diagram that contains them?

Reverting to the < 16.0 behavior would be not showing them at all. There is no option to hide them, let alone use behavior that has never existed.

The problem is, when responding to user requests to show them in the browser we found it completely untenable to have them directly in the package. It clearly detracted from the usefulness of the browser for all users, even those that never requested it. Collecting them into a single node for each parent is a relatively effective compromise between the two options that we had.

[Dave_Bullet]

Thanks - it was my mistake thinking they were shown at all.

In anycase, having an option in the preferences (show / not show) would have been the solution for both user groups.

[Guillaume]

As discussed on a previous thread, +1 on having an option to enable/disable this feature, which I find useful for a number of users.

[Dave_Bullet]

I've added a feature request as per:
https://sparxsystems.com/forums/smf/index.php/topic,47319.0.html

[Rich Anderson]

Big +1 for this feature requests.  This pseudo folder is very much in the way, especially when walking through a model with non EA users over Teams/Zoom, etc, which is something I do all the time.   This should be a hide/show button right on the browser panel.   

[Ian Mitchell]

I agree: useful to have the ability to see these 'other' kinds of thing, and even more so to have the option to hide them, as Rich says, from the novice user. So probably a per-user switch.
Slightly radical idea: how about getting us users engaged with when and how to implement these kinds of features. We might have views which are helpful...

[Paolo F Cantoni]

I agree: useful to have the ability to see these 'other' kinds of things, and even more so to have the option to hide them, as Rich says, from the novice user. So probably a per-user switch.
Slightly radical idea: how about getting us users engaged with when and how to implement these kinds of features? We might have views that are helpful...

(my emphasis)
The BPMN diagram for Sparx product development does not seem to have this participant as a pool; consequently, no messages are sent to or received from it.

Paolo

[Modesto Vega]

The elements under the "{} package" are non-modelling elements, I would not be too surprised if "{} package" is not a package at all. Let's not forget that in the data model packages have a dual personality, they exist both as elements of a package type (in the objects table) and as packages (in the package table, which are really folders).

Since, from a modelling perspective, packages and folders are not and should not be the same thing. My radical proposal is to move them to a folder of their own directly under the root node and call the folder something like non-modelling elements.

 

[Geert Bellekens]

The elements under the "{} package" are non-modelling elements

Why would you say that? I see things like notes and boundaries in there. Why do you call those "non-modelling" elements?

It's just that EA has chosen in the past to hide those elements in the project browser. The fact that they are now visible in the project browser is a good thing in my book.

Geert