NodeGui

if those are correct, what do you say of giving a short for a tool that automaticaly generates types (with jsdocs) from qt sources ? (which I assume has headers with comments ?

I recently gain experience regarding this and I'm maintaining opencv TypeScript typings for opencv.js (webaseembly port) basically consuming doxygen XML output this is the result

I wonder if something like this iw worthwhile or if i'm totally mistaken in my assumptions

and finally and related, just want to know if you are aware of this project claiming to automatically generate bindings and typings by small declarations in the c++ files (https://github.com/charto/nbind) ? - just asknig - never used it but I see projects facing problems similar as this using it successfull and if the claims are not false that would save lots of work and accelerate the API porting... thanks and sorry to speack without even being familiarized with the project

nodegui APIs are similar / equivalent to qt APIs - Yes, we want to keep nodegui APIs similar to that of Qt APIs as much as possible so that we can make use of api design decisions that are made in Qt (which are mature and really nice). But there will be few changes where necessary due to language differences. Also, we are not aiming to export all of the apis from QT (only those are necessary). For example we are not going to export out all overloaded methods.

NodeGui typings are not manually created. We have a TS counterpart to the c++ bindings. This is necessary for handling events and making necessary changes to exported bindings due to language differences. These TS counterparts additionally also serve as typescript typings.

https://github.com/charto/nbind <- Yes, I did take a look at this. The big issue with this is that it generates NAN bindings instead of NAPI. NAPI is the newer and ABI stable bindings for node js addons.

If there is something like nbind for NAPI we can take a look.

Also, Lets try and discuss these in General channel instead ? since its easier to navigate there.

Yo,

First congratulations for the project!!!

Its only possible use typescript to work with nodegui?

Hi Dalton, you can use plain javascript as well. just replace .ts files with .js files and replace import statements with require in the starter peojects

Hi team, thanks for the hard work on the library. I'd like to use this for an embedded application, the application should start up in fullscreen, I'm not sure if the API has been exposed for that or whether it's possible?

Realise I'd likely want to write straight to the framebuffer, like you can with Qt

But if that's not possible, programatically setting it with something along the lines of:

Mainwindow w;
w.setWindowState(Qt::WindowMaximized);
w.show();

Hi

@keabarnes

You can already do this using

import { QMainWindow, WindowState } from '@nodegui/nodegui';
const win = new QMainWindow();
win.setWindowState(WindowState.WindowMaximized);
win.show();

@master-atul

, I'd like to contribute to help filling up the Handle events page, where should I start?

Awesome! The documentation lives in the same repo as the project. The guides can be accessed here: https://github.com/nodegui/nodegui/tree/master/website/docs/guides They are all just mark down files. And NodeGui is using docusauraus.

Great, regarding the event list, I guess I can find it on the Qt Event System docsite right?

Yes, NodeGui supports all events from Qt.So that you can get from Qt's docs or from here: https://github.com/nodegui/nodegui/blob/576ba1ace6e6e67bd65889303c9f1909249cce31/src/lib/core/EventWidget/index.ts#L40. Apart from regular events, Qt also has a concept of signals. So NodeGui also adds support for some signals. signals need to be manually exported out. So those you can find in each widget's source code ( I think those should live with each widget's doc). Since JS has only the concept of events. I merged Qt's events and Qt's signals into one in NodeGui.

Let me know if you need more clarification.

Thanks!