docs: restore screenshots to Why Ferese
This commit is contained in:
1 parent
643fd5fef1
commit
950ba723ab
1 file changed
+4
@@ -12,6 +12,8 @@ Settings and `~/.config/ferese/config.kdl` are two ways to edit the same configu
|
||||
|
||||
The shared settings have a defined scope. Ferese can coordinate the surfaces it draws and the transitions it manages; it does not control every animation an application draws inside its own window. That distinction matters when describing a consistent desktop: consistency between Ferese’s components should not be confused with taking over application behaviour.
|
||||
|
||||
[](images/screenshots/rose-pine-dark.webp)
|
||||
|
||||
## Different work needs different arrangements
|
||||
|
||||
A scrolling layout is useful when several windows need more space than can comfortably fit on one screen. Instead of shrinking everything to remain visible, the desktop can show part of a wider arrangement and move the viewport as focus changes. Tree tiling serves a different situation: the available screen is divided between windows so they can remain visible together.
|
||||
@@ -20,6 +22,8 @@ Ferese supports both, with the layout selected per workspace. Floating windows a
|
||||
|
||||
Even within scrolling, moving focus does not always need to move the desktop. Ferese’s minimal focus strategy leaves a fully visible column where it is and scrolls only far enough to reveal a hidden edge. Other strategies centre the focused column or arrange columns into viewport-sized pages. These choices affect how much the desktop moves while you work, so they belong in the layout’s behaviour rather than being treated as visual decoration.
|
||||
|
||||
[](images/screenshots/ferese-blue-overview.webp)
|
||||
|
||||
## Movement that responds to what you do next
|
||||
|
||||
An animation often starts before you have finished deciding what to do. You might focus another window while the viewport is moving, reverse a fullscreen transition, or reopen a panel before it has finished closing. The desktop needs to handle that next input using the state already on screen.
|
||||
|
||||
Reference in new issue
Block a user