Gadget toolbox UI is terrible

[JoeLudwig]

• Gadgets collide with each other
• The "I'm in range" indicator of increasing the scale is hard to see on many gadgets
• Gadget "icons" are all different sizes
• Gadget names don't appear anywhere
• There's no way to remove a gadget from the list once it appears there
• The scroll thumb (if that's even the right metaphor) is too small

[JaredMonkey]

Making something like this. Back facing spheres, with 3d assets inside.

[JoeLudwig]

That looks nice. Have you tried prototyping that in Aardvark?

[JaredMonkey]

Thanks! I'll get the back facing asset in, and start with a static radial layout to see how it is in app.

[JaredMonkey]

Backfacing spheres work as expected and seem to be decent in Aardvark with the lighting update. I also have a means to make new environment maps in the right format now. I could even bring in the one from the comp. I've got a clear path to getting Gadget Seeds to look like the comp I can get going quickly.

I tried laying out the gadget seeds with CSS and the underlying html div classes got styled, but the aardvark components didn't seem to get adjusted. I was prototyping in Chrome dev tools to start out with.

Going to go down a path of wrapping the Gadget Seeds in AvTransforms and lay things out better tomorrow.

[JoeLudwig]

I added "scaleToFit" to models, which should help with gadget scale. See AvGadgetSeed for examples

I also fixed a bug with sphere-sphere intersections not taking scale into account, which was causing the radius of the gadget seeds in the control panel to be very different from the size of the models. (The control panel is scaled by 0.25, but the radius being used for those controls was unscaled.)

Those should make things work better.

[JaredMonkey]

scaleToFit works well. Trying out some layout logic

[JoeLudwig]

Are you still thinking about this, or should we unassign it?

[JoeLudwig]

Gadget menu has been completely replaced, and most of these issues are better. If there are any issues with the new one (which seems likely), we should open a new Github issue to track it.