Hi sledgeman. Thank you for the support. Your questions are very much welcome.
More than compatible, I'd say that it "is" three.js with an engine around it. In fact, we decided against "rolling our own", in favour of a well known and battle tested rendering engine. The scene is a three.js object so you have all of its features at your disposal + engine related api and the component system which "proxies" some Object3d methods and ads a couple, without changing the state of the objects or "touching" the library.
We're still deciding this. Mainly because the engine uses three.js on the background and any change to the api, could easily break it. The good thing is that since our "extension" doesn't touch the library itself, for us it'd be quite trivial to update three.js and make the necessary changes, but it might be dangerous to give control over this to the user. Still, like you said, it's very early to tell.
This is among the first custom components we had in mind to build first. You have just pulled it up on the list 👍
This one is in our mid-long term scope, but here's why. We're focusing on extendibility, since we're hoping people will create more components and even better than ours. We hope that for whatever component we create someone will publish a far better extension, and since creating/publishing them (mark my words here) will be very simple, if there's a component missing, someone will create it. So, visual scripting might not be on the top of our list, but hopefully it might just be on someone else's.
The automated publishing is on our Trello board. It's still early, but we're planning on creating a publishing portal and a service to publish directly from the editor. I imagine something like a private cloud build, that you can make public.
Three has an SVG loader. It's all three.js on the rendering side so, If three.js can handle it, we can. Someone could even come up with an SVG editor window extension.
Same as before, we use three.js file loaders. The only difference, of course, is that you just have to drag n drop the file, we handle the import code on the background.
Thanks for your questions, I hope I was able to clear most of your doubts. Any suggestion, feedback or requests are most welcome