Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document the difference to pure QML #7

Closed
ShalokShalom opened this issue Jul 11, 2017 · 2 comments
Closed

Document the difference to pure QML #7

ShalokShalom opened this issue Jul 11, 2017 · 2 comments

Comments

@ShalokShalom
Copy link

QML is indeed Javascript and you can write in pure JS in each QML file

Where is the difference to this project?

@ShalokShalom ShalokShalom changed the title Dokument the difference to pure QML Document the difference to pure QML Jul 11, 2017
@cfsghost
Copy link
Collaborator

cfsghost commented Aug 5, 2017

The JavaScript in QML is limited, which is used for QML components control only. If you need more functions that something's like system calls(FileSystem, Socket, crypto ...etc) or using external libraries, C/C++ is the only way to make it.

Brig project provides a way to make it possible to use Node.js to extends QML without C/C++, that means you can do more thing in QML with NPM modules and Node.js APIs.

@ShalokShalom
Copy link
Author

Aha, so it basically expands the JS compatibility to Qt with Node.js? You may want to add that information on the README and so. Thanks a lot for the clarification, I will add that to the bindings section of the Qt Wiki, once an internal issue is solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants