It goes beyond that by also adding Wayland support. Shuttle-lander then converts device inputs into keys using what I think is the same approach as Nanosyzygy’s ShuttlePRO for X11 systems. Plus, the lack of a cross platform API means I’d have to do the same R&D on Windows and Mac, and Mac’s documentation on the topic is very lacking. ![]() That is the approach I was planning on taking for QPrompt because I couldn’t find a cross platform solution to read those inputs but I decided to focus on global hotkeys instead for now, since they would allow routed keys to work even when QPrompt isn’t focused. Maybe… I’ve got to say, Robotista/shuttle-lander looks very promising! The program is grabbing the inputs straight from the Shuttle devices using native Linux APIs. ![]() To be honest I’m mostly interested in this side project because it seems like a fun challenge, but that’s only enough for me to get it started, not necessarily finished. Most developers out there also wouldn’t know how to tackle our desktop fragmentation in a way that is sustainable. There are over a dozen of window managers and desktop environments to support, and two completely different display technologies X11 and Wayland, that deal with inputs in very different ways. Going back to the Shuttle’s interface, I see people could complain because this may seem like a simple app that Contour gives for free in other platforms, but there’s nothing simple about this software on Linux. This is because paid is associated with proprietary software, even when that isn’t the case which is why I admire the Elementary OS and Flatpak projects, for their initiatives that push the boundaries. Charging usually prevents word of mouth from happening because paying for software in Linux is a controversial topic. I’m aware that Linux users in general may react negatively to charging for the software that I make. Here’s what I’ll be working with: libusb: Asynchronous device I/O I’ll be looking into a library called libusb, which supports multiple operating systems, is well established, and has the potential to work for a very long time. This shouldn’t be a problem for commonplace distributions until, at least, 2026.Ī more cross platform approach is recommended to enable QPrompt’s Shuttle support on a wider range of devices, and for a longer term. Which doesn’t include modern versions of macOS, nor any version of Windows and it will fail to work on future Linux distributions once distros have fully replaced Xorg with Wayland and start offering no X11 backwards compatibility. This means that this library will only work on Linux and Unix systems that make use of the Xorg display server. I’ve also taken a quick look at nanosyzygy/ShuttlePRO’s source code and noticed that it is dependent on X11. I ended up purchasing the Shuttle Xpress and Shuttle Pro V1, and am still on the lookout for a Shuttle Pro V2. Code contributions (contributions in the form of software development time) are also welcome. Nevertheless, QPrompt will always be free software, as defined by the Free Software Foundation, and Open Source as defined by the Open Source Initiative.Īnyone interested in QPrompt having support for the Shuttle Pro V1, or any other device, is invited to donate one of such devices to the project, and I will gladly provide support for it. QPrompt is meant to be a self sustaining project, so I may end up charging for the feature. I will only be supporting these two devices for now, and none of their earlier versions. I’m currently in the process of purchasing both the Shuttle Pro V2 and Shuttle Xpress with the intent of developing support for them, on all platforms, later this year. Now to answer your question more directly, and update on the matter: ![]() If you or anyone is willing to donate one or more of these devices, I will add support for them." I’ve already identified a library that can be used to abstract some of the code so that its easier to support all platforms. "Dedicated hardware support requires said device to be developed for individually on each supported platform. This was my reply to videosmith’s request over at GitHub: ![]() Hello few users, including have asked for Shuttle support to be added.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |