-
Notifications
You must be signed in to change notification settings - Fork 15
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
Styles configuration #18
Comments
In current implementation, customization of font is a requirement, as monospaced font is required for proper rendering of tables in nodes. From what I remember, filling nodes with color doesn't look good in nodes with rounded corners, which we use. |
What I would like to have is better styles to differentiate between selected nodes in that extension. Take a look at this image from the extension page: I don't like those styles particularly, but they do a good job in highlighting the selected nodes. As that extension lets you click on a node or search for it to highlight it, it really helps in understanding the diagram. I think that it would be enough being able to define the background color, border thickness and font weight, both for the selected / unselected states. |
I tried this plugin, it is very interesting. However, selected/unselected states are solely plugin terms. We can add configuration for "unselected" states, but it doesn't mean that this improves readability, as colors for "selected" state are defined by the plugin. |
That's something we could use then, if at least we can configure the base style, we can then play with the plugin to produce a better contrast between "unselected" and "selected". Configuring the base style would be interesting also to define a general look, even when we don't use this kind of plugins. |
I'm using the Graphviz Interactive Preview VS Code extension to visualize DOT files.
It would be great to be able to configure the styles for the generated diagrams, in terms of colors, border thickness, etc. By now I think it's only possible to change the font.
The text was updated successfully, but these errors were encountered: