Nice, glad to hear! (I’ve moved your reply to the unreal connector discussion thread - felt it’s better). All your comments are spot on.
Re (1) we have no real experience, so if it makes your life easier, we can look at doing things like that. Regarding (2) - it’s just a POC implementation currently, so that can definitively be implemented. Our ideas here were to follow the implementation of our grasshopper and dynamo clients, and have a little url parser in front that dictates what’s happening:
(3) Is a longer discussion, what would be the data you have in mind? It’s going to be particularly difficult, as Unreal works with meshes: what you would be able to send out is just that. Some properties, such as volume, length, etc. will be lost. Nevertheless, we’ve found that this is usually good enough for a review process.
(4) Totally, yes please!
Re contributions: our policy is to accept PRs from other forks of our repos. The workflow would be to fork our repo and submit PRs upstream whenever you are ready to do so. It’s good to raise issues in the parent repo so we can follow along, discuss and coordinate on changes. And, as well, please give the contributions guidelines a quick read!