-
Notifications
You must be signed in to change notification settings - Fork 50
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
Implement UML Packages ( C # namespaces & Java packages ) #6
Comments
Hi, I'm not sure that I understand the second part, but opening an issue here and working on your fork is the way to go. What exactly did you read, can you drop me a link? |
I actually didn't know about github task lists, thanks for the info :) |
I think I'm gonna setup a slack workspace, where we can discuss such things. |
So, I've setup a slack workspace, if you drop me an email, I will invite you. |
"Slack channel", never used it, we may try it. Regarding current issue: |
Due to email hunters i'm making it a bit harder to read: |
Thank you, I've sent you invite and removed your email. |
Hello, |
Hi, Best regards :) |
Hello, I'm terribly sorry about not giving any sign of life. It may require some major refactoring before implementing package graphical nesting. Cheers! |
Hello @mrpetro , Regards |
Hi @gbaychev , |
Hi @gbaychev As you may noticed, i've created a pull request. Here are same notes from pull request for tracking:
|
So, @mrpetro , I've downloaded the PR, that you submitted and did some work on it. Currently it looks like this: It is more or less functioning, but it is kinda difficult to get the element drawing/selection order correct, so sometimes dragging shapes gets kinda funky. What also needs to be done is:
I also intend to replace the package icon with something more passing to the other icons. The project uses the visual studio 2013 image library, which I find more aesthetically pleasing then the flat madness of vs2015+, but it is screwing me over, because it is difficult to find icons/images. There will also be some color adjustments of the package shape. All in all - great work, @mrpetro, thank you very much for this PR! I'm going to need this functionality for other types of diagrams. Currently I have about 4 hours per week to work on the project, so maybe this feature is going to be ready next week. |
Hi @gbaychev, Fingers crossed for finishing bringing this feature to full complete. In this month I'll try to focus on issue #7 .It's causing lots of problems. |
Hi @mrpetro, I've updated my post above with the list of the work left. See ya around. |
So, guys and gals, this is done and if you want to check it out, you can download the v2.6.0-pre release. Currently, if you use the Visual Studio (ClearType) style, it looks like this: |
Oh, and by the way, the copy and paste was completely broken, it is fixed now. |
Hey @gbaychev , |
Hello @vishwas-trivedi , Regards |
Hi @gbaychev, Thank you for accepting my suggestion earlier! 1). I'm unable to open old projects on the pre-release version. Following error is displayed : 2). NClass icon in taskbar is not visible, white/empty icon is displayed. Regards |
Hello @vishwas-trivedi ,
And maybe open a new issue with you problem, so other users can see it too, if they have a problem Regards |
Feature request:
UML standard allows to create Packages in diagrams.
One package element can have member elements with various types (classes, interfaces and even other packages). Package can also have nested types and other packages
C # stereotype in UML is namespace
Java stereotype in UML is package
Few things have to be done here in order to implement this feature:
BTW: you can assign it to me because this work is near finished.
I've tried to use Project and issues creation on my Fork but turns out that the issue numbers are counted from hash1 which creates problems with history of issues. So I've decided to create an issue in main branch. Also I've read about different levels of access to branch features, So I could do more, like start projects on main branch instead of my fork. This is something to consider. And I'm sorry about writing this in an issue but I couldn't find any other way to contact repository owner.
The text was updated successfully, but these errors were encountered: