windy VS owlkettle

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.

This is really cool! I love the JSX-like approach to UI and it's a shame it's not so common on desktop. https://github.com/can-lehmann/owlkettle is the only thing I find comparable.

Ones that have not been mentioned so far:

nlvm is an unofficial LLVM backend: https://github.com/arnetheduck/nlvm

npeg lets you write PEGs inline in almost normal PEG notation: https://github.com/zevv/npeg

futhark provides for much more automatic C interop: https://github.com/PMunch/futhark

nimpy allows calling Python code from Nim and vice versa: https://github.com/yglukhov/nimpy

questionable provides a lot of syntax sugar surrounding Option/Result types: https://github.com/codex-storage/questionable

ratel is a framework for embedded programming: https://github.com/PMunch/ratel

cps allows arbitrary procedure rewriting to continuation passing style: https://github.com/nim-works/cps

chronos is an alternative async/await backend: https://github.com/status-im/nim-chronos

zero-functional fixes some inefficiencies when chaining list operations: https://github.com/zero-functional/zero-functional

owlkettle is a declarative macro-oriented library for GTK: https://github.com/can-lehmann/owlkettle

A longer list can be found at https://github.com/ringabout/awesome-nim.

Although for a GUI (if I even made one, rather than just a fixed/hardcoded setup) I'd probably use Owlkettle(though there are some things I don't like about it, see closed issue 16).

A similar library in nim is https://github.com/can-lehmann/owlkettle

There's also Owlkettle that seems a bit easier/cleaner IMO, though when I tried it I had some issues (clunky container workflow, wanting better scaling) and would prefer something similar using Qt.