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

Allow the underlying DOM implementation to be changed #34

Open
lastmjs opened this issue Feb 16, 2017 · 1 comment
Open

Allow the underlying DOM implementation to be changed #34

lastmjs opened this issue Feb 16, 2017 · 1 comment

Comments

@lastmjs
Copy link
Member

lastmjs commented Feb 16, 2017

Explain and allow for different DOM implementations to be used. Explain what types of devices scram can run on if it uses Electron, versus if it uses jsdom or another library. Provide much more detail on the types of devices and how to use scram on those devices. I think it will be a good idea to call scram as its own binary...

@lastmjs
Copy link
Member Author

lastmjs commented Aug 14, 2018

Yes, this makes sense. I don't think we'll ever need Electron though. Node.js as a platform can be supported through something like basicHTML: Should be obsolete in lieu of basicHTML: https://github.com/WebReflection/basicHTML, and then other implementations can be supported with an implementation similar to basicHTML. In fact, perhaps we will be able to compile basicHTML to web assembly and use it on much more resourse-constrained devices, and perhaps if Rust can import web assembly libraries, we can really share all of this implementation. Follow basicHTML and WebAssembly, perhaps an AssemblyScript implementation will be the easiest thing to do at first. Though, we should probably keep all of these repositories separate, who knows.

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

1 participant