3 ms·
Hi, OP here. For folks who prefer HTML5 APIs, I'm also working on a layer that translates these Qt APIs into HTML5 primitives (like Canvas and AudioContext): h
by arturadib 15y ago
Hi, OP here. For folks who prefer HTML5 APIs, I'm also working on a layer that translates these Qt APIs into HTML5 primitives (like Canvas and AudioContext):
http://news.ycombinator.com/item?id=3816870 http://news.ycombinator.com/item?id=3816870
(There are some neat demos there :))
- buu700 15y agoWait, so what Node-Qt and Node-Five would both allow you to use exactly the same code?
- arturadib 15y agoNot the same, but sometimes similar. (For example the QPainter API is similar to the Canvas 2D API, etc). Node-Five is for folks who are more familiar/prefer HTML5 APIs over Qt's proprietary API.
- buu700 15y agoHold on, I think I misinterpreted something. Is Node-Five a Web framework or a native application framework?
- arturadib 15y agoThink of Node-Five as a very small WebKit/Gecko engine for Node.js. It is written in JavaScript on top of Node-Qt, whereas Node-Qt itself is written in C++. When I say "native apps" in this context I simply mean you don't need a traditional browser to run the apps, and the runtime interacts more closely with the OS (for example, Qt exposes native menu methods, native OpenGL, etc).
- buu700 15y agoAh, okay, awesome. I was thinking Node-Five was a Web framework which would take your Node-Qt code and run it server-side as a public Web application by translating the Qt API calls.