Node shape geometry
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- computer-graphics
Research direction
Start by tracing how node shapes are consumed by the SVG renderer and edge-routing logic. Use the Graphviz node-shapes and record-node references to define the geometry, sizing attributes, and record syntax requirements. Done means the requested shape tiers, including recursive record layouts, are supported with path generation and boundary intersections.
Written by the indexing model from the issue text.
Description
Each node shape needs two things: an SVG path generator (given center and size, produce the drawable path) and a boundary intersection function (given an incoming edge angle, compute where it hits the shape perimeter). These are used by the SVG renderer and edge routing respectively.
Shapes should be implemented in tiers. Tier 1 covers the most common shapes: `ellipse` (the default), `box`/`rect`, `circle`, `point`, `plaintext`/`plain`, and `none`. Tier 2 adds polygon-based shapes: `diamond`, `triangle`, `pentagon`, `hexagon`, `octagon`. Tier 3 adds `record` and `Mrecord`, which have their own label sub-language (`{a|{b|c}|d}`) requiring a mini-parser and recursive cell layout algorithm. Tier 4 covers the remaining ~40 Graphviz shapes. The `width`, `height`, and `fixedsize` attributes control shape sizing.
References
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from terror/dotgraph
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
SVG renderingOpenenhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Style resolutionOpenenhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Arrowhead geometryOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Edge routingOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
area:casework bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
registrystack/registry-stack#1623 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
leptos-rs/leptos#4885 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
longbridge/gpui-kit#3276 ·
Maintainers usually reply within 1 day
-
A-Migration Guides D-Straightforward S-Ready-For-Implementation X-Uncontroversial
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bevyengine/bevy-website#2607 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day