Separation of Timeline Display and Scrolling Options #143

Open
opened 2026-06-02 15:48:50 +00:00 by nienty · 2 comments
nienty commented 2026-06-02 15:48:50 +00:00 (Migrated from codeberg.org)

I would like to suggest an improvement to the timeline settings.

Currently, a single option controls both the position of new messages (top or bottom) and the scrolling behavior, including the placement of the top and bottom navigation menus. As a result, these different interface behaviors are tied together.

I would like to propose splitting this into two separate settings:

New Message Placement
Display new messages at the top
Display new messages at the bottom
Timeline Scrolling Direction
Scroll from top to bottom
Scroll from bottom to top

While I understand that implementing this change may not be straightforward, I believe it would provide a more logical and flexible user experience. Users could configure the timeline according to their personal preferences without one setting automatically affecting other aspects of the interface.

Thank you for considering this suggestion.

I would like to suggest an improvement to the timeline settings. Currently, a single option controls both the position of new messages (top or bottom) and the scrolling behavior, including the placement of the top and bottom navigation menus. As a result, these different interface behaviors are tied together. I would like to propose splitting this into two separate settings: New Message Placement Display new messages at the top Display new messages at the bottom Timeline Scrolling Direction Scroll from top to bottom Scroll from bottom to top While I understand that implementing this change may not be straightforward, I believe it would provide a more logical and flexible user experience. Users could configure the timeline according to their personal preferences without one setting automatically affecting other aspects of the interface. Thank you for considering this suggestion.
tom79 commented 2026-06-03 06:44:53 +00:00 (Migrated from codeberg.org)

The thing is, the message placement and the scroll direction can't really be separated. They are linked by design: if new messages show at the top, you read from top to bottom, and vice versa. Splitting them into two free options would create combinations that don't make sense. Or did I misunderstand your meaning?

What can be decoupled is the position of the navigation menus (top/bottom), since that is just a visual choice. I can look into making that one independent: a single bar that can be set at the bottom or the top.

The thing is, the message placement and the scroll direction can't really be separated. They are linked by design: if new messages show at the top, you read from top to bottom, and vice versa. Splitting them into two free options would create combinations that don't make sense. Or did I misunderstand your meaning? What can be decoupled is the position of the navigation menus (top/bottom), since that is just a visual choice. I can look into making that one independent: a single bar that can be set at the bottom or the top.
nienty commented 2026-06-03 11:42:06 +00:00 (Migrated from codeberg.org)

yes the goal is to manage the display of the top and low menu bars

yes the goal is to manage the display of the top and low menu bars
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
tom79/Holos-App#143
No description provided.