←back to thread

Show HN: Graphite, a Blender-inspired 2D procedural design Rust app

(graphite.rs)
783 points Keavon | 1 comments | 15 Oct 24 22:32 UTC | HN request time: 0.206s | source

For the past three years I've been building what I hope will be the next Blender, tackling the lack of any good 2D design or image editing tools outside the Adobe monopoly. This was our first year participating in Google Summer of Code and this Q3 update includes the big payoff from that, covering the most progress we've made so far as a project. If you're a Rust dev, consider getting involved as we apply for the next GSoC in the new year— you could be our intern next summer :)

Q3 progress report: https://graphite.rs/blog/graphite-progress-report-q3-2024/

Show context
fwip ◴[16 Oct 24 15:28 UTC] No.41860222[source]▶
Very cool! One comment, one question. 1) panning the node graph of the leaves demo seemed slow / laggy on my macbook pro in chrome, which gave an initial low-quality feeling - moving nodes was nice and responsive.

2) Given that this is written in Rust (compiled), is it on the roadmap to 'export' the parameterized designs into some callable library code? e.g: a game engine that calls "leaves = generate_texture("changing_leaves.graphite", percentage=0.2)"? It would be cool to keep that configurability even once you leave the editor - basically, splitting the node-graph renderer out as its own library that you can call programmatically.

replies(1): >>41862373 #
Keavon ◴[16 Oct 24 18:46 UTC] No.41862373[source]▶
1. Please see https://news.ycombinator.com/item?id=41854076 2. Yes, you got it! That's very much something we are building towards, and you hit it on the nail in describing how that will work and the utility it will provide to people across many industries from game dev to backend services.
replies(1): >>41863830 #
1. fwip ◴[16 Oct 24 21:02 UTC] No.41863830[source]▶
Awesome! Composable tools rule.