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

Contributions? #1

Open
ryceg opened this issue Jun 7, 2022 · 3 comments
Open

Contributions? #1

ryceg opened this issue Jun 7, 2022 · 3 comments

Comments

@ryceg
Copy link
Contributor

ryceg commented Jun 7, 2022

Hi there, you might recognise me from the other thread. I'd love to get involved- though I am not familiar at C# so can't help with the porting over. Anything I can do to help?

@aseaday
Copy link
Owner

aseaday commented Jun 7, 2022

Hi, very grateful for you. I am planing to write down the port roadmap especially my working progress and future plan.
I think one important thing is that the render vendor. It could be canvas, webgpu on the browser or soemthing node.js could support. If you feel interested in it. It is a good start. My focus is the port of interpreter this week.

@ryceg
Copy link
Contributor Author

ryceg commented Jun 9, 2022

Performance wise, WebGPU might be best but it doesn't have nearly the adoption rate of canvas- my suggestion would be to focus on canvas implementation as a baseline and then extend out to WebGPU. I can see instances where node.js would be useful, too.

@aseaday
Copy link
Owner

aseaday commented Jun 9, 2022

I had finished a basic demo support a easy line. You could see it in the README.md with some guides to contribute.

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