Status bar for spreadsheet editor #86142

Closed
opened 2021-03-01 15:18:40 +01:00 by Dalai Felinto · 6 comments

See #86027.

On the right we have:
Rows: rows / total rows | Columns: col / total_cols
(e.g., Rows: 2 / 10 | Columns: 3 / 15)


Less important:

On the left we have:
Row Name | Column Name | Data Type | Full Value
(e.g., "24 | Mask | Float | 0.23423423432")

See #86027. On the right we have: Rows: rows / total rows | Columns: col / total_cols (e.g., Rows: 2 / 10 | Columns: 3 / 15) --- Less important: On the left we have: Row Name | Column Name | Data Type | Full Value (e.g., "24 | Mask | Float | 0.23423423432")
Author
Owner

Added subscriber: @dfelinto

Added subscriber: @dfelinto
Jacques Lucke self-assigned this 2021-03-11 12:26:42 +01:00
Member

Added subscribers: @brecht, @HooglyBoogly

Added subscribers: @brecht, @HooglyBoogly
Member

Here I go with a dissenting opinion again...

I was going to post this in the patch, but in the interest of staying on topic there I'll put it here. I'm heading in a similar vein as @brecht's feedback (an mine) on the initial design.
Mainly, surrounding the actual data with UI regions on all four sides just feels like too much to me. The footer specifically feels more unnecessary than the others.

  • The row name would always be displayed by the "on top" index column.
  • Similarly, the column name is always displayed
  • I'm not sure of the purpose of always seeing the total number of columns.
  • Other data can be displayed differently-- the full value with precision controls, tooltips, the data type with a tooltip, etc.
  • The number of filtered columns is indeed a bit harder to display without a status bar, but there are other places to put the information.

So be it if we move forward with this design anyway, I just wanted to write this down.

Here I go with a dissenting opinion again... I was going to post this in the patch, but in the interest of staying on topic there I'll put it here. I'm heading in a similar vein as @brecht's feedback (an mine) on the initial design. Mainly, surrounding the actual data with UI regions on all four sides just feels like too much to me. The footer specifically feels more unnecessary than the others. - The row name would always be displayed by the "on top" index column. - Similarly, the column name is always displayed - I'm not sure of the purpose of always seeing the total number of columns. - Other data can be displayed differently-- the full value with precision controls, tooltips, the data type with a tooltip, etc. - The number of filtered columns is indeed a bit harder to display without a status bar, but there are other places to put the information. So be it if we move forward with this design anyway, I just wanted to write this down.

This issue was referenced by b617b44419

This issue was referenced by b617b44419613ae87d64b5d4692515750c83b417
Author
Owner

Moving this to done, but poked Jacques via chat that we need comma separator for thousands/millions

Moving this to done, but poked Jacques via chat that we need comma separator for thousands/millions
Author
Owner

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

Changed status from 'Needs Triage' to: 'Resolved'
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#86142
No description provided.