Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using kwin_x11 instead of Openbox #164

Closed
probonopd opened this issue Apr 19, 2021 · 66 comments
Closed

Consider using kwin_x11 instead of Openbox #164

probonopd opened this issue Apr 19, 2021 · 66 comments

Comments

@probonopd
Copy link
Member

probonopd commented Apr 19, 2021

image

Using kwin_x11 instead of Openbox would give us

  • "Aero Snap"
  • Resizable windows (at all edges)
  • Resize icon in the bottom right
  • Properly centered titles
  • Qt theming
  • Drop shadow rendering that does not appear before the rest of the window
  • Nice animations on window resize
  • "Magic lamp" effect when minimizing and un-minimizing windows, even to the Dock if it supports it
  • "Exposé" overview of all open windows
  • Stacked initial window placement Cascade = staircase-by-title
  • ...while respecting centered Application splash screens
  • Rounded corners at the top and sharp corners at the bottom (as we want)
  • Rounded corners at the top disappear if windows are maximized or snapped to the top
  • Many other cool features

As a result, the whole desktop feels much more modern (in a positive way).

But

  • Need to find a way to build it with fewer dependencies (also see https://community.kde.org/KWin/Dependencies) - POTENTIAL SHOWSTOPPER
  • Seems to draw in /usr/local/bin/kglobalaccel5 for global keyboard shortcuts such as Alt-Tab; this might mean that we should retire /usr/local/bin/lxqt-globalkeysd; configuration lives in ~/.config/kglobalshortcutsrc
  • Can break Command+Space. When you click on the Desktop background and then type Command+Space, then it works. When another window is frontmost, then it is broken more often than not.

Notes


Starting with today's experimental ISO builds, the configuration for KWin is included on the ISO, but not KWin nor the BreezeEnhanced theme yet. For those who would try KWin on helloSystem, sudo pkg install -y plasma5-kwin, replace openbox with kwin_x11 in /usr/local/bin/start-hello, and build and install the BreezeEnhanced theme.

@probonopd

This comment has been minimized.

@PreyK

This comment has been minimized.

@probonopd
Copy link
Member Author

probonopd commented Apr 20, 2021

This is what happens if you try to install the plasma5-kwin package. It would grow the ISO by over 100 MB. Looking at the dependencies I wonder whether one could make e.g., a kwin-x11-minimal package that would not draw in the non-essential dependencies.

FreeBSD% sudo pkg install plasma5-kwin
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 110 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        aspell: 0.60.8_1,1
        boost-libs: 1.72.0_4
        brotli: 1.0.9,1
        docbook: 1.5
        docbook-sgml: 4.5_1
        docbook-xml: 5.0_3
        docbook-xsl: 1.79.1_1,1
        dotconf: 1.3_1
        espeak: 1.48.04_7
        fftw3: 3.3.9
        flac: 1.3.3
        gnupg: 2.2.27
        gpgme: 1.15.1
        gpgme-cpp: 1.15.1
        gpgme-qt5: 1.15.1
        gstreamer1-libav: 1.16.2
        gstreamer1-plugins-a52dec: 1.16.2
        gstreamer1-plugins-core: 1.16
        gstreamer1-plugins-dts: 1.16.2
        gstreamer1-plugins-dvdread: 1.16.2_1
        gstreamer1-plugins-mpg123: 1.16.2
        gstreamer1-plugins-pango: 1.16.2
        gstreamer1-plugins-png: 1.16.2
        gstreamer1-plugins-resindvd: 1.16.2_1
        gstreamer1-plugins-theora: 1.16.2
        gstreamer1-plugins-ugly: 1.16.2
        hyphen: 2.8.8
        iso8879: 1986_3
        kf5-attica: 5.80.0
        kf5-breeze-icons: 5.80.0
        kf5-frameworkintegration: 5.80.0
        kf5-kactivities: 5.80.0
        kf5-karchive: 5.80.0
        kf5-kauth: 5.80.0
        kf5-kbookmarks: 5.80.0
        kf5-kcmutils: 5.80.0
        kf5-kcodecs: 5.80.0
        kf5-kcompletion: 5.80.0
        kf5-kconfigwidgets: 5.80.0
        kf5-kcrash: 5.80.0
        kf5-kdeclarative: 5.80.0
        kf5-kded: 5.80.0
        kf5-kdelibs4support: 5.80.0
        kf5-kdesignerplugin: 5.80.0
        kf5-kdewebkit: 5.80.0
        kf5-kdoctools: 5.80.0
        kf5-kemoticons: 5.80.0
        kf5-kglobalaccel: 5.80.0
        kf5-kguiaddons: 5.80.0
        kf5-kiconthemes: 5.80.0
        kf5-kidletime: 5.80.0
        kf5-kinit: 5.80.0
        kf5-kio: 5.80.1
        kf5-kirigami2: 5.80.0
        kf5-kitemmodels: 5.80.0
        kf5-kitemviews: 5.80.0
        kf5-kjobwidgets: 5.80.0
        kf5-knewstuff: 5.80.0
        kf5-knotifications: 5.80.0
        kf5-kpackage: 5.80.0
        kf5-kparts: 5.80.0
        kf5-kplotting: 5.80.0
        kf5-kservice: 5.80.0
        kf5-ktextwidgets: 5.80.0
        kf5-kunitconversion: 5.80.0
        kf5-kwallet: 5.80.0
        kf5-kwayland: 5.80.0
        kf5-kwidgetsaddons: 5.80.0
        kf5-kxmlgui: 5.80.0
        kf5-plasma-framework: 5.80.0
        kf5-solid: 5.80.0
        kf5-sonnet: 5.80.0
        liba52: 0.7.4_3
        libassuan: 2.5.4
        libcanberra: 0.30_5
        libcanberra-gtk3: 0.30_5
        libdca: 0.0.7
        libksba: 1.5.0
        libsndfile: 1.0.31
        mpg123: 1.26.5
        npth: 1.6
        phonon-qt5: 4.11.1
        pinentry: 1.1.1
        pinentry-curses: 1.1.1
        pinentry-qt5: 1.1.1
        plasma-wayland-protocols: 1.2.1
        plasma5-breeze: 5.20.5
        plasma5-kdecoration: 5.20.5
        plasma5-kscreenlocker: 5.20.5
        plasma5-kwayland-server: 5.20.5
        plasma5-kwin: 5.20.5_1
        portaudio: 19.6.0_5,1
        qt5-assistant: 5.15.2
        qt5-designer: 5.15.2_1
        qt5-help: 5.15.2_1
        qt5-qdbus: 5.15.2
        qt5-sensors: 5.15.2_1
        qt5-speech: 5.15.2
        qt5-uiplugin: 5.15.2
        qt5-uitools: 5.15.2_1
        qt5-virtualkeyboard: 5.15.2_1
        qt5-wayland: 5.15.2_1
        qt5-webkit: 5.212.0.a4_4
        sdocbook-xml: 1.1_2,2
        speech-dispatcher: 0.8.8_1
        woff2: 1.0.2_4
        xcb-util-cursor: 0.1.3
        xmlcatmgr: 2.2_2
        xmlcharent: 0.3_2
        xwayland-devel: 1.20.0.907

Number of packages to be installed: 110

The process will require 552 MiB more space.
108 MiB to be downloaded.

cc'ing @jbeich @adriaandegroot. tl;dr: helloSystem is a Qt based FreeBSD-based system that does not use the KDE Plasma desktop but its own Qt-based helloDesktop, and we would like to use KWin without having to install "half of KDE Plasma". We are also not interested in Wayland in any way, form or shape, especially given its current state on FreeBSD.

@adriaandegroot
Copy link

"half of KDE-Plasma" is a terrible way to characterize this.
Wayland works remarkably well on FreeBSD -- just not KDE Plasma. You'll note that all the things jbeich@ works on (or maintains in ports), work well.

A fair chunk of what you're seeing here is like what you had in Falkon, previously, and which I explained there: packaging is a "batteries included" exercise most of the time, so you get all the bits.

  • Some part of the stack has a Qt Designer plugin: then you get a dependency on Qt Designer -- which is great for developers in general, and lousy for a live CD where you're not going to be doing development anyway.
  • Presumably you have your own theming, too, so you could lose breeze.
  • doctools pulls in the SGML things.
  • spell checking, grammar checking, those seem a bit superfluous.
  • webkit I don't know where it comes from and doubles up on webengine (which I think you already have for Falkon so webengine is "free").

Some more effort from the helloSystem side on making packages more lightweight through flavors (like falkon@qtonly) even if it's just small patches ("here's a patch to make a @lite flavor of KWin; it's not very lite yet, but drops Wayland support" or "kwin depends on webkit through ... is that really necessary?") would go a long way here.

BTW, FreeBSD PR 241490 may also be relevant for you. I suppose with "real" graphics you do need a real mesa-DRI, but keep in mind what elephant (I think it was jbeich@ who said it) gets dragged in by that.

@jbeich
Copy link

jbeich commented Apr 20, 2021

https://community.kde.org/KWin/Dependencies

  • Not promising: "This page was last edited on 4 March 2014, at 10:13."
  • According to Gentoo barely anything is optional
  • kf5-wayland and plasma5-kwayland-server are REQUIRED
  • kf5-breeze (pulls 76Mb large kf5-breeze-icons) is OPTIONAL but plasma5-kwin also has indirect dependency on it

X11-only or Wayland-only flavors cannot be implemented globally for all packages due to lack of provides/requires support to avoid exploding the number of packages. For example, in A -> B -> C -> D dependency chain A has @nowayland flavor but supporting it currently requires propagating the flavor into B/C/D, none of which care whether A was built with or without Wayland support.

@jbeich
Copy link

jbeich commented Apr 20, 2021

All Wayland dependencies combined likely take less than plasma5-kwin alone.

Space used per extra package
  • boost-libs uses 166 MiB
  • kf5-breeze-icons uses 76 MiB
  • docbook-xsl uses 47 MiB
  • qt5-webkit uses 42 MiB
  • plasma5-kwin uses 22 MiB
  • kf5-kio uses 21 MiB
  • plasma5-breeze uses 19 MiB
  • kf5-kdelibs4support uses 18 MiB
  • gnupg uses 10 MiB
  • kf5-kunitconversion uses 10 MiB
  • qt5-designer uses 8.6 MiB
  • kf5-plasma-framework uses 7.6 MiB
  • kf5-kwidgetsaddons uses 6.8 MiB
  • qt5-wayland uses 6.3 MiB
  • docbook-xml uses 5.5 MiB
  • fftw3 uses 5.2 MiB
  • aspell uses 4.9 MiB
  • kf5-knewstuff uses 3.7 MiB
  • espeak uses 3.1 MiB
  • kf5-kxmlgui uses 3.0 MiB
  • kf5-kwayland uses 2.8 MiB
  • docbook-sgml uses 2.7 MiB
  • flac uses 2.6 MiB
  • kf5-kdoctools uses 2.4 MiB
  • kf5-kemoticons uses 2.2 MiB
  • xwayland-devel uses 2.2 MiB
  • kf5-kwallet uses 1.9 MiB
  • plasma5-kwayland-server uses 1.9 MiB
  • brotli uses 1.8 MiB
  • kf5-solid uses 1.8 MiB
  • qt5-virtualkeyboard uses 1.7 MiB
  • kf5-frameworkintegration uses 1.7 MiB
  • gpgme uses 1.7 MiB
  • kf5-kirigami2 uses 1.5 MiB
  • kf5-kconfigwidgets uses 1.5 MiB
  • kf5-sonnet uses 1.4 MiB
  • speech-dispatcher uses 1.4 MiB
  • kf5-ktextwidgets uses 1.4 MiB
  • gpgme-qt5 uses 1.4 MiB
  • kf5-kcmutils uses 1.3 MiB
  • phonon-qt5 uses 1.2 MiB
  • kf5-kservice uses 1.1 MiB
  • qt5-uitools uses 1.1 MiB
  • kf5-kdeclarative uses 1.0 MiB
  • libsndfile uses 999 KiB
  • kf5-kparts uses 893 KiB
  • qt5-assistant uses 875 KiB
  • mpg123 uses 869 KiB
  • qt5-sensors uses 868 KiB
  • kf5-kpackage uses 850 KiB
  • kf5-attica uses 849 KiB
  • libksba uses 842 KiB
  • plasma5-kscreenlocker uses 798 KiB
  • qt5-help uses 759 KiB
  • kf5-kbookmarks uses 652 KiB
  • portaudio uses 635 KiB
  • kf5-kcodecs uses 635 KiB
  • gpgme-cpp uses 540 KiB
  • kf5-kiconthemes uses 533 KiB
  • kf5-kactivities uses 516 KiB
  • kf5-kinit uses 498 KiB
  • kf5-knotifications uses 480 KiB
  • kf5-kitemmodels uses 478 KiB
  • kf5-kglobalaccel uses 457 KiB
  • kf5-kcompletion uses 434 KiB
  • gstreamer1-plugins-ugly uses 425 KiB
  • kf5-kjobwidgets uses 424 KiB
  • libdca uses 412 KiB
  • gstreamer1-libav uses 400 KiB
  • kf5-kauth uses 378 KiB
  • kf5-kitemviews uses 366 KiB
  • kf5-karchive uses 338 KiB
  • libcanberra uses 325 KiB
  • libassuan uses 292 KiB
  • plasma5-kdecoration uses 282 KiB
  • kf5-kdewebkit uses 245 KiB
  • kf5-kguiaddons uses 233 KiB
  • hyphen uses 213 KiB
  • woff2 uses 206 KiB
  • gstreamer1-plugins-resindvd uses 195 KiB
  • liba52 uses 187 KiB
  • sdocbook-xml uses 165 KiB
  • plasma-wayland-protocols uses 163 KiB
  • kf5-kdesignerplugin uses 161 KiB
  • kf5-kplotting uses 155 KiB
  • dotconf uses 145 KiB
  • pinentry-qt5 uses 138 KiB
  • kf5-kidletime uses 138 KiB
  • qt5-speech uses 135 KiB
  • kf5-kded uses 134 KiB
  • libcanberra-gtk3 uses 109 KiB
  • gstreamer1-plugins-pango uses 108 KiB
  • xmlcharent uses 94 KiB
  • gstreamer1-plugins-theora uses 87 KiB
  • qt5-qdbus uses 83 KiB
  • pinentry-curses uses 80 KiB
  • iso8879 uses 70 KiB
  • kf5-kcrash uses 69 KiB
  • gstreamer1-plugins-dvdread uses 66 KiB
  • npth uses 65 KiB
  • pinentry uses 58 KiB
  • gstreamer1-plugins-png uses 56 KiB
  • xcb-util-cursor uses 53 KiB
  • xmlcatmgr uses 48 KiB
  • gstreamer1-plugins-a52dec uses 47 KiB
  • gstreamer1-plugins-mpg123 uses 45 KiB
  • gstreamer1-plugins-dts uses 45 KiB
  • qt5-uiplugin uses 41 KiB
  • gstreamer1-plugins-core uses 0 B
  • docbook uses 0 B

@adriaandegroot
Copy link

Thanks @jbeich , confirms what I was thinking that Wayland is not the problem here. I've got a patch lined up for ports that turns KDE_USE=doctools into KDE_USE=doctools_build for most everything. That drops the docbook and related deps from kwin, at least. The doctools are really not needed, not even in the "batteries included" style of most FreeBSD ports.

From that table of "extra space" getting rid of boost would be a real win. The point of intersection between pkg info -d plasma5-kwin and pkg info -r boost-libs is kf5-kactivities. That has a stated LIB_DEPENDS on boost, but ldd doesn't mention it. Looking at the source, it seems it's only algorithms from boost being used, so that could go to a BUILD_DEPENDS instead and then we're pretty good (except to the extent that boost might be needed for the installed headers, so we're skirting along the edge of "when do dev-tools get installed").

