alexl

joined 2 years ago
[–] alexl@pkm.social 1 points 1 year ago

It was another person.

Again, you are confusing the concept of CSD with GTK's implementation of CSD.

I give up, cheers.

[–] alexl@pkm.social 1 points 1 year ago (2 children)

Removing the whole title bar implies no window buttons, the point is having them while not wasting space.

As I already shown to you GTK apps display window controls according to a global config. So you can turn a header bar in just a toolbar. I don't know about other CSD apps but it would be their fault, not a CSD disadvantage.

[–] alexl@pkm.social 1 points 1 year ago (4 children)

In some cases a SSD title bar is just a waste of space.

[–] alexl@pkm.social 1 points 1 year ago (6 children)

Me and the other person here are trying to make you understand that CSD doesn't imply GNOME's header bar.

Some applications could take advantage of CSD without the user even noticing if they are looking at a SSD or CSD app.

CSD vs SSD is just a technical implementation with the difference that the SSD draws a line inside a window: the window manager is responsible for what is above the line (the title bar) and the app for what is below the line.

With CSD that line just doesn't exist.

[–] alexl@pkm.social 1 points 1 year ago (8 children)

It's like the content of the window could "leak" into the title bar

If you enable CSD in Firefox you can already merge the tabs with the window controls

[–] alexl@pkm.social 1 points 1 year ago (12 children)

> What is the benefit of changing from SSD to CSD if the end result is to look like SSD, but have all the issues that come from using CSD?

Because you can implement things like these (open this comment in Mastodon if in Lemmy you don't see the attached images) and I don't see what the issues are:

[–] alexl@pkm.social 1 points 1 year ago (2 children)

And if you install them they will follow whatever global setting you have, consistently.

Sorry for assuming you were familiar with GNOME/GTK.

[–] alexl@pkm.social 1 points 1 year ago (4 children)

About the hamburger menu: are those screenshots by you or by diffetent people from the Web? Because the position of the menu is a user setting:

https://docs.gtk.org/gtk4/property.Settings.gtk-decoration-layout.html

About the split of header bar: it depends if an app has a header bar that refers to both the views below or the app is splitted in two with two header bars that refer to the respective views.

[–] alexl@pkm.social 1 points 1 year ago (6 children)

These are guidelines for header bars:

https://developer.gnome.org/hig/patterns/containers/header-bars.html

Yes different applications feature a different set of controls but in a consistent way, just like the rest of the UI. I don't understand why you expect a portion of UI to be exactly the same for all apps.

[–] alexl@pkm.social 1 points 1 year ago (8 children)
[–] alexl@pkm.social 1 points 1 year ago (10 children)

As shown by Latte Dock's Window Buttons widget, apps can display window controls that follow the window decoration theme.

And in GNOME apps follow some guidelines that include how header bars should be.

KDE apps do the same for everything but the titlebar that is drawn by KWin. If they are consistent with their content, I don't see why they wouldn't stay consistent when making the titlebar/window controls their own responsability.

view more: next ›