frameplot 0.5.5__tar.gz → 0.5.7__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (27) hide show
  1. {frameplot-0.5.5/src/frameplot.egg-info → frameplot-0.5.7}/PKG-INFO +8 -1
  2. {frameplot-0.5.5 → frameplot-0.5.7}/README.md +7 -0
  3. {frameplot-0.5.5 → frameplot-0.5.7}/pyproject.toml +1 -1
  4. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/api.py +6 -2
  5. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/layout/route.py +578 -275
  6. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/layout/text.py +14 -8
  7. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/model.py +8 -5
  8. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/render/svg.py +93 -23
  9. {frameplot-0.5.5 → frameplot-0.5.7/src/frameplot.egg-info}/PKG-INFO +8 -1
  10. {frameplot-0.5.5 → frameplot-0.5.7}/tests/test_rendering.py +117 -0
  11. {frameplot-0.5.5 → frameplot-0.5.7}/LICENSE +0 -0
  12. {frameplot-0.5.5 → frameplot-0.5.7}/setup.cfg +0 -0
  13. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/__init__.py +0 -0
  14. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/layout/__init__.py +0 -0
  15. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/layout/order.py +0 -0
  16. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/layout/place.py +0 -0
  17. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/layout/rank.py +0 -0
  18. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/layout/scc.py +0 -0
  19. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/layout/types.py +0 -0
  20. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/layout/validate.py +0 -0
  21. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/render/__init__.py +0 -0
  22. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/render/png.py +0 -0
  23. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot/theme.py +0 -0
  24. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot.egg-info/SOURCES.txt +0 -0
  25. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot.egg-info/dependency_links.txt +0 -0
  26. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot.egg-info/requires.txt +0 -0
  27. {frameplot-0.5.5 → frameplot-0.5.7}/src/frameplot.egg-info/top_level.txt +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: frameplot
3
- Version: 0.5.5
3
+ Version: 0.5.7
4
4
  Summary: Turn Python-defined pipeline graphs into presentation-ready SVG and PNG diagrams.
5
5
  Author: Small Turtle 2
6
6
  License-Expression: MIT
@@ -147,6 +147,12 @@ Top-level imports are the supported public API:
147
147
  - `to_png_bytes(scale=4.0) -> bytes`
148
148
  - `save_png(path, scale=4.0) -> None`
149
149
 
150
+ ## Modeling Guidance
151
+
152
+ - Keep the main graph at one abstraction level. Frameplot lays the pipeline out as a dependency-driven left-to-right graph, not as a freeform block diagram.
153
+ - Use `DetailPanel` for repeated block internals or per-stage mechanics that would otherwise create long-range edges in the main graph.
154
+ - Use `Group` to highlight nearby related nodes, not to force distant nodes to stay together. Groups are visual overlays and routing obstacles, so very wide groups can increase route detours.
155
+
150
156
  ## Advanced Example: Multi-cloud Data Pipeline
151
157
 
152
158
  The hero image at the top and the theme gallery above are generated from [`examples/theme_heroes.py`](https://github.com/smturtle2/frameplot/blob/main/examples/theme_heroes.py), using the shared pipeline definition in [`examples/hero_pipeline.py`](https://github.com/smturtle2/frameplot/blob/main/examples/hero_pipeline.py). Together they showcase:
@@ -161,6 +167,7 @@ The hero image at the top and the theme gallery above are generated from [`examp
161
167
  - Edge labels are not supported yet, but edge-to-edge joins can render optional `+` / `x` badges.
162
168
  - Groups stay visual overlays, and routes leaving or re-entering grouped nodes bend outside grouped areas.
163
169
  - Detail panels render as separate lower insets attached to a focus node in the main flow.
170
+ - If a sample looks stretched or routes far outside the intended block, the graph usually mixes stage-level flow with internal logic in one plane; move the internals into a `DetailPanel`.
164
171
 
165
172
  ## Development
166
173
 
@@ -118,6 +118,12 @@ Top-level imports are the supported public API:
118
118
  - `to_png_bytes(scale=4.0) -> bytes`
119
119
  - `save_png(path, scale=4.0) -> None`
120
120
 
121
+ ## Modeling Guidance
122
+
123
+ - Keep the main graph at one abstraction level. Frameplot lays the pipeline out as a dependency-driven left-to-right graph, not as a freeform block diagram.
124
+ - Use `DetailPanel` for repeated block internals or per-stage mechanics that would otherwise create long-range edges in the main graph.
125
+ - Use `Group` to highlight nearby related nodes, not to force distant nodes to stay together. Groups are visual overlays and routing obstacles, so very wide groups can increase route detours.
126
+
121
127
  ## Advanced Example: Multi-cloud Data Pipeline
122
128
 
123
129
  The hero image at the top and the theme gallery above are generated from [`examples/theme_heroes.py`](https://github.com/smturtle2/frameplot/blob/main/examples/theme_heroes.py), using the shared pipeline definition in [`examples/hero_pipeline.py`](https://github.com/smturtle2/frameplot/blob/main/examples/hero_pipeline.py). Together they showcase:
@@ -132,6 +138,7 @@ The hero image at the top and the theme gallery above are generated from [`examp
132
138
  - Edge labels are not supported yet, but edge-to-edge joins can render optional `+` / `x` badges.
133
139
  - Groups stay visual overlays, and routes leaving or re-entering grouped nodes bend outside grouped areas.
134
140
  - Detail panels render as separate lower insets attached to a focus node in the main flow.
141
+ - If a sample looks stretched or routes far outside the intended block, the graph usually mixes stage-level flow with internal logic in one plane; move the internals into a `DetailPanel`.
135
142
 
136
143
  ## Development
137
144
 
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "frameplot"
7
- version = "0.5.5"
7
+ version = "0.5.7"
8
8
  description = "Turn Python-defined pipeline graphs into presentation-ready SVG and PNG diagrams."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.11"
@@ -19,8 +19,12 @@ class Pipeline:
19
19
  """Describe and render a pipeline diagram.
20
20
 
21
21
  The constructor accepts any iterable of nodes, edges, and groups, then
22
- normalizes them to tuples for deterministic rendering. Passing `theme=None`
23
- uses the default :class:`Theme`.
22
+ normalizes them to tuples for deterministic rendering. The main graph uses
23
+ dependency-driven left-to-right auto-layout, so it works best when kept to
24
+ one abstraction level. If stage flow and internal mechanics are mixed into
25
+ the same graph, ranks can stretch and routes can become unexpectedly long;
26
+ move those internals into a :class:`DetailPanel` instead. Passing
27
+ `theme=None` uses the default :class:`Theme`.
24
28
  """
25
29
 
26
30
  nodes: tuple[Node, ...]