Spreadsheet editor navtree total number of components per domain #86886

Closed
opened 2021-03-24 11:37:25 +01:00 by Dalai Felinto · 9 comments

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: (#86584)

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: #86027

Design by @FabianSchempp:
{F9921040 size="full"} |

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: (#86584) 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: #86027 Design by @FabianSchempp: {[F9921040](https://archive.blender.org/developer/F9921040/spreadsheet_components_per_domain_a.png) size="full"} |
Author
Owner

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Owner

Added subscriber: @dfelinto

Added subscriber: @dfelinto
Member

Added subscriber: @FabianSchempp

Added subscriber: @FabianSchempp
Member
{F9921036 size="full"} {F9921040 size="full"}
| {[F9921036](https://archive.blender.org/developer/F9921036/spreadsheet_components_per_domain_b.png) size="full"} | {[F9921040](https://archive.blender.org/developer/F9921040/spreadsheet_components_per_domain_a.png) size="full"} | | -- | -- |

Added subscriber: @someuser

Added subscriber: @someuser

In #86886#1141258, @FabianSchempp wrote:
| {F9921036 size="full"} | {F9921040 size="full"} |

Corner -> Face Corner

> In #86886#1141258, @FabianSchempp wrote: > | {[F9921036](https://archive.blender.org/developer/F9921036/spreadsheet_components_per_domain_b.png) size="full"} | {[F9921040](https://archive.blender.org/developer/F9921040/spreadsheet_components_per_domain_a.png) size="full"} | Corner -> Face Corner
Author
Owner

Hi @FabianSchempp 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 @FabianSchempp 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.
Member

In #86886#1144953, @dfelinto wrote:
Hi @FabianSchempp 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

  • ...

> In #86886#1144953, @dfelinto wrote: > Hi @FabianSchempp 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 - > ...
Author
Owner

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Dalai Felinto self-assigned this 2021-04-26 12:18:54 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#86886
No description provided.