UI Design: Title Bar Format #102794

Open
opened 2022-11-26 19:54:36 +01:00 by Harley Acheson · 19 comments
Member

In the near future we will start to better differentiate between Blender versions in order to aid users who run multiple versions simultaneously:

{F13972120,width=100%}

{F13972101,width=100%}

This makes it a good time to consider adding the Blender version to the title bar to help differentiate running versions. Currently the longest form of the title bar text looks like this:

{F13972103,width=100%}

It is without version numbers. The asterisk that indicates that the file is "dirty" is anchored to the program name. The file path is in (odd) square brackets, which looks especially messy when the file has been recovered.

I propose that we include the version number. Major and Minor version and only add patch version if non-zero. Append Greek small letter alpha "α" in early Bcon stages, small letter beta "β" in beta stages.

Separate the Blender name and version from the file path portions with SPACE - EN DASH - SPACE. The en dash is used traditionally as a sentence-level pause or interrupter.

Do not surround the path with any brackets.

Move the "file is dirty" indicator to the end.

This results in the following examples:

{F13972111,width=100%}

{F13972113,width=100%}

{F13972115,width=100%}

The above just deals with files that have been saved at one time. But what to display before any saving has occurred? Currently we always just show "Blender" regardless if the file is dirty or not, even though we do know its dirty state.

I'd be inclined to show only the name and version if unsaved and unchanged, so initial loading state:

{F13973733,width=100%}

But once any changes are made, display it as:

{F13973726,width=100%}

