@Nils said in Artboard roles:
So, for example, in the acyclic graph, a fill could be the leaf of an object node, right? And if this object then has another "fill style" leaf, that fill leaf gets redirected towards every other object that uses the fill style.
Something along these lines correct ( fill style implementation could be different I guess? )?
Yes, fill / stroke nodes can be shared in multiple branches. But the real value comes when sharing whole groups of objects.
I see, this reminds me a lot Flutter's tree structure with configuration and render trees. Did you draw some inspiration there? If yes, nice work!
Not inspired by, but I'm sure others have done something like this. It is quite common when an "abstract" model is slow to process, to have a parallel "realized / compiled" model.
The basis for the VS document model was coded in 2013 (i just checked Flutter is started in 2015).
Couldn't you just insert a locked rectangle in the tree upon artboard creation, which you'd then prevent from showing up in the layers panel?
Would not really help and would create a lot of problems with Layers.