Implement per-object-colours

[didimitrie]

Step 0:

• I've read the contribution guidelines!

It's essential for people doing analysis and wanting to view results online. How to implement, I'm thinking more of convention rather than schema-level enforcement:

If an object has a properties.spkcolor property set to a value we can actually parse and use (ie, hex or rgba?) use that to override any other default colours set for by layers, etc.

This should work for any object type (also points, lines, etc.).

[mswaidan]

That strategy seems fine. Can we also expand from just colors to materials? Something like:

properties.spkMaterial = {
  type: diffuse, specular, etc.
  color: rgba OR map
  specular: float OR map
  bump  = map
  etc. }

Obviously we don't want to send a bunch of material maps back and forth for each object / layer. Maybe theres a SpeckleMaterial that is referenced by objects/layers instead? Thoughts?

[didimitrie]

Hm... If any texture info is just a pointer to a resource we can request async, i'm happy. I would not store such things in the db though.

I do believe both would be good, ie can have just a simple colour, or if really keen, a sweet material.

So I would say yes to a SpeckleMaterial of sorts (maybe we'll get inspired by gltf), but one with textures only for version 2.0 (as that's when we're going to add a s3-compat layer, where we can store blobs efficiently), and for 1.0 colour (simple) and material (no textures). Does that make any sense?

[didimitrie]

closed in #78