Confusing Link/Append interface #41593

Closed
opened 2014-08-26 15:50:44 +02:00 by Francesco Siddi · 24 comments

Hello,
I would like to get a more formal discussion going on how to address the following situation: the Link/Append workflow has been modified (the Append checkbox has been removed from the operator panel), but the panel and the button still show a Link/Append label.

As an alternative to bringing the checkbox back, I would propose to name the button and the panel according to the action chosen (Link OR Append). This will solve confusion and frustration for users not using the File... menu.

Any feedback is appreciated.

Hello, I would like to get a more formal discussion going on how to address the following situation: the Link/Append workflow has been modified (the Append checkbox has been removed from the operator panel), but the panel and the button still show a Link/Append label. As an alternative to bringing the checkbox back, I would propose to name the button and the panel according to the action chosen (Link OR Append). This will solve confusion and frustration for users not using the File... menu. Any feedback is appreciated.
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez
Member

Added subscribers: @JonathanWilliamson, @ideasman42

Added subscribers: @JonathanWilliamson, @ideasman42
Member

Adding you both (Jonathan + Campbell) to discuss this, I think this is something to try to fix before release.

I don't support the decision taken time ago about removing the option to Link or Append. It only worsened the issue.

Additionally, it would help communication if we could have the Link/Append button in the file browser to actually display "Link" or "Append" if this is the case. If this is too complicated maybe we could try to find a way for the UI to help in that case. Bring back the Link | Append in the shape of a radio button? So is more prominent.

Open to ideas!

Adding you both (Jonathan + Campbell) to discuss this, I think this is something to try to fix before release. I don't support the decision taken time ago about removing the option to Link or Append. It only worsened the issue. Additionally, it would help communication if we could have the Link/Append button in the file browser to actually display "Link" or "Append" if this is the case. If this is too complicated maybe we could try to find a way for the UI to help in that case. Bring back the Link | Append in the shape of a radio button? So is more prominent. Open to ideas!

I think I missed some commits somewhere, what was actually changed with Link/Append? I just tested against 70a4942 and neither Link or Append (from the File menu) show anything in the Operator panel. It doesn't even register an operator: http://cl.ly/XDJy

I think I missed some commits somewhere, what was actually changed with Link/Append? I just tested against 70a4942 and neither Link or Append (from the File menu) show anything in the Operator panel. It doesn't even register an operator: http://cl.ly/XDJy

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges
Member

@JonathanWilliamson Some time ago the "Link" checkbox on the sidebar was removed when Linking/Appending. If you use the shortcut to Link, or the shortcut to Append, the File Browser looks exactly the same and there is no way to tell them apart.

When we had the "Link" checkbox, you would know what you were about to do.

Ref-FileBrowser-Panels-LinkAppend.png

I vote to revert this change, bring back the checkbox for release, until we propose a better UI for Linking/Appending (also related to the Asset Manager project)

