https://github.com/drewcrawford/quartzcorer
Drew's very fast Core Animation bindings
https://github.com/drewcrawford/quartzcorer
core-animation coreanimation quartz quartzcore rust
Last synced: 3 months ago
JSON representation
Drew's very fast Core Animation bindings
- Host: GitHub
- URL: https://github.com/drewcrawford/quartzcorer
- Owner: drewcrawford
- License: other
- Created: 2021-11-14T02:29:27.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-10-23T21:09:22.000Z (8 months ago)
- Last Synced: 2025-03-24T11:02:07.702Z (3 months ago)
- Topics: core-animation, coreanimation, quartz, quartzcore, rust
- Language: Rust
- Homepage:
- Size: 12.7 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Drew's fast Rust QuartzCore bindings
Provides select Rust bindings for Apple [QuartzCore](https://developer.apple.com/documentation/quartzcore) framework, also known as Core Animation. As far as I know,
this is the only crate to use this framework from Rust.Part of the [objr expanded universe](https://github.com/drewcrawford/objr#objr-expanded-universe), distinctive features of this library:
* Fast. This crate is *significantly* faster than other crates. If you're struggling to get 60fps or ProMotion/adaptive refresh rate speeds, this
is the solution for you.
* The full set of optimization is far too many to list, but the big idea is to either do what native ObjC/Swift applications do, or do something faster.
* Compile-time selectors. Most Rust crates do a runtime lookup for ObjC methods, which involves acquiring a lock and other yucky stuff, either on the first call or every call. Instead, we do what real ObjC compilers do, which is way faster. For more details, see [objr](https://github.com/drewcrawford/objr)
* Smart pointers that provide global ARC inference. Like ARC, you don't need to write manual retain/release calls. Unlike ARC, the compiler
usually doesn't need to write them either, meaning lower runtime memory management cost than even native code. For more details, see [objr](https://github.com/drewcrawford/objr).
* Runtime autorelease eliding, which keeps your objects out of autoreleasepools. For more details, see [objr](https://github.com/drewcrawford/objr).
* Pointer packing for optional types so they fit in a `u64`. For more details, see [objr](https://github.com/drewcrawford/objr)
* Safe APIs. Where possible APIs are designed with safe abstractions to provide familiar guarantees to Rust developers
* Low-level. These bindings assume familiarity with bound APIs and are not documented separately. For details on how they work, see the native documentation.
* Free for noncommercial or "small commercial" use.# Implementation status
The following APIs are at least partially implemented. These implementations are incomplete but contain common functions or "the ones I use".The [objr](https://github.com/drewcrawford/objr) macro system makes it very ergonomic to add new bindings for specific missing features
or new Metal APIs.* CAMetalLayer - many APIs
* CAMetalDrawable - a few APIs
* CALayer - type only
* CALayerDelegate - type only