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

Feature request #4

Open
commandline-be opened this issue Jun 6, 2024 · 2 comments
Open

Feature request #4

commandline-be opened this issue Jun 6, 2024 · 2 comments

Comments

@commandline-be
Copy link

Can it be considered to test this template against Deno to assure it is 100% compatible ?

https://deno.com/

Deno is the open-source JavaScript runtime for the modern web. Built on web standards with zero-config TypeScript, unmatched security, and a complete built-in toolchain, Deno is the easiest, most productive way to JavaScript.

@Heziode
Copy link

Heziode commented Aug 3, 2024

On my side, it works.

From the README, just update instructions to:

Usage

  1. Clone or download this repository
    git clone https://github.com/slint-ui/slint-nodejs-template my-project
    cd my-project
    
  2. Run the application binary
    deno run --allow-read --allow-ffi src/main.js
    

From the doc:

Slint-node (Beta)

Slint is a UI toolkit that supports different programming languages. Slint-node is the integration with Node.js and Deno.

To get started you use the walk-through tutorial. We also have a Getting Started Template repository with the code of a minimal application using Slint that can be used as a starting point to your program.

Warning: Beta Slint-node is still in the early stages of development: APIs will change and important features are still being developed.
source

So, I suppose Deno is the exactly same API than Node.js. But, since it is in an early stage, the API can change.

@tronical
Copy link
Member

tronical commented Aug 3, 2024

Yeah, feel free to make a PR for the README.

One general issue with Deno is the inability to efficiently integrate event loops. The two loops will always be spinning and the app will constantly use the CPU.

With Node.js’ use and exposure of libuv, it’s (theoretically) possible to put both to sleep and wake up accordingly when there’s activity.

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

3 participants