> NodeJS-to-Native-GUI

I feel I have to find a better name for libui-node

Some days ago I started a N-API version of the bindings: https://github.com/parro-it/libui-napi

Is still really incomplete compared to libui-node, but just in case someone wants to help

Is it a pretty simple re-write or something that requires a lot of c wizardry?

Not a simple rewrite, but neither a task that require a C wizard... The current version of libui-node implements C++ classes that wraps libui C function. They are exposed directly to JS. This experiment implements N-API C functions that wraps libui C function. Then, a set of JS classes wrap them, offering the same public API as libui-node.

Currently, I implemented windows, boxes, and multiline entry. I have to compare this experiment with the curent implementation in terms of erformance, memory consuption etc. before to decide to continue with N-API or not.

FYI, I just wrote the comparison I was speaking above: https://github.com/parro-it/libui-napi/issues/11

Pretty impressive results!

Yes, N-API seems to be superior. And it's a particular good fit because libui itself has a C API

Hi, libui-node author here. I'm glad for your appreciation. The project is well alive now, proton-native give me new motivational energy

The data grid has still problems on macOS unfortunately, but @andlabs is working on it...

No, the data grid has problems on Windows, as that code is being contributed by someone else. I already have it on macOS and Linux, and have for years now... Hopefully soon the Windows code will be merged in and we can keep going.

Ah yes, sorry @andlabs

Also (for the benefit of the rest of HN) s/as/but/ — I had problems on Windows, and someone is proposing a solution I just need to merge in once the mega-PR that added it and a bunch of other things are split into more manageable chunks that won't merge conflict as easily with what I am independently doing to stabilize the build.

I'm not a native speaker, I had no idea what "kike" means in english before reading this issue.

I intended the word only in the sense "to suffer the same fate as the azer/kik project".

I renamed the project, my apologies to anyone who could have been offended by my mistake.

No harm done, node itself has 'gyp' which is a racial epithet for gypsies in most of Europe.

Even "gypsy" has negative connotations, hence their preference for "Roma", generally speaking.

Btw, it should also be "are trademarked" :)

Right!