@JonathanWilliamson Some time ago the "Link" checkbox on the sidebar was removed when Linking/Appending. If you use the shortcut to Link, or the shortcut to Append, the File Browser looks exactly the same and there is no way to tell them apart. When we had the "Link" checkbox, you would know what you were about to do. ![Ref-FileBrowser-Panels-LinkAppend.png](https://archive.blender.org/developer/F107028/Ref-FileBrowser-Panels-LinkAppend.png) I vote to revert this change, bring back the checkbox for release, until we propose a better UI for Linking/Appending (also related to the Asset Manager project)

Oh well that's super crappy.

Seems to me there's a few options:

  • Add radio button for choosing link or append
  • Make panel and button context-senstive to the action chosen, such that it always correctly displays the right label

Make Link and Append separate operators

The third option is pretty bad I suspect, since it'd likely add code duplication (assuming here). I feel that option 2 may be the best. At least in my own workflow I have never, that I can remember, used the checkbox to switch between link/append. I always specify the exact option I want from the menu or hotkey.

Oh well that's super crappy. Seems to me there's a few options: - Add radio button for choosing link or append - Make panel and button context-senstive to the action chosen, such that it always correctly displays the right label # Make Link and Append separate operators The third option is pretty bad I suspect, since it'd likely add code duplication (assuming here). I feel that option 2 may be the best. At least in my own workflow I have never, that I can remember, used the checkbox to switch between link/append. I always specify the exact option I want from the menu or hotkey.
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Added subscriber: @elubie

Added subscriber: @elubie
Member

Actually, the third option is the most straight forward in the code. the duplication would only consist of a single function, as the exec and poll functions for the operator can still be used.

Alternatively, I think it might be possible to additionally set the operator name to Link only if linking and Append when appending. I suppose that is all that would be needed from the UI side.

Actually, the third option is the most straight forward in the code. the duplication would only consist of a single function, as the exec and poll functions for the operator can still be used. Alternatively, I think it might be possible to additionally set the operator name to Link only if linking and Append when appending. I suppose that is all that would be needed from the UI side.
Member

Added subscriber: @zanqdo

Added subscriber: @zanqdo
Member

I would prefer if the link option be brought back, it was very flexible and imo, clearer that way and the reason it was taken out never seemed really valid (some user not reading the manual)

best regards

I would prefer if the link option be brought back, it was very flexible and imo, clearer that way and the reason it was taken out never seemed really valid (some user not reading the manual) best regards
Member

Ok, I wrote patch to separate the operators in case the consensus is to not bring the link option back.

Let me know what you guys propose, I'll take a look Wednesday (in 3 days) latest.

Ok, I wrote patch to separate the operators in case the consensus is to not bring the link option back. Let me know what you guys propose, I'll take a look Wednesday (in 3 days) latest.

Personally I prefer the Separate Operators option as these are really quite different tools that are not as interchangeable as they seem (in my opinion). For example, when linking there are currently settings displays that don't apply to appending, such as setting Relative or Absolute Path. This just muddies it.

Personally I prefer the Separate Operators option as these are really quite different tools that are not as interchangeable as they seem (in my opinion). For example, when linking there are currently settings displays that don't apply to appending, such as setting Relative or Absolute Path. This just muddies it.

Added subscriber: @piiichan

Added subscriber: @piiichan
Author
Member

Added subscriber: @fsiddi

Added subscriber: @fsiddi
Author
Member

Thanks everybody for discussing this! I think what @JonathanWilliamson suggest is a good enough solution (which is what @elubie implemented).

Thanks everybody for discussing this! I think what @JonathanWilliamson suggest is a good enough solution (which is what @elubie implemented).

Added subscriber: @ClaasKuhnen

Added subscriber: @ClaasKuhnen

In #41593#20, @JonathanWilliamson wrote:
Personally I prefer the Separate Operators option as these are really quite different tools that are not as interchangeable as they seem (in my opinion). For example, when linking there are currently settings displays that don't apply to appending, such as setting Relative or Absolute Path. This just muddies it.

Somewhat true. I would like to point to something I observed with Fusion 360. Rhino 3D is great has many tools but for nearly each tool option they have a separate tool entry bloating up the menus. Fusion in contrast by logic combines tools into well lets say an ueber tool. And in my workflow I started to appreciate this a lot. Less searching - less scrolling ...

Link and append to a certain degree do different things. Appending is more an import function - while link just creates well a link, imports nothing.
But a linked data you can make local in Blender as well. Now currently I work a lot with Revit and architects and they either import DATA or link it dynamically into the scene. Both commands are called out differently.

Personally I would prefer link and append to be fused into a single command, but I am sure listing them separately will work well as well.

However what maybe should be considered is the order in the menu.
Currently it looks like this:

new open recovery stuff
save save as
preferences factory settings
append link
import export
external data

and I feel this might make more sense
new open
save save as
link append import export (should be one block because it deals with data transfers)
external data
preferences factory settings

preferences factory settings etc are buttons I always need to move my mouse over when I go to the export menu, something I do a lot because I heavily work in different cad applications while working on the same project.

preferences are really the least often used and thus should be at the end of the list.

> In #41593#20, @JonathanWilliamson wrote: > Personally I prefer the Separate Operators option as these are really quite different tools that are not as interchangeable as they seem (in my opinion). For example, when linking there are currently settings displays that don't apply to appending, such as setting Relative or Absolute Path. This just muddies it. Somewhat true. I would like to point to something I observed with Fusion 360. Rhino 3D is great has many tools but for nearly each tool option they have a separate tool entry bloating up the menus. Fusion in contrast by logic combines tools into well lets say an ueber tool. And in my workflow I started to appreciate this a lot. Less searching - less scrolling ... Link and append to a certain degree do different things. Appending is more an import function - while link just creates well a link, imports nothing. But a linked data you can make local in Blender as well. Now currently I work a lot with Revit and architects and they either import DATA or link it dynamically into the scene. Both commands are called out differently. Personally I would prefer link and append to be fused into a single command, but I am sure listing them separately will work well as well. However what maybe should be considered is the order in the menu. Currently it looks like this: new open recovery stuff save save as preferences factory settings append link import export external data and I feel this might make more sense new open save save as link append import export (should be one block because it deals with data transfers) external data preferences factory settings preferences factory settings etc are buttons I always need to move my mouse over when I go to the export menu, something I do a lot because I heavily work in different cad applications while working on the same project. preferences are really the least often used and thus should be at the end of the list.

Added subscriber: @hewi

Added subscriber: @hewi
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Andrea Weikert self-assigned this 2014-09-04 19:40:06 +02:00
Member

Closed by committing D770.

Closed by committing [D770](https://archive.blender.org/developer/D770).

Added subscriber: @michaelknubben

Added subscriber: @michaelknubben
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
11 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#41593
No description provided.