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
Should we be using a custom editor or Scratch 3.0? #1
Comments
We should use scratch 3.0. Scracth 3.0 uses Blocky. |
But... We would be rewriting quite a lot of the code anyway. The basic drag-and drop mechanics won't be that difficult to re-code. IIRC, that would also mean we have to be BSD-licensed rather than Apache |
Making our own Will Take a lot of time. |
@Narulacodes Repo for what? This is the editor repo... |
Opps. So how are we going to make this? |
SVG elements to render blocks, perhaps. For drag and drop, probably just this. |
How do we start this? |
I don't know. Right now, we are still in the process of fixing elementnet/elementnet-www |
What Do we need to fix? |
Organization. Take a look at other Node.JS projects. Root is clean, a few folders, and are built. I tried to do some of this on the |
So, What files? |
We should also probably move this elsewhere (like Gitter) |
@elementnet/editor Question: is it really that good of an idea to be using our own block rendering and stuff? I think we'd be much better off using Scratch 3.0
On the other hand, that would mean we would have to re-program it to work for us properly.
The text was updated successfully, but these errors were encountered: