Skip to content

Separate client and daemon #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 21 commits into from
Dec 11, 2022
Merged

Separate client and daemon #57

merged 21 commits into from
Dec 11, 2022

Conversation

LGFae
Copy link
Owner

@LGFae LGFae commented Dec 4, 2022

This separates swww into two programs: a client and a "server". The "server" is just our previous daemon.

I moved everything I could to the client, so as to lessen the daemon's dependencies and code size. On my machine, this seems to have as much as halved the overall memory usage, both when animating a large gif, and when doing many image transitions. I personally also believe that the code looks simpler now. The daemon's internal logic was greatly simplified. The most complicated thing now is how the client needs to ask the daemon the outputs' size to know how to resize the image.

Currently, this version should work 100% correctly, but I still plan to test it more before merging.

Furthermore, I was thinking of making more modifications to the code, to make it more organized in general.

Closes #52

@LGFae LGFae force-pushed the separate-client-and-daemon branch from aff6a04 to 154fda7 Compare December 9, 2022 22:10
@LGFae LGFae merged commit 358eaa2 into main Dec 11, 2022
@LGFae LGFae deleted the separate-client-and-daemon branch December 11, 2022 02:08
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.

Separate daemon and client in two separate programs
1 participant