Re:Proton Native – React Native for the desktop
by zengid on Wednesday May 02, 2018 @02:45PM
(#16979979)
>So weight-wise, it's basically comes at the cost of native node module
And now with NAPI [1] it should be easier than ever to make node modules!
Re:Proton Native – React Native for the desktop
by parro-it on Thursday May 03, 2018 @03:00AM
(#16983892)
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
Re:Proton Native – React Native for the desktop
by zengid on Thursday May 03, 2018 @08:30PM
(#16991225)
Is it a pretty simple re-write or something that requires a lot of c wizardry?
Re:Proton Native – React Native for the desktop
by parro-it on Friday May 04, 2018 @12:45PM
(#16995984)
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.
Re:Proton Native – React Native for the desktop
by parro-it on Friday May 04, 2018 @01:48PM
(#16996584)
FYI, I just wrote the comparison I was speaking above: https://github.com/parro-it/libui-napi/issues/11
Sidenote as for why a UI library would wrap another UI wrapping library, Gtk is what is considered "native" on Gnome based distros.
So weight-wise, it's basically comes at the cost of native node module which is not bad compared to Electron's crazy IPC bridge back and forth communication nonsense.