Spreadsheet: refactor data set drawing #125239

Merged
Jacques Lucke merged 1 commits from JacquesLucke/blender:refactor-spreadsheet-dataset-drawing into main 2024-07-22 18:30:14 +02:00
Member

This separates a single GeometryDataSetTreeViewItem into separate tree view items for the individual parts of the tree view. While requiring a bit more boilerplate overall, this simplifies the code quite a bit and makes it more extensible.

This was already reviewed as part of #124186.

This separates a single `GeometryDataSetTreeViewItem` into separate tree view items for the individual parts of the tree view. While requiring a bit more boilerplate overall, this simplifies the code quite a bit and makes it more extensible. This was already reviewed as part of #124186.
Jacques Lucke added 1 commit 2024-07-22 17:41:46 +02:00
refactor
All checks were successful
buildbot/vexp-code-patch-lint Build done.
buildbot/vexp-code-patch-linux-x86_64 Build done.
buildbot/vexp-code-patch-darwin-x86_64 Build done.
buildbot/vexp-code-patch-windows-amd64 Build done.
buildbot/vexp-code-patch-coordinator Build done.
1c5746f243
Author
Member

@blender-bot build

@blender-bot build
Jacques Lucke merged commit 9974ee71bd into main 2024-07-22 18:30:14 +02:00
Jacques Lucke deleted branch refactor-spreadsheet-dataset-drawing 2024-07-22 18:30:18 +02:00
Member

Have you considered using ui::BasicTreeViewItem as base class? It can help avoid some bolierplate, by default it just adds a label with an optional icon.

Although the extra level of inheritance is not so nice.

Have you considered using `ui::BasicTreeViewItem` as base class? It can help avoid some bolierplate, by default it just adds a label with an optional icon. Although the extra level of inheritance is not so nice.
Author
Member

I haven't really, and I'm also not sure I'd prefer it. Using BasicTreeViewItem here potentially creates a bit of a diamond on the parent hierarchy, also I kinda like that all the tree view items in this file just have simple drawing code and are more uniform in this way.

I haven't really, and I'm also not sure I'd prefer it. Using `BasicTreeViewItem` here potentially creates a bit of a diamond on the parent hierarchy, also I kinda like that all the tree view items in this file just have simple drawing code and are more uniform in this way.
Member

BasicTreeViewItem would be used as the base class instead of AbstractTreeView, it's not a mix-in.

(Really just checking, I'm completely fine with not using it. No need to justify even :) )

`BasicTreeViewItem` would be used as the base class instead of `AbstractTreeView`, it's not a mix-in. (Really just checking, I'm completely fine with not using it. No need to justify even :) )
Sign in to join this conversation.
No reviewers
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
2 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#125239
No description provided.