Suggestion: Multiple instances of project browser

[Ian Kirwan]

(Possibility of similar or same suggestion already existing accepted. Apologies in advance for duplicate suggestions and existing capabilities that already cover the suggestion.)

Suggest allowing more than one instance of the project browser to make reorganizing models easier. Dragging elements from one part of a model to another, though not impossible, can be tricky. Having 2 instances of browser open would allow the user to see the source and destination on screen(s) simultaneously, reducing the probability of losing the destination package or mistaking with a similarly named package.

[PeterHeintz]

+1

[Uffe]

I'm all for this, but it has been up before and I'm afraid the concept of "the" project browser is pretty fundamental, so it's not likely to change.

/Uffe

[qwerty]

This comes up since many years. And the browser still looks (more or less) like in the beginning.

q.

[Ian Kirwan]

It would be interesting to hear from the developers whether this really is such a difficult functionality to implement. I find it hard to believe personally speaking, especially if the multiple were limited to 2, which is probably all that is required.

[Eve]

If I may, the request here is actually a way to drag elements between packages more easily. Multiple instances of the project browser is a "first thought" of how to achieve this.

The problem with that suggestion isn't creating the extra browser, keeping it in synch or implementing drag and drop. It's with every function in EA that uses project browser selection (and isn't being directly called from the project browser.) Because of that alone an equal with the project browser can't be done. That leaves using secondary views to achieve the same purpose. We already have several.

The Package Browser window is my preferred way. It allows elements to be dragged both to and from the Project Browser to change the package.
The Specification Manager is a similar but different option.
Another option that I don't use often is the Model Views window.

These may need to be more visible, perhaps training would help, or maybe there's some reason why they don't work for you.

[Ian Kirwan]

The Package Browser window is my preferred way. It allows elements to be dragged both to and from the Project Browser to change the package.

This solves the problem as far as I am concerned 

The help could probably do with a section on organisation and maintenance of the model that includes such ideas.

[Barrie Treloar]

If I may, the request here is actually a way to drag elements between packages more easily. Multiple instances of the project browser is a "first thought" of how to achieve this.

[deleted].

We already have several.

The Package Browser window is my preferred way. It allows elements to be dragged both to and from the Project Browser to change the package.
The Specification Manager is a similar but different option.
Another option that I don't use often is the Model Views window.

These may need to be more visible, perhaps training would help, or maybe there's some reason why they don't work for you.

Apologies for necro posting, but this is the most relevant google result.

And I haven't found any detailed instructions on setting this up.

So for future me, here they are:

See the docs at https://sparxsystems.com/enterprise_architect_user_guide/17.1/the_application_desktop/reportview.html

I used the Browser to locate my root package.
Right click on root package > Open Package in > List View
(Dock the Package Browser with the Browser and Inspector)
Right click on the Fields in the Package Browser > Field Chooser >
- Removed all fields but Name
- Added Field Type

In the top right toolbar of the Package Browser clicked on the format icon
- enable Show Nested Package Control
- enable Show Element Hierarchy
- enable Show Filter Bar
- disable Group bar

Now I can scroll through all the AWS elements to locate the one I want.

Or type in the Name field to filter the list

Drag and Drop onto diagrams is now easy!