Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to create a package #1954

Closed
sz332 opened this issue Dec 25, 2022 · 10 comments
Closed

Ability to create a package #1954

sz332 opened this issue Dec 25, 2022 · 10 comments
Milestone

Comments

@sz332
Copy link
Contributor

sz332 commented Dec 25, 2022

Is your feature request related to a problem?

Add ability to create a package without creating any kind of diagram

Describe the solution you'd like

I would like to be able to add packages without creating diagrams.

Describe alternatives you've considered

Additional context

@amolenaar
Copy link
Member

This is possible by right-clicking on any package. Only it's not possible to create a top level package directly. You'll have to drag it.

@danyeaw
Copy link
Member

danyeaw commented Dec 25, 2022

Maybe we should allow it from the top level project?

@sz332
Copy link
Contributor Author

sz332 commented Dec 25, 2022

As a user that would be the most intuitive action for me. I honestly never thought about dragging the package to whatever.

@danyeaw
Copy link
Member

danyeaw commented Dec 26, 2022

@sz332 I just tested this with 2.14.0, if I right-click on the top level package, I am able to create a Package directly.
image

@danyeaw
Copy link
Member

danyeaw commented Dec 26, 2022

I get it after reading #1952, you are deleting the top level model package, and now you don't have a way to create a new one. Other tools actual call this top level package a Model, put a triangle in the package symbol, and I don't think it can be deleted. I don't think that is specified in the OMG specs, but what if we did something similar?

@amolenaar
Copy link
Member

I think it's perfectly fine to have multiple top-level packages.

One option is to create a popup menu when not over any elements.
Another is to generalize the "New diagram" button in the header bar, as discussed in #1927, and allow for a Create toplevel package entry.

@sz332
Copy link
Contributor Author

sz332 commented Dec 27, 2022

From user point of view the best way to handle this would be definitely to have a top level/root element with a custom icon showing that this represents the model which simply cannot be deleted. The advantage of this concept is that it opens the door to have multi-model solution later, when in a single project you can import multiple models (some of them as read only). It is extremely useful when working on smaller project but when you created reusable UML Profiles (for example for conceptual modeling, REST, etc.).

@amolenaar
Copy link
Member

I added a popup menu for the empty space of the model browser. It fixes the problem of not being able to create top level packages without having to put them in a diagram. I'm considering adding a "New Package" in the diagrams popup in the header (which then should change it's icon). Not sure if we really need it, though.

Quite some work has to be done before we can support multiple models in one window. Especially if some of them need to be read-only. I think it would be more natural to introduce this concept when we can actually support multiple models.

@danyeaw
Copy link
Member

danyeaw commented Jan 14, 2023

@sz332 Thanks again for submitting this issue! Are you happy with us closing this with #1995 merged?

@sz332
Copy link
Contributor Author

sz332 commented Jan 14, 2023

Sure, thank you!

@amolenaar amolenaar added this to the 2.16 milestone Jan 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants