8=======D

Generate class diagram and Dependency diagram from existing project.

The Classes most have its constructors visible to recieve parameters or what else.

When we are designing a system, is common we change our mind about use an interface or class. Models is just a draft until they generate code.

Would be nice be able to change an element originally create as interface to class and vice-versa.

I need this feature

Let us select "Word Wrap" as default option for new diagrams. I use it a lot.

It is also, be awesome, if you let us create our own color palettes to define own styling for diagram elements. Default colours are not sufficient in every case.

On activity diagrams, object flow and control flow are indistinguishable. And I sometimes use line style as another kind of visible "stereotype".

Why not allow to set line style for all types of connections?

any shape supporting links to other shapes such as classes, components, etc... on a diagram should offer a "Add related shapes" context menu option to add all related shapes to the diagram.

Additionally it would be nice if the user could specify the number of transitive dependency layers being considered.

License validation is a tricky thing, the last thing you want is users figuring out a way of getting your software for free.

You might not be aware of the following gist which proposes a very simple way of "cracking" the validation system : https://gist.github.com/trandaison/40b1d83618ae8e3d2da59df8c395093a

This mainly uses the fact that a local javascript file is used to validate the license : which is really not a good idea.

My request would be to switch from the usual LicenseManagerDomain.js to another validation system (maybe something in Delphi, or an external compiled program).

ERD, Entities rows are fixed, it is better to add extra row to the entity.

add sub numbers for messages or hide numbers

On OSX File-> Close should be bound to Cmd-W

As an example, it would be useful to be able to navigate by click or double click on the element referenced as the value of source or target within a use case. This should apply, overall, to all properties that reference other elements.

The "one and only one" and "one or many" notation symbols are not quite correct.

https://www.codeproject.com/Articles/878359/Data-modelling-using-ERD-with-Crow-Foot-Notation

I know the main concept of this great tool is support UML for engineer work (mostly in the backend). But, have you ever think in give also a little bit of support for UI/UX prototyping? It don't need to have a complete palete of component, but just the basics. Freelance coder sometimes have to model this for their clients, and having the chance for doing this from the same tool they use for another models, would be great.

I'd like to create simple markdown documents in the project in order to describe how the application works or how consistance issues are solved.

Documents should be exported as pages in html docs.

Please for god's sake, HTTPS certificates are free now (LetsEncrypt) and takes 5min to configure ...