In the near future we will start to better differentiate between Blender versions in order to aid users who run multiple versions simultaneously: {[F13972120](https://archive.blender.org/developer/F13972120/image.png),width=100%} {[F13972101](https://archive.blender.org/developer/F13972101/image.png),width=100%} This makes it a good time to consider adding the Blender version to the title bar to help differentiate running versions. Currently the longest form of the title bar text looks like this: {[F13972103](https://archive.blender.org/developer/F13972103/image.png),width=100%} It is without version numbers. The asterisk that indicates that the file is "dirty" is anchored to the program name. The file path is in (odd) square brackets, which looks especially messy when the file has been recovered. I propose that we include the version number. Major and Minor version and only add patch version if non-zero. Append Greek small letter alpha "α" in early Bcon stages, small letter beta "β" in beta stages. Separate the Blender name and version from the file path portions with SPACE - EN DASH - SPACE. The en dash is used traditionally as a sentence-level pause or interrupter. Do not surround the path with any brackets. Move the "file is dirty" indicator to the end. This results in the following examples: {[F13972111](https://archive.blender.org/developer/F13972111/image.png),width=100%} {[F13972113](https://archive.blender.org/developer/F13972113/image.png),width=100%} {[F13972115](https://archive.blender.org/developer/F13972115/image.png),width=100%} The above just deals with files that have been saved at one time. But what to display *before* any saving has occurred? Currently we always just show "Blender" regardless if the file is dirty or not, even though we do know its dirty state. I'd be inclined to show only the name and version if unsaved and unchanged, so initial loading state: {[F13973733](https://archive.blender.org/developer/F13973733/image.png),width=100%} But once *any* changes are made, display it as: {[F13973726](https://archive.blender.org/developer/F13973726/image.png),width=100%}
Harley Acheson self-assigned this 2022-11-26 19:54:36 +01:00
Author
Member

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

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Member

Added subscriber: @Harley

Added subscriber: @Harley
Author
Member
Added subscribers: @ideasman42, @pablovazquez, @HooglyBoogly, @brecht, @JulianEisel

I don't think we should include the version number in the title. Some distinction between alpha/beta and release seems reasonable, but I think this is too much clutter when scanning over multiple window titles looking for the right blend file.

I don't think we should include the version number in the title. Some distinction between alpha/beta and release seems reasonable, but I think this is too much clutter when scanning over multiple window titles looking for the right blend file.
Author
Member

Our competitors show such things as "Autodesk 3ds Max 2018", "Autodesk Maya 2019", "CINEMA 4D R16.050 Broadcast (R16)" in title, along with the full path just like us.

Our competitors show such things as "Autodesk 3ds Max 2018", "Autodesk Maya 2019", "CINEMA 4D R16.050 Broadcast (R16)" in title, along with the full path just like us.

Right, but I don't think that's great, and plenty of other apps don't show the version number.

Right, but I don't think that's great, and plenty of other apps don't show the version number.

Added subscriber: @DuarteRamos

Added subscriber: @DuarteRamos

I wouldn't mind seeing version numbers in the title bar as well, it helps in a lot of situations when running multiple installs in parallel, testing different builds or diagnosing issues remotely from screenshots.
But I can see how it may add some clutter.

Would making window titles reachable though the python API somehow make it any better? Maybe (part of) it could be customized through scripting by combining strings, accessible through preferences.
"Blender" + Version + Save_State + Blend_Full_Path + "Random User String

I wouldn't mind seeing version numbers in the title bar as well, it helps in a lot of situations when running multiple installs in parallel, testing different builds or diagnosing issues remotely from screenshots. But I can see how it may add some clutter. Would making window titles reachable though the python API somehow make it any better? Maybe (part of) it could be customized through scripting by combining strings, accessible through preferences. `"Blender" + Version + Save_State + Blend_Full_Path + "Random User String`
Author
Member

@brecht - ...too much clutter when scanning over multiple window titles looking for the right blend file.

We might be looking at this quite differently. I see the top of these two samples being far more cluttered and harder to quickly read the file path:

{F13977032,width=100%}

> @brecht - ...too much clutter when scanning over multiple window titles looking for the right blend file. We might be looking at this quite differently. I see the *top* of these two samples being **far more** cluttered and harder to quickly read the file path: {[F13977032](https://archive.blender.org/developer/F13977032/image.png),width=100%}

Added subscriber: @Nurb2Kea

Added subscriber: @Nurb2Kea

On MacOS it looks like this and all the info is there already!
Screenshot 2022-11-29 at 1.49.56 am.jpg
right mouse click to see the path structure
Screenshot 2022-11-29 at 1.57.07 am.jpg

Statusbar (blender version):
Screenshot 2022-11-29 at 1.51.40 am.jpg

Looks clean and compact with all info needed.
Just an idea to keep it simple and consistant between Linux, Mac & Windows etc...

On MacOS it looks like this and all the info is there already! ![Screenshot 2022-11-29 at 1.49.56 am.jpg](https://archive.blender.org/developer/F13977070/Screenshot_2022-11-29_at_1.49.56_am.jpg) right mouse click to see the path structure ![Screenshot 2022-11-29 at 1.57.07 am.jpg](https://archive.blender.org/developer/F13977080/Screenshot_2022-11-29_at_1.57.07_am.jpg) Statusbar (blender version): ![Screenshot 2022-11-29 at 1.51.40 am.jpg](https://archive.blender.org/developer/F13977073/Screenshot_2022-11-29_at_1.51.40_am.jpg) Looks clean and compact with all info needed. Just an idea to keep it simple and consistant between Linux, Mac & Windows etc...

Added subscriber: @triget

Added subscriber: @triget

In #102794#1452644, @brecht wrote:
Right, but I don't think that's great, and plenty of other apps don't show the version number.

This is faulty thinking. Displaying the program version in the bar avoids many problems such as switching versions. There is no need to look in other windows to see what version of Blender we have installed.

> In #102794#1452644, @brecht wrote: > Right, but I don't think that's great, and plenty of other apps don't show the version number. This is faulty thinking. Displaying the program version in the bar avoids many problems such as switching versions. There is no need to look in other windows to see what version of Blender we have installed.

Added subscriber: @jacek007g

Added subscriber: @jacek007g

In #102794#1452800, @Harley wrote:

@brecht - ...too much clutter when scanning over multiple window titles looking for the right blend file.

We might be looking at this quite differently. I see the top of these two samples being far more cluttered and harder to quickly read the file path:

{F13977032,width=100%}

It looks way cleaner and better than old version. Especially the asterisk on the end of the line - it's a lot more visible status of the file.
However I think that it would be better to use Latin minor "a" and "b" than Greek letters.

> In #102794#1452800, @Harley wrote: >> @brecht - ...too much clutter when scanning over multiple window titles looking for the right blend file. > > We might be looking at this quite differently. I see the *top* of these two samples being **far more** cluttered and harder to quickly read the file path: > > {[F13977032](https://archive.blender.org/developer/F13977032/image.png),width=100%} It looks way cleaner and better than old version. Especially the asterisk on the end of the line - it's a lot more visible status of the file. However I think that it would be better to use Latin minor "a" and "b" than Greek letters.
Contributor

Added subscriber: @persun

Added subscriber: @persun

Added subscriber: @Grady

Added subscriber: @Grady

What about this format:

ICON FILENAME (STATUS) - FOLDER - BLENDER_VERSION

Where:

ICON Is the Blender icon (represented by - [x] in this comment)
FILENAME Is the name of the file including the extension.
STATUS Is the status of the file if it is recovered/unsaved/etc.
FOLDER Is the folder path where the file is located
BLENDER_VERSION Is the name and version of Blender

With one additional change, instead of using an asterisk to represent 'unsaved', we use a text label to be more explicit in the communication.

So instead of:

*- [x] Blender 3.5 - C:\Users\John\Documents\Blends\Example.blend We could have:- [x] Example.blend (Unsaved) - C:\Users\John\Documents\Blends - Blender 3.5β

The logic for putting the filename first is - If you have multiple versions of Blender open, and you're looking at your taskbar to find a specific file you have open to switch to, what are you going to be looking for? Probably the filename of the Blend file in the title. But with that all the way at the end of the window title, the only way to see that would be to hover your mouse over each individual Blend file to see the filename in the hovertext.

And if you need to put your cursor over each taskbar icon anyway you might as well click on them instead, since there's a delay while waiting for the hovertext that is slower than clicking on the window to switch to it.

For example:

Capture.PNG

Putting the filename at the start would resolve that. You don't really 'need' the application name at the start, because it's fairly obvious what the application is by the orange Blender icon.

What about this format: ICON FILENAME (STATUS) - FOLDER - BLENDER_VERSION Where: | ICON | Is the Blender icon (represented by - [x] in this comment) | -- | -- | | FILENAME | Is the name of the file including the extension. | STATUS | Is the status of the file if it is recovered/unsaved/etc. | FOLDER | Is the folder path where the file is located | BLENDER_VERSION | Is the name and version of Blender With one additional change, instead of using an asterisk to represent 'unsaved', we use a text label to be more explicit in the communication. So instead of: **- [x] Blender 3.5 - C:\Users\John\Documents\Blends\Example.blend ***We could have:**- [x] Example.blend (Unsaved) - C:\Users\John\Documents\Blends - Blender 3.5β** The logic for putting the filename first is - If you have multiple versions of Blender open, and you're looking at your taskbar to find a specific file you have open to switch to, what are you going to be looking for? Probably the filename of the Blend file in the title. But with that all the way at the end of the window title, the only way to see that would be to hover your mouse over each individual Blend file to see the filename in the hovertext. And if you need to put your cursor over each taskbar icon anyway you might as well click on them instead, since there's a delay while waiting for the hovertext that is slower than clicking on the window to switch to it. For example: ![Capture.PNG](https://archive.blender.org/developer/F14051427/Capture.PNG) Putting the filename at the start would resolve that. You don't really 'need' the application name at the start, because it's fairly obvious what the application is by the orange Blender icon.

Is there any new information regarding this change? It's a quick task that will help a lot of users (it's cursory to prioritize these changes, because it should have been fixed a long time ago) and it doesn't make sense to wait "5 years" again for any changes.

Is there any new information regarding this change? It's a quick task that will help a lot of users (it's cursory to prioritize these changes, because it should have been fixed a long time ago) and it doesn't make sense to wait "5 years" again for any changes.
Thomas Dinges added this to the 3.5 milestone 2023-02-07 18:55:56 +01:00
Brecht Van Lommel removed this from the 3.5 milestone 2023-02-09 19:33:02 +01:00
Philipp Oeser removed the
Interest
User Interface
label 2023-02-10 09:21:27 +01:00
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
8 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#102794
No description provided.