windy VS nim-gamepad

Interesting project, though I'd rather just use Obj-C. I guess if you wanna use it in something like JavaScript or Lua it'd make sense to have C as a bindi g layer.

> https://gamepipeline.org/betray.html

Interesting, I've been using a similar project for Nim lately: https://github.com/treeform/windy

It's surprising how simple Obj-C interaction is compared to Java JNI or something. Here's the Obj-C interop for Windy:

- macdefs: https://github.com/treeform/windy/blob/master/src/windy/plat...

I used https://github.com/treeform/windy in my text editor. It's a pure Nim library like SDL. For separate keypresses I used a state machine where every keypress advances the state and when it reaches an end state the action performed. Works pretty well ^

I made it because I really like pixie/boxy/windy combo, but there is no gamepad support built-in.

The author Fidget actually has a number of other great libraries that are part of the rendering stack. Notably, Pixie for text and shape rendering in 2D, Boxy for rendering textures to the GPU via opengl, and then Windy for an OS window context and user events, and a number of other libraries related to 3D rendering.

Here is my project. Whenever I try to build things that depend on that, it says I am missing the C files, even though it puts them where I would expect. It builds fine from inside the project.

Update: I figured it out so if you need a nice & simple cross-platform nim standalone gamepad library (no SDL or GLUT or whatever) this may be for you!