UI: Tab filtering for properties editor #115626

New Issue

Open

opened 2023-11-30 19:51:10 +01:00 by Richard Antalik · 6 comments

Richard Antalik commented

2023-11-30 19:51:10 +01:00

Member

Some time ago, I suggested to move sequencer properties to properties editor as a solution for #92584. There has been discussion on how to deal with noise of having sequencer data present with non VSE workflows and vice versa. I proposed implementation of filtering for what is visible in properties editor. Even though my goal is oriented towards VSE, it may allow to simplify interface for particular workflows.

On user level, I would implement this similar to outliner. The filtering would be done per editor, so each workspace could have set of items that is visible by default.

Perhaps it may not be good idea to use this feature for modelling workflows due to muscle memory. I would still propose this for specific workflows like video editing where practically only output properties, strip data and modifiers are needed.

This has been discussed briefly at HQ with @fsiddi and @pablovazquez, but I would like to discuss details or possible limitations this would pose. Code wise, this seems to be fairly simple, at least for bare functionality. I have created WIP patch !115624.

Some time ago, I suggested to move sequencer properties to properties editor as a solution for #92584. There has been discussion on how to deal with noise of having sequencer data present with non VSE workflows and vice versa. I proposed implementation of filtering for what is visible in properties editor. Even though my goal is oriented towards VSE, it may allow to simplify interface for particular workflows. On user level, I would implement this similar to outliner. The filtering would be done per editor, so each workspace could have set of items that is visible by default. ![Untitled.png](/attachments/4c8cdad8-a758-46bd-afe8-b6c8a81b34e6) Perhaps it may not be good idea to use this feature for modelling workflows due to muscle memory. I would still propose this for specific workflows like video editing where practically only output properties, strip data and modifiers are needed. This has been discussed briefly at HQ with @fsiddi and @pablovazquez, but I would like to discuss details or possible limitations this would pose. Code wise, this seems to be fairly simple, at least for bare functionality. I have created WIP patch !115624.

Untitled.png

48 KiB

👍 2 ❤️ 2

Richard Antalik added the

Video Sequencer

labels 2023-11-30 19:51:11 +01:00

Richard Antalik referenced this issue

2023-11-30 19:51:29 +01:00

WIP: Use filtering for properties editor #115624

Nika Kutsniashvili commented

2023-11-30 23:50:18 +01:00

Contributor

If default startup file is correctly filtered so that there is no visible changes for users, I don't see how that can be bad idea. It keeps existing workflow for users, but gives more customization ability to those who are interested.

I have seen multiple examples, where people, especially in studios are not happy with how overwhelming Blender is sometimes, when you just need it for one specific workflow. In fact, I have seen addons/configurations that simplify Blender with purpose to make it just able to one task, for example in interior visualization.

This can be good solution towards that path and I think people will welcome this change, especially since Blender Apps is being delayed.

If default startup file is correctly filtered so that there is no visible changes for users, I don't see how that can be bad idea. It keeps existing workflow for users, but gives more customization ability to those who are interested. I have seen multiple examples, where people, especially in studios are not happy with how overwhelming Blender is sometimes, when you just need it for one specific workflow. In fact, I have seen addons/configurations that simplify Blender with purpose to make it just able to one task, for example in interior visualization. This can be good solution towards that path and I think people will welcome this change, especially since Blender Apps is being delayed.

Brecht Van Lommel commented

2024-01-17 12:25:24 +01:00

Owner

On the design level, this setting is related to what is in the Workspace panel in the tool properties, where you can configure the workspace mode and add-ons. I think in some way this makes more sense as a workspace setting rather than a setting of the properties editor. For add-ons it's already effectively a control to hide certain panels and tabs.

If it has to be a setting in the properties editor, I think the filter icon in the header is not the right metaphor. In other editors this controls which data is shown, e.g. based on selection state or object type. I think that is a quite different thing, and would not use the same icon for that and potentially confuse things. I would probably move it into the little arrow menu right next to it instead of making it this prominent.

On the design level, this setting is related to what is in the Workspace panel in the tool properties, where you can configure the workspace mode and add-ons. I think in some way this makes more sense as a workspace setting rather than a setting of the properties editor. For add-ons it's already effectively a control to hide certain panels and tabs. If it has to be a setting in the properties editor, I think the filter icon in the header is not the right metaphor. In other editors this controls which data is shown, e.g. based on selection state or object type. I think that is a quite different thing, and would not use the same icon for that and potentially confuse things. I would probably move it into the little arrow menu right next to it instead of making it this prominent.

Francesco Siddi commented

2024-01-21 18:42:49 +01:00

Member

Thank you Brecht for this feedback. Making this a Workspace related feature is aligned with Blender's current design and perhaps the best way forward.

An alternative would be to simply display the "Strip" properties tab once a strip is selected in the VSE.

In any case, I would suggest creating only one tab, and place all the information there (merging the content of Strip and Modifiers from the VSE area).

Thank you Brecht for this feedback. Making this a Workspace related feature is aligned with Blender's current design and perhaps the best way forward. An alternative would be to simply display the "Strip" properties tab once a strip is selected in the VSE. In any case, I would suggest creating only one tab, and place all the information there (merging the content of Strip and Modifiers from the VSE area).

ThinkingPolygons commented

2024-01-21 19:53:59 +01:00

this makes more sense as a workspace setting

probably im missing something, but if i have more than one properties editor in my workspace and i wanted each one of them do display a differnt set of panels, would it work if this was a workspace setting?
as a workspace setting wouldn't it affect all the properties editors? 🤔

> this makes more sense as a workspace setting probably im missing something, but if i have more than one properties editor in my workspace and i wanted each one of them do display a differnt set of panels, would it work if this was a workspace setting? as a workspace setting wouldn't it affect all the properties editors? 🤔

Richard Antalik commented

2024-01-23 16:48:25 +01:00

Author

Member

I am fine with making this workspace setting and making the filter "bit more hidden".

this makes more sense as a workspace setting

probably im missing something, but if i have more than one properties editor in my workspace and i wanted each one of them do display a differnt set of panels, would it work if this was a workspace setting?
as a workspace setting wouldn't it affect all the properties editors? 🤔

It would affect all properties editors. I guess I can see why you would want to have multiple editors with different sets of tabs, but don't think making this workspace setting would be limiting. I would imagine, that you would do this to avoid switching tabs anyway.

In any case, I would suggest creating only one tab, and place all the information there (merging the content of Strip and Modifiers from the VSE area).

I can do this to start with, but personally I would like to have a game plan for using modifier tab. Being able to use current modifier tab would be nice I think.

I am fine with making this workspace setting and making the filter "bit more hidden". > > this makes more sense as a workspace setting > > probably im missing something, but if i have more than one properties editor in my workspace and i wanted each one of them do display a differnt set of panels, would it work if this was a workspace setting? > as a workspace setting wouldn't it affect all the properties editors? 🤔 It would affect all properties editors. I guess I can see why you would want to have multiple editors with different sets of tabs, but don't think making this workspace setting would be limiting. I would imagine, that you would do this to avoid switching tabs anyway. > In any case, I would suggest creating only one tab, and place all the information there (merging the content of Strip and Modifiers from the VSE area). I can do this to start with, but personally I would like to have a game plan for using modifier tab. Being able to use current modifier tab would be nice I think.

ThinkingPolygons commented

2024-01-23 20:09:46 +01:00

don't think making this workspace setting would be limiting

sounds quite limiting to me ☹️

> don't think making this workspace setting would be limiting sounds quite limiting to me ☹️

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

5 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#115626

No description provided.