Inspiration

Digital Twin is an offshoot of Moore's law. With computing power, the 7-Layer Silo is breaking. Allen T my erstwhile neighbor, invented a virtual machine, setting off a virtualization trend: First money got virtualized and so IBM was born; Did you know that IATA is the precursor of modern computing trends? More recently, Amazon copied IATA, the data centers got virtualized and Cloud Computing became the fad. That spilled over to Taxi Hailing as cartography got virtualized. Digital Twin is the new catch phrase for the convergence of all these varied trends - yet it is in a nutshell indeed Virtualization, Virtualization, Virtualization! Virtualization provides new affordances, rather Digital Twin( read - Virtualization) demands new affordances. And UI/UX will have to proactively cope up with the demand! For instance, UI/UX apart from getting the work done, will have offer scope for expressing the Human Empathy - it is in this context MX devices are relevant! The Actions SDK is indeed a jail-break by Hardware layer into the Application layer. Exchanging empathy is a sure shot way to succeed in any freedom struggle: This challenge submission is an expression of solidarity in the silo breaking freedom struggle! The I/O peripheral has come a long way from punch card to VT100 toMX - from simply TX/RXing bits to (possibly)exchanging Empathy. To actualize that, MX devices need some love/empathy initially - this plugin a humble expression of it.

What it does

This Option+ plus plugin for Gimp3 ( GNU Image manipulation Program version 3) integrates the versatile Gimp3 to even more versatile MX devices. Actions and Workflow in Gimp3 are bound to Actions in Options+ so that custom profiles, Action Ring configs could be effortlessly made for Gimp3 operations and workflows.

Why Gimp?

Gimp has a long history of easy extensibility. Making its versatility come alive with MX devices would widen the market reach of MX devices. Possibly triggering a MX device adoption spiral.

How we built it

The project is built using AWS Kiro as the dev environment. It was given a requirements input. It generated the requirements and the design and translated the design into tasks. It was guided to use the Logi ActionsSDK. The NoAsService plugin https://github.com/KobeBrandt/no-as-a-service-logi-plugin/tree/main and LibreHardware monitor https://github.com/notadoctor99/librehardwaremonitorplugin/tree/master served as ereference sdk plugins to learn the SDK. The OBS plugin - both the Option+ side and the OBS side of it is available as opensource. This helped the communication design and advanced features. Indeed the OBS use case brought out the applicability, versatility of MX devices to Gimp. We searched far and wide for a way to do the 2-way communication between the application and the device, and settled on MQTT pub/sub as the way. The availability of MQTTnet as a robust in-memory MQTT server was a clincher for the MQTT way. We are very proud of the how MQTT over websocket could be handy for Web apps integration and excited about Web Apps seamlessly interacting with MX devices. That is the HapticFox for your - and it is FOSS!

Challenges we ran into

Kiro was playing dumb/unimaginative developer focused on getting the spec driven development to 'production' and finish-off. Got into the usual debug and Aha moment coding gotchas.

Accomplishments that we're proud of

Progressing this much without having a device, doing the dev purely on the cloud. Doing it with Kiro and the related productivity(?!) gains. Frankly, without AI assistance, the contest would have been dismissed at the first look itself. The message broker based reusable 2-way communication design. Last but not the least - the spilling MX to the real world ( Ahem, subject to winning!)

What we learned

If the human is de-cluttered, good design bubbles up. Presently AI is more like cross checking the technical knowledge of the human. The threat of AI is like the threat of the Mouse: Pointing devices and touch dramatically transformed human-computer interaction, UI and UX. Across industries. Just like how Mouse is taken for granted ( it got assimilated!) the AI needs to be assimilated completely. Sooner the better. But we are far off - which is also good!

What's next for HapticFox - Gimp Fox on the loose; Gimp3 Options+ Plugin

Making Action Ring like UI/UX spill to the real world. Like the mouse, the Action Ring UI/UX is to be assimilated by one and all. This submission is a small step towards that leap.

Built With

Share this project:

Updates