For reference: https://devtalk.blender.org/t/proposal-ui-remove-properties-area-from-the-default-vse-ui/16656

As Blender currently is designed, all things 3d are first class citizens, and all other editors and their objects aren't. By exposing the object properties of all other editors in the general Properties, Blender is one step closer to integrating the otherwise somewhat standalonish editors into the UI design of the main part of Blender(On the functional side ex. the Compositor and VSE still needs much better and faster integration in the 3D workings).

However, there are several things concerning this suggested change which needs to be discussed ex.:

• In the name of consistency, does this change mean that all editors with "objects" will get the properties exposed in the Properties "Editor"?
• If that is the case, should each editor have a property tab of their own? How can that be done without cluttering the Properties even more than they are now?
• If there are objects in the 3d view, but the workspace is Video Editing, all of the 3d property tabs are exposed, so in the current layout, you won't even see the VSE tab:

• When starting Blender in Video Editing, there are multiple irrelevant 3d properties exposed in the Property editor, are these going to be cleaned out depending on each Workspace, so only the relevant will be exposed?
• Is it a durable workflow to working with ex. NLA + 3D view, Node Editor + 3D View or VSE + Graph Editor "objects" to switch tab in Properties, everytime users need to change an editor related property?
• Since this suggestion is only moving the properties of the active "object" to the sidebar all the other properties are still exposed in the sidebar, and users will easily end up with many sidebars all over the screen anyway, so no screen estate might be saved anyway?

• Is that considered better than exposing the same properties in Sequencer & Preview view mode, in just a single sidebar? (Render settings are exposed already in a workspace tab, and could also be integrated in the sidebar of a filebrowser pop-up for render sequencer animation(like Render Audio): https://devtalk.blender.org/t/proposal-ui-remove-properties-area-from-the-default-vse-ui/16656)

In the actual, I guess preliminary, implementation, the strip name and modifiers and single file proxy(relating to active strip too), properly needs to be moved into properties too. The only properties left in the Sequencer sidebar should be "Sequencer" properties, and no strip properties?

There might be several additional UI and functional problems which needs to be mapped out, before deciding to do this. Normally contributors are forced to do a devtalk thread on things needing discussion, isn't that the case in this situation too, though it is initiated by BF devs?

For some reason, the moving of properties into the "Properties Editor", is seen as connected with a menu context problem in Sequencer & Preview view mode, which imo should be solved independently, and not by trashing the valuable "Sequencer & Preview" view mode. These things needs to be separated and discussed properly each and everyone of them.

If you want to do this, all properties of the active strip need to be moved into Properties including Modifiers, Strip Cache and Strip Proxy, and it will also affect all editors with object properties like curves, nla strips, images, movie clips, nodes, etc. which also should be moved, but as mentioned above this really needs to be properly discussed beforehand.

While I think this the right direction, it would be good to have an overall, cross-module design decision to be signed off before implementation. The concept of "properties" editing using the properties editor could be applied to other aspects of Blender (f-curve for example). I see @Peter Fog (tintwotin) already raised some points related to this, maybe he has time to come up with a succinct design spec?

In D13165#351754, @Francesco Siddi (fsiddi) wrote:

While I think this the right direction, it would be good to have an overall, cross-module design decision to be signed off before implementation. The concept of "properties" editing using the properties editor could be applied to other aspects of Blender (f-curve for example). I see @Peter Fog (tintwotin) already raised some points related to this, maybe he has time to come up with a succinct design spec?

This is going to be a quite big change, touching pretty much all editors of Blender, so I think the only way to deal with is that you guys to have a design meeting at the Blender Studio and discuss this in detail. Personally, I think the Sequencer/Preview is that superior to the current Video Editing workspace that it should replace it, and the menu context challenges should be solved(this is really a small problem).