You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been doing lots and lots of diagrams and I struggled with something...
When you define your objects, there's no way to keep them invisible and use them later... I came across an idea of creating a section of resources; just like D2 classes but those "resources" could be based on classes too.
To help you understand the idea better, I share you a link to a diagraming tool that a friend of mine found. This tool has a resources section (coincidently LOL).
If you can implement that "resources" behavior, D2 will be strong enough to have no competitors, I have all the faith in your efforts; I wish I had the time to spare helping you coding it.
Imagine if the next scenario could be possible:
FILE: styles.d2
classes: {
dog: {
shape: circle
}
male: {
style.fill: brown
style.fill: brown
style.font-color:white
}
female: {
style.fill: orange
}
}
Hey Alixander!
I've been doing lots and lots of diagrams and I struggled with something...
When you define your objects, there's no way to keep them invisible and use them later... I came across an idea of creating a section of resources; just like D2 classes but those "resources" could be based on classes too.
To help you understand the idea better, I share you a link to a diagraming tool that a friend of mine found. This tool has a resources section (coincidently LOL).
If you can implement that "resources" behavior, D2 will be strong enough to have no competitors, I have all the faith in your efforts; I wish I had the time to spare helping you coding it.
Imagine if the next scenario could be possible:
FILE: styles.d2
FILE: dogs.d2
FILE: houses.d2
FILE: diagram.d2
The previous example should compile into something like this:
It really improves the readability of what really matters: the relations, ¿Don't you think?
¿What do you say, can you implement it sometime in the future?
The text was updated successfully, but these errors were encountered: