Jollywatt
commented
4 months ago Unfortunately, this is because fletcher uses its own coordinate system ("elastic coordinates"), and I simply haven't replicated everything cetz can do with coordinate transformations.
- I could reimplement all of cetz special coordinates (relative, polar, tangent, etc), but I don't want to duplicate all that functionality in a separately maintained package.
- Alternatively, fletcher could integrate more closely with cetz in order to fully support cetz's special coordinates and anchors. However, I don't know how to do that.
The reason fletcher doesn't integrate with cetz more closely is because the order of operations makes it difficult:
- First, the physical dimensions of nodes in a diagram are determined from
measure(). - The nodes' row and column positions (elastic coordinates), combined with their sizes, then determines the diagram's grid layout (the row and column sizes, or how elastic coordinates map to physical positions).
- Then, the physical positions of nodes (and edges) are calculated and these are given to cetz to draw.
In order to fully support cetz coordinates (to enable e.g., node((rel: (1, -1), to: "anchor"), [Hi]) where the (1, -1) are in the diagram's coordinates), cetz needs to know how to fully resolve the coordinates, which means the conversion from elastic to physical coordinates must be defined. However, this coordinate transformation is not known until all the nodes in the diagram are measured and their row/colum positions (elastic coordinates) are known.
I tried (rel:,to:) in cetz, but it seems no dice, why isn't this supported?