Matt Campbell

Given that I've addressed your concerns about code size and linking requirements, and you're willing to distribute AccessKit with the engine, would you prefer to work with a C API...

The JSON format is neither documented nor stable yet, but it will be by the time AccessKit gets to 1.0. In fact, I want to experiment with pushing the JSON...

Since someone mentioned my AccessKit project, I'll offer a quick update on it. I've got a basic Windows implementation working; the biggest limitation right now is lack of support for...

As far as I can tell, rust-cpython is already licensed under only the MIT license. That's fine with @DataTriny and me. It's the Apache license that's problematic, since it's incompatible...

@davidhewitt Have you found time to reach out to Van Lindberg or the Rust Foundation yet? I now know of a concrete case where this relicensing effort matters: [MathCAT for...

Let me provide some clarifications on binary sizes. I'll be breaking down the sizes of the shared (dynamic) libraries on all supported platforms, for the x86-64 architecture. The sizes for...

The AccessKit Python package is now [published on PyPI](https://pypi.org/project/accesskit/). Of course, the C API is also an option if, for some reason, adding this Rust-based Python extension module to the...

Now that [AccessKit](https://github.com/AccessKit/accesskit) integration is merged in egui, and the AccessKit Windows backend supports text editing (coming soon on macOS), maybe it's a good time to look at integrating AccessKit...

If there are any concerns about AccessKit's implementation, API, or support for different widget types that are blocking Slint's adoption of AccessKit, please let me know. Thanks.

There is no such requirement on initialization. That's the whole reason we run an async executor on its own thread. As you can see in `accesskit_winit`'s example, and in the...