That’s totally what we’re going for. Speckle w/o any kits would be… rather disappointing 
This approach does lock the end-user in a potential “only one kit per push” - so objects inside a specific stream version (we’re renaming that to commits, but that’s another post!) can’t have mixed sources - not a big issue in itself.
I feel that another aspect we didn’t describe well yet, in terms of behavior, is un-conversion. This won’t change that much.
The current envisoned flow is:
- Blobs getting streamed back from the server - as a
string. It’s pure text at this stage. Yes,jsonformatted text, but it’s still text. - We deserialize that text into an a specific class (coming from a kit!).
- If the original class is not present, we fall back on the base speckle object class, and store the props as dynamic props.
- If the original class is there, no problems - proceed as usual.
- At this stage we have kit object of a specific type, that comes from a specific kit, which should expose a specific
IConverterclass for the current host application - no user input needed!
@Daan, agree re versioning. We’ll most likely, in the alpha stage, start without it but add it during the beta stage.
The reason being that it sounds like potentially a lot of work and testing to get right, and we wanna get alpha stage code out to you ASAP 