-
Notifications
You must be signed in to change notification settings - Fork 0
Implement features requested in Issue #2 #3
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
base: tauri_frontend
Are you sure you want to change the base?
Conversation
Added a UI element to indicate the option to delete locally saved video files
…rement Add buttons to pause dynamic backgrounds (either all or only the one on the active space). Remove requirement of a nightly chain for building from source.
Added a very hacky way of hiding and (again) showing the app icon. Currently causes the app window to flash very briefly.
Use `SMAppService` class to register the app officially as a LoginItem, i.e. launch the app on startup/login, if the user agrees to do so.
Add external Objective-C library to check if the app was launched as a LoginItem, i.e., automatically at startup. For this, an external library was written in Objective-C, which then gets compiled within the `build.rs` file automatically. Supports fat (universal) binaries with Tauri's `universal-apple-darwin` target.
Add Apple Clang as a build dependency to README.md
|
I see there is some progress, awesome 👍 Can you make a (beta) build; I can't seem to make a build on my own according the instruction you mentioned earlier, and I surely want to test the changes you made. |
Sure, I'd love to! But keep in mind that this is all very much in beta right now and I currently question my approach to certain topics. This is all very much based around Apple's AppKit, Core Graphics and Core Foundation frameworks. As the code grows I do realize that I have to write more and more code in Objective-C (and C, because there will be a need for Apple's Private APIs). The interoperability with Rust directly is - let's put it very plainly - half-baked at best. Even more so, it discards Rusts memory safety guarantees and I do see some SIGSEGVs happen. |
|
Hey, me again :-) It's been a while ago, so I thought let's get in touch again. Would love to hear if you still have plans to work on the mentioned adjustments. Just wondering because it can be an awesome app IMO. |
As requested in #2, WavyBackgrounds should be enhanced with new features. This draft pull request keeps track of the current progress:
To test out the new and yet to be merged features, clone the
devbranch.