Page MenuHome

Spreadsheet editor navtree total number of components per domain
Closed, ResolvedPublicDESIGN

Description

It is helpful to see at a glance the ballpark figures of the different domains in an object. This will be particular important when inspection of active nodes is supported: (T86584)

For instance, some nodes create a lot of geometry, or add point instances, or create geometry.

For lower numbers (under 100) the exact number can be useful. But for anything larger than that it is more important to be able to tell if there are hundreds, thousands, millions or billions of elements.

This task is for the design/mockup of this. The mockups without this are here: T86027

Design by @Fabian Schempp (fabian_schempp):

|

Event Timeline

Dalai Felinto (dfelinto) changed the task status from Needs Triage to Confirmed.Mar 24 2021, 11:37 AM
Dalai Felinto (dfelinto) created this task.

Hi @Fabian Schempp (fabian_schempp) the right-most image seems fine.
What is not clear to be is what is the formal definition for when we should the precision separator, whether we cap the polygon count at a number. This can be cleared during implementation though.

Hi @Fabian Schempp (fabian_schempp) the right-most image seems fine.
What is not clear to be is what is the formal definition for when we should the precision separator, whether we cap the polygon count at a number. This can be cleared during implementation though.

Yes my design is a bit mixed up I initially wanted to keep it at 2 digits but I think 3 would be needed to represent all numbers. And I would use only one digit behind the seperator.

  • max length: 3 digits + seperator + unit
  • one digit behind the seperator

-> 1, 10, 100
-> 1K, 1.5K, 10K, 10.5K, 100K, 500K
-> 1M, 1.5M, 10M 10.5M, 100M, 500M
-> 1B, 1.5B, 10B, 10.5B, 100B, 500B
-> ...

Dalai Felinto (dfelinto) closed this task as Resolved.Apr 26 2021, 12:18 PM
Dalai Felinto (dfelinto) claimed this task.