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

Post by deskr » Thu, Oct 17, 2024, 3:55 PM UTC

Keavon wrote: post #117

deskr wrote: post #81

Some suggestions: I was doing something and then suddently I got a red error message, "The document cannot be rendered in it current state", instructing me to click the Node Graph button. 1. I couldn't find that button. Perhaps show a picture of it or just embed it in the error message. 2. Make the error text selectable. 3. Let me report the bug straight from the app?

Thanks for the feedback. What you've encountered is a type error— basically a programming language's compiler telling you that your code is invalid. It's not a bug per-se, although sometimes it is caused by our nodes not being as general as they should be. We just fixed an issue where the Stroke and Fill nodes only applied to vector data but didn't apply to group data (where the group contained one or more vector dat…

Post by adastra22 » Thu, Oct 17, 2024, 6:39 PM UTC

airstrike wrote: post #92

Keavon wrote: post #37

Earlier quoted context omitted.

It was a top contender when I was picking a GUI solution but it didn't meet the cut. Remember that this was 3.5 years ago. The decision to go with HTML/CSS was undoubtedly the right one and it'll continue to treat us well for the foreseeable future. But we are beginning to rewrite certain areas, like the node graph, in our own render stack because this streamlines the code best. And other widgets like histograms, col…

It's your app, so obviously do whatever you want, but I agree with the sibling comment that an immediate mode GUI wastes valuable CPU cycles redrawing the frame repeatedly and will invariably hurt performance Again, since iced is "just rust", you can write whatever widgets you need, although it comes with a long list of built-in widgets (and there are many more built by the community). You can compose views with a bu…

Post by Keavon » Thu, Oct 17, 2024, 7:56 PM UTC

deskr wrote: post #122

Keavon wrote: post #117

Earlier quoted context omitted.

Thanks for the feedback. What you've encountered is a type error— basically a programming language's compiler telling you that your code is invalid. It's not a bug per-se, although sometimes it is caused by our nodes not being as general as they should be. We just fixed an issue where the Stroke and Fill nodes only applied to vector data but didn't apply to group data (where the group contained one or more vector dat…

I'd suggest allowing bug reports directly from the app. You can capture highly useful context with the report. You have highly technical people here eager to help your wonderful creation!

Post by deskr » Thu, Oct 17, 2024, 10:43 PM UTC

Keavon wrote: post #125

deskr wrote: post #122

Earlier quoted context omitted.

I'd suggest allowing bug reports directly from the app. You can capture highly useful context with the report. You have highly technical people here eager to help your wonderful creation!

We have this for crash reports. Perhaps that's a good idea to add a menu button for reporting other bugs. Do you have suggestions as to how to make that discoverable?

Post by joelignaatius » Fri, Oct 18, 2024, 3:43 AM UTC

Keavon wrote: post #105

bethemoly wrote: post #75

This sounds like a big project—congrats on releasing it! Just curious, as a business other than a hobby, do you have enough resources to see it through?

Everything we do is bootstrapped through donations and volunteer development time. When our main other core contributor graduates in a year, we'll need the funds to hire him, so we will be pushing that donation angle more in the coming year as well as applying for grants. I personally would like to be paid eventually, but I'm well-equipped to keep at this for a while before finances become a problem in my life. I can…