@probonopd
Copy link
Member Author

Thank you very much for looking into this topic.

here's a patch to make a @lite flavor of KWin

Yes, that's what I was thinking of. Was thinkinging that it wouldn't hurt to informally discuss with you the experts first.
Do you think it would be a good idea to have kwin-x11-lite and possibly kwin-wayland-lite packages?

@adriaandegroot
Copy link

As Jan points out:

  • removing Wayland as a dep is probably very difficult
  • removing Wayland as a dep has a microscopically small effect
  • (yes, the dependencies page for KWin is probably very outdated, but that wiki is not the source of truth anyway)

Effective changes I have already implemented, but not pushed to the ports tree (they'll land together with Plasma 5.21):

  • drop doctools as a runtime dep for individual frameworks (might need extending to plasma- ports)
  • move boost to a buildtime dep
  • drop unnecessary kdelibs4support deps

Things on @probonopd 's plate then are:

  • figure out where your webkit dependency comes from
  • see if you can get rid of breeze and breeze icons
    Together with changes already implemented that saves you at least 330MB.

@probonopd

This comment has been minimized.

@probonopd
Copy link
Member Author

KWin seems to use kglobalaccel5 for keyboard shortcuts, e.g., to switch from window to window with Alt-Tab. To change those, one apparently needs to use skel as those cannot be changed system-wide?!

https://forum.kde.org/viewtopic.php?f=111&t=118450

@adriaandegroot
Copy link

adriaandegroot commented Apr 25, 2021

KWin seems to use kglobalaccel5 for keyboard shortcuts, e.g., to switch from window to window with Alt-Tab. To change those, one apparently needs to use skel as those cannot be changed system-wide?!

You are linking to a discussion from 2013 that is discussing kde4-era kwin. You'd have a better time asking current Kwin folk on one of their support channels. There is a #kwin IRC channel on Freenode.

@adriaandegroot
Copy link

Effective changes I have already implemented, but not pushed to the ports tree (they'll land together with Plasma 5.21):

This has landed, and it'd be good to hear if that helps out your dependency size any.

@probonopd
Copy link
Member Author

Thank you very much @adriaandegroot for you help, this is tremendous.

probonopd added a commit to helloSystem/Dock that referenced this issue Apr 25, 2021
So that windows minimized by KWin get animated to go to the Dock rather than where the mouse is
Backport cyberos/cyber-dock@6bb30c4
cyberos/cyber-dock#5
helloSystem/hello#164
@kettle-7
Copy link

I tried installing the plasma5-kwin package, and it only threw 7 dependencies at me:

The following 7 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        kf5-kidletime: 5.80.0
        plasma-wayland-protocols: 1.2.1
        plasma5-kscreenlocker: 5.20.5
        plasma5-kwayland-server: 5.20.5
        plasma5-kwin: 5.20.5_1
        xcb-util-cursor: 0.1.3
        xwayland-devel: 1.20.0.917

Number of packages to be installed: 7

The process will require 28 MiB more space.
7 MiB to be downloaded.

Everything else is just pulled in by kf5-breeze-icons, which I installed because of another project I'm making. None of these packages are that big, so it's clearly the breeze icon theme with all of its SVG icons for every button or mimetype you can imagine.

@kettle-7
Copy link

kettle-7 commented May 16, 2021

So far, so good. kwin_x11 --replace absolutely nuked the desktop, so I had to log out and back in again. I edited start-hello to start KWin instead of openbox and picom and it works, so something tells me that KWin and Picom don't agree with each other. Also, there's a chunk missing out of the bottom-right corner of every window, is this normal?

Edit

2 things I noticed:

  • The window borders (besides the bottom-right corner) look nice, but they're a lot thicker than the openbox ones.
  • When I hover the mouse over a window titlebar, I get the ugly default X cursor, as opposed to my preferred cursor theme.
    Neither of these are of much importance.

@probonopd
Copy link
Member Author

probonopd commented May 16, 2021

A future release will come with kwin_x11 out of the box. I am running it locally since a month now and am happy with it. It does require quite a bit of configuration, so I suggest to just wait until it appears fully pre-configured in helloSystem.

KWin and Picom don't agree with each other

kwin_x11 has picom-like functionality built in, so you don't need picom anymore.

The window borders

All of this needs to be heavily configured so that it looks and works like we want in helloSystem. I have such a configuation locally and it looks like this:

image

@kettle-7
Copy link

I like the window control layout that you're using with openbox, close on the left and max on the right.

@jhjacobs81
Copy link

how did elementaryos did it? they wrote their own desktop environment i believe, would that not be possible for helloSystem too? (jus thinking out loud here) Then it would be possible to slim down on all the extra requirements?

@probonopd
Copy link
Member Author

elementary OS is using Gtk, which we do not want to use. kwin_x11 does the job nicely, been using it for a while now.

@kettle-7
Copy link

You can get some good traffic light kwin themes on the KDE store (another of those annoying pling ones!)

@probonopd
Copy link
Member Author

Let's move away from traffic lights to look less like "a Mac theme". Remember, the goal is to be "welcoming to switchers" but not to be a "Mac theme". The colors can be disturbing anyway.

@kettle-7
Copy link

There is a Qml module specifically for writing compositing window managers, I'll try find it.

@kettle-7
Copy link

Are you using Breeze Enhanced?

@probonopd
Copy link
Member Author

Yes, for the upcoming kwin_x11 we are using a custom patched version of it:
https://github.com/helloSystem/BreezeEnhanced

The reason why we need a custom patched version is explained here:
tsujan/BreezeEnhanced#32

@probonopd
Copy link
Member Author

I tried installing the plasma5-kwin package, and it only threw 7 dependencies at me

Strange, I now built an ISO with latest rather than quarterly packages (so that we benefit from all recent changes in packaging) and plasma5-kwin, and the resulting Live ISO (compressed) is 1.61 GB, up from 1.27 GB. 340 MB (compressed) just for adding a window manager is still something that I cannot understand. Need to look into this more deeply.

@probonopd
Copy link
Member Author

Besides the different icons (an intentional choice to make things visually more distinctive) the look should not be that different at all.

Do you think the advantages listed at #164 (comment) make it still worthwhile to pursue?

@bmentink
Copy link

Do you think the advantages listed at #164 (comment) make it still worthwhile to pursue?

Personally I would say no. If those extra features introduce complexity, bloat and a performance hit, then I would stay with the openbox windows as they are, they actually look very good as they are and are functional "enough", especially if you could fix the dragable corners issue .. again just my 2c.

@PreyK
Copy link

PreyK commented Jun 27, 2021

I think in this case getting everything under kwin would actually decrease the complexity.
As far as I looked into it Menu and Dock already using kwin libraries for some of the functionality, kwin_x11 with kwin libraries would mean that there's no undefined behaviour.
Also the whole system uses Qt pretty heavily and kwin/the kde project was made with explicitly Qt in mind.
On top of this with the additional nice to haves outlined in #164 (comment) I think it's definetly worth it.
But that's just how I see it
On the snappiness, that might be compositing, kwin has a few different modes, might worth a look

@probonopd
Copy link
Member Author

@bmentink reported:

Used to be able to click on "Search" top bar and start typing a name to get to a program fast, no longer works, typing does nothing.

I noticed the same today.

Stangely it is depending on which application is frontmost when you press Command+Space. When you click on the Desktop background and then type Command+Space, then it works.

@bmentink
Copy link

on 0.5.0 release yes that is true. You have to click on the desktop before you can hit Command+Space and search, you should be able to do it any time no matter what is frontmost ..

On your experimental-12.2 build you linked, you can't even do that! Click on the desktop then try to use Command+Space and nothing happens, you can not try typing to search ..

@probonopd
Copy link
Member Author

probonopd commented Jun 28, 2021

Needs to be investigated further. On my local build system, I can click on the desktop then try to use Command+Space and it works. But here I am not using the KWin.app with the stubs yet. So I need to check whether that breaks it even more than it is broken already without it...

@probonopd
Copy link
Member Author

Regarding menu transparency:

*.kwinrule files can be used to adjust certain classes of windows, e.g., to give them translucency (= less than opacity 100).

Apparently they are loaded from /usr/local/etc/xdg/kwinrulesrc and ~/.config/kwinrulesrc but I could not get it to work yet. Did anyone?

@probonopd
Copy link
Member Author

Do we want rounded corners also at the bottom? Seems doable with KWin using
https://github.com/srevinsaju/KDE-Rounded-Corners

@kettle-7
Copy link

adjust certain classes of windows

I used this for some apps that don't have the title bar blend, like Firefox and FeatherPad.

Did anyone?

I used KDE System Settings, it's useful for a lot of things.

Do we want rounded corners also at the bottom?

YES. With the Breeze Enhanced theme, you change the window border thickness to Tiny and then you get rounded bottom corners. You also don't get the bottom right corner chopped off, AND it's easier to resize.

@probonopd
Copy link
Member Author

If you can share your settings files, I will have a good look at them! 👍

@kettle-7
Copy link

I did it all through KDE System Settings.

Also, for some reason I get a strange x-shaped cursor when the mouse touches the edge of the screen.

@probonopd
Copy link
Member Author

I did it all through KDE System Settings.

It must have stored the settings somewhere ;-)

@kettle-7
Copy link

kettle-7 commented Jul 6, 2021

I despise dconf, yet find it so useful...

@probonopd
Copy link
Member Author

This is how it should look like when you move the mouse cursor all the way into the corner:

image

Using our KWin.app, we just get a graphical glitch instead of the blue glow.

We are probably missing an asset in KWin. Does anyone know where this asset lives?

@louies0623
Copy link

Try to reduce the transparency of blue glow to 50, the blue is a bit "dazzling"

@probonopd
Copy link
Member Author

KWin.app breaks search in the Menu.
helloSystem/ISO#234

@probonopd
Copy link
Member Author

probonopd commented Sep 13, 2021

KWin.app breaks search in the Menu.
helloSystem/ISO#234

This seems to be related to how we start Welcome.app; if one logs out and logs in again on the Live ISO, then it starts to work. Snap to edge is working too.

Thanks @wesbluemarine for pointing in this direction.

probonopd added a commit to helloSystem/Utilities that referenced this issue Sep 16, 2021
probonopd added a commit to helloSystem/Utilities that referenced this issue Sep 16, 2021
@probonopd
Copy link
Member Author

Let's see if build 0F34 improves this.

@probonopd
Copy link
Member Author

probonopd commented Sep 19, 2021

Command+Tab can be restored by installing kf5-kglobalaccel. Unfortunately this draws in kf5-kcrash, kf5-karchive, and kf5-kservice.

probonopd added a commit to helloSystem/ISO that referenced this issue Sep 19, 2021
@probonopd
Copy link
Member Author

probonopd commented Sep 19, 2021

KWin ignores QT_SCALE_FACTOR, hence breaking HiDPI for helloSystem:
helloSystem/KWin#3

@probonopd
Copy link
Member Author

What do we have to enter in .config/kwinrc to get "large icons" on Command-Tab?

[TabBox]
HighlightWindows=true
LayoutMode=0
DesktopLayout=???
DesktopListLayout=???
LayoutName=compact   

@probonopd
Copy link
Member Author

helloSystem 0.6.0 has been released with KWin.app. Let's see how the feedback is.

@alphamodh0
Copy link

I love rounded corners at top and bottom, is more confortable and modern look. If does'nt exist a grafical way to make it. ¿How can I do it?

@probonopd
Copy link
Member Author

probonopd commented Oct 2, 2021

Thanks for your feedback @alphamodh0. helloSystem is less about a "modern look" than about great user experience. We now have a resize icon at the right-hand bottom side of windows, where it belongs according to https://dl.acm.org/doi/book/10.5555/573097. For the same reason, the iterations of Mac OS X (when it still was good) had rounded corners at the top but not at the bottom of the screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants