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
ok no, I'll do svg for first (clickable links :)), and png for second
local image is now first class
it's maybe even only/main?
like, end-user API becomes just the one func, depgraph.
Why still use an online one, if dot is now bundled.
it's fun for live-playing w/ dot styling etc; but not so useful for end users I think
So: yes:
ah, hm, ok. Web is still useful for SVG zoom-and-pan (as written before here somewhere..)
otoh, we're veering more towards png again (which are also locally very zoom-and-pannable)
The text was updated successfully, but these errors were encountered:
(so do that first, and give the
depgraph_web
and url as an alternative below)for darkmode, can use png's, as in
-Tsvg:cairo
) #103 (comment)ok no, I'll do svg for first (clickable links :)), and png for second
it's maybe even only/main?
like, end-user API becomes just the one func,
depgraph
.Why still use an online one, if dot is now bundled.
it's fun for live-playing w/ dot styling etc; but not so useful for end users I think
So: yes:
depgraph_image
→depgraph
(only end user func). Relegate _web to internals/advanced/tools/.. #105ah, hm, ok. Web is still useful for SVG zoom-and-pan (as written before here somewhere..)
otoh, we're veering more towards png again (which are also locally very zoom-and-pannable)
The text was updated successfully, but these errors were encountered: