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

Updating to support Node JS #61

Open
Levi-Armstrong opened this issue Nov 12, 2023 · 3 comments
Open

Updating to support Node JS #61

Levi-Armstrong opened this issue Nov 12, 2023 · 3 comments

Comments

@Levi-Armstrong
Copy link
Contributor

@johnwason I am not familiar with SWIG, but noticed that it supports converting to Node JS. I am interested to hear your thoughts on what it might take to updated this to support Node JS?

@johnwason
Copy link
Contributor

I haven’t worked with the JS swig generator but it should be possible. I think a better approach would be to use Robot Raconteur which has a JS client library. JS users are typically not going to need low level interface. There is very little analysis work done in JS robotics it is typically front-end work.

@Levi-Armstrong
Copy link
Contributor Author

The architecture is that you have a separate process running which communicates using Robot Raconteur to the JavaScript UI?

@johnwason
Copy link
Contributor

Typically yes, but it is sometimes possible to run the RR service in the same process. With nodejs there are often multiple processes even with relatively simple programs. For instance electron which is the common ui library runs things in multiple separate processes.

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