Skip to content

Curves image adjustment node#1214

Merged
Keavon merged 18 commits into
masterfrom
curves-node
Aug 13, 2023
Merged

Curves image adjustment node#1214
Keavon merged 18 commits into
masterfrom
curves-node

Conversation

@nat-rix

@nat-rix nat-rix commented May 12, 2023

Copy link
Copy Markdown
Contributor

No description provided.

@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) May 14, 2023 16:50 Inactive
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented May 14, 2023

Copy link
Copy Markdown

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 55dd406
Status: ✅  Deploy successful!
Preview URL: https://ae4c9a0b.graphite.pages.dev
Branch Preview URL: https://curves-node.graphite.pages.dev

View logs

@github-actions

github-actions Bot commented May 14, 2023

Copy link
Copy Markdown

Deploy Preview ready!

Name Link
🔨 Latest commit 55dd406
🔍 Latest deploy log https://github.com/GraphiteEditor/Graphite/actions/runs/5034567205
😎 Deploy Preview Url https://ae4c9a0b.graphite.pages.dev
🌳 Environment preview

@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) May 14, 2023 17:06 Inactive
@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) May 14, 2023 23:23 Inactive
@nat-rix

nat-rix commented May 16, 2023

Copy link
Copy Markdown
Contributor Author

@Keavon Dennis said, that you gonna have opinions about the curves widget I've implemented. In my implementation the backend and frontend communicate via a list of curve samples and the frontend composes the resulting svg. At the moment the backend works with cubic splines and the frontend works with bezier (a quick wikipedia look said me they are bijective), but probably it's the best to replace the backend (cubic) spline implementation with bezier-rs. Dennis also showed me https://github.com/GraphiteEditor/Graphite/tree/master/website/other/bezier-rs-demos. I guess I'll leave my frontend code as it is and only steal the neat design from there.

@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) May 19, 2023 20:15 Inactive
@Keavon

Keavon commented May 19, 2023

Copy link
Copy Markdown
Member

Looks like this is taking shape and starting to work now! I'm noticing that it breaks (and throws a console error) after a little while of dragging the points around, at which point the laggy UI stops being laggy (since it's not doing anything anymore from then on).

@nat-rix

nat-rix commented May 19, 2023

Copy link
Copy Markdown
Contributor Author

I'm noticing that it breaks (and throws a console error) after a little while of dragging the points around

Could you please provide an error log? I can't reproduce that.

@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) May 20, 2023 17:18 Inactive
@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) May 20, 2023 19:21 Inactive
@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) May 20, 2023 21:22 Inactive
@Keavon

Keavon commented May 20, 2023

Copy link
Copy Markdown
Member

Could you please provide an error log? I can't reproduce that.

It should definitely just happen by using it for a bit, maybe try and be aggressive and drag it around a lot every frame. I'm using Chrome in case that makes any difference. I'm adding this downstream of the Downscale node for a 4000x3000 image. The only error it prints is this:

image

Note, that is not referring to hitting a Rust unreachable!(); macro, but rather this wasm instruction.

@nat-rix

nat-rix commented May 20, 2023

Copy link
Copy Markdown
Contributor Author

Huh, interesting. This looks like an out of memory error. My first intuition is that this happens, because too many non-completed events stack up in the event queue. But I'll have
a look into this a bit later

@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) May 20, 2023 23:06 Inactive
@TrueDoctor

Copy link
Copy Markdown
Member

I've updated the branch to use the new master, I think it makes sense to merge this pretty soon (even if it is not completely done) to prevent further code rot

@TrueDoctor

Copy link
Copy Markdown
Member

This does acutally work surprisingly well, I can fix the tests and I think we might be good to merge then

@Keavon

Keavon commented Aug 12, 2023

Copy link
Copy Markdown
Member

I built this branch and don't see the Curves node in the layer add menu, do you know what's up with that?

@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) August 12, 2023 10:40 Inactive
@TrueDoctor

Copy link
Copy Markdown
Member

@nat-rix do you know what would most likely be the culprit for the failing tests?

@TrueDoctor

Copy link
Copy Markdown
Member

I built this branch and don't see the Curves node in the layer add menu, do you know what's up with that?

The build link works, can you retry that?

@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) August 13, 2023 00:45 Inactive
@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) August 13, 2023 03:27 Inactive
@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) August 13, 2023 04:37 Inactive
@Keavon Keavon marked this pull request as ready for review August 13, 2023 04:39
@TrueDoctor

Copy link
Copy Markdown
Member

@Keavon It is unfortunate you had to revert the brightness contrast changes. It would be very good if we could reuse that code instead of duplicating the entire file + we lose the improvements to the code structure

@Keavon

Keavon commented Aug 13, 2023

Copy link
Copy Markdown
Member

Yes, but that'll have to be a future contributor's task since the more important priority right now is just getting this merged in its current (plus slightly fixed up) state.

@github-actions github-actions Bot temporarily deployed to graphite-dev (Preview) August 13, 2023 08:00 Inactive
@Keavon Keavon merged commit dc4b16a into master Aug 13, 2023
@Keavon Keavon deleted the curves-node branch August 13, 2023 08:07
@Keavon

Keavon commented Jun 13, 2026

Copy link
Copy Markdown
Member

Hi @nat-rix, thanks again for this code contribution to the project! We're still hoping you will respond to the request to relicense this code. Please see #4208 ASAP, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants