This looks amazingly useful but I struggle to overcome my irrational dislike of projects that use NeXT!s naming convention and are not written in Objective-C.
Sorry. When I mentioned the project name, without linking to the project, it was a point of confusion for someone last week; they assumed it was an Apple-only thing. So I’m actually thinking about renaming it.
I originally conceived the name in 2012 or 2013, long before I started working on the project itself. I didn’t intend to write it in Objective-C back then either; I originally figured I’d do it in C++. But I wanted my library to be the WebKit of accessibility, in terms of its broad platform support. That was before Chromium forked WebKit.
I haven’t come up with a particularly good new name yet. Here are the ones I’m thinking of:
But I wanted my library to be the WebKit of accessibility, in terms of its broad platform support. That was before Chromium forked WebKit
WebKit is also a slightly confusing name because it’s the name of the Objective-C framework that provides a web view as well as the name of the umbrella project. The thing that people normally think of as WebKit is the combination of WebCore (the HTML / CSS part) and JavaScriptCore (the JavaScript JIT). Most of the non-Apple ports of ‘webkit’ ported everything except the WebKit framework.
AccessKit is a great name, you could easily pull a Polkit (formerly PolicyKit) and just name it Accesskit. But It’s okay for people to be wrong, it’s your project.
libaccess sounds good. I’m somewhat used to lib* being a C library, but I don’t know if there’s any similarly widespread convention for Rust libs (that wouldn’t just make the name more noisy).
The lib- prefix is also used for non-C things that expose C-compatible interfaces. My understanding is that AccessKit is intended to be usable from any language, so that makes sense.
This looks amazingly useful but I struggle to overcome my irrational dislike of projects that use NeXT!s naming convention and are not written in Objective-C.
Sorry. When I mentioned the project name, without linking to the project, it was a point of confusion for someone last week; they assumed it was an Apple-only thing. So I’m actually thinking about renaming it.
I originally conceived the name in 2012 or 2013, long before I started working on the project itself. I didn’t intend to write it in Objective-C back then either; I originally figured I’d do it in C++. But I wanted my library to be the WebKit of accessibility, in terms of its broad platform support. That was before Chromium forked WebKit.
I haven’t come up with a particularly good new name yet. Here are the ones I’m thinking of:
WebKit is also a slightly confusing name because it’s the name of the Objective-C framework that provides a web view as well as the name of the umbrella project. The thing that people normally think of as WebKit is the combination of WebCore (the HTML / CSS part) and JavaScriptCore (the JavaScript JIT). Most of the non-Apple ports of ‘webkit’ ported everything except the WebKit framework.
The strongest candidate so far for a new name is “libaccess”. Any thoughts?
AccessKit is a great name, you could easily pull a Polkit (formerly PolicyKit) and just name it Accesskit. But It’s okay for people to be wrong, it’s your project.
libaccesssounds good. I’m somewhat used tolib*being a C library, but I don’t know if there’s any similarly widespread convention for Rust libs (that wouldn’t just make the name more noisy).That’s definitely not a convention for Rust libraries, which is one strike against that name.
The lib- prefix is also used for non-C things that expose C-compatible interfaces. My understanding is that AccessKit is intended to be usable from any language, so that makes sense.
I had started to build something like this at work, for accessibility testing.
But this is so much better in every way. :)