Live data from Hacker News

XFCE 4.20 Released

alexxcons.github.io

11–20 of 49 posts

Re: XFCE 4.20 Released

#11
post #8
post #4

Earlier quoted context omitted.

Wayland still intrigues me - it was first released 16 years ago but still support like in XFCE is "experimental". I really don't know much about Wayland but its initial goals and the excitement if caused (at first) seemed always very noble.

XFCE is the one running late here. Gnome, kde, and even all the wlroots based compositors have been pretty solid

some value of "solid" that ignores machines with vmgfx or nvidia modules.

Re: XFCE 4.20 Released

#12
post #9
post #4

Earlier quoted context omitted.

Wayland still intrigues me - it was first released 16 years ago but still support like in XFCE is "experimental". I really don't know much about Wayland but its initial goals and the excitement if caused (at first) seemed always very noble.

There's definitely a lesson to be learned from Wayland's rollout. Technically it's a vastly superior approach to system graphics. The major roadblock to its adoption has been that it didn't deal with all the "extras" that X provided to desktop distributions as well. Things like copy/paste, screen sharinf, and others don't have a single standard way of accomplishing through Wayland because those aren't things related…

> provide a side project where all the extra bits that maybe people liked can grow a replacement

The whole point of freedesktop.org was to provide such a side project in the first place. The fact that it doesn't seem to be doing this with any effectiveness at present is the real issue.

Re: XFCE 4.20 Released

#13
post #7

Making your own app-icons is notoriously difficult. $ cat /usr/local/bin/noko-make-icon convert -size 24x24 -gravity center -background yellow -fill black\ label:$1 ~/.local/share/icons/$1.png file=~/.local/share/applications/$1-noko.desktop echo [Desktop Entry] > $file echo Name=$1 >> $file echo Comment=noko-made >> $file echo Exec=$1 >> $file echo Terminal=false >> $file echo Icon=~/.local/share/icons/$1.png >> $fi…

Would you prefer this script to be shipped for you? If so, I suppose it should support more optional parameters, e.g. for the name and comment.

BTW you can DRY it up:

  convert ... # Unchanged.
  cat ~/.local/share/applications/$1-noko.desktop
  [Desktop Entry]
  Name=$1
  Comment=noko-made
  Exec=$1
  Terminal=false
  Icon=~/.local/share/icons/$1.png
  Type=Application
  EOF

Re: XFCE 4.20 Released

#14
post #7

Making your own app-icons is notoriously difficult. $ cat /usr/local/bin/noko-make-icon convert -size 24x24 -gravity center -background yellow -fill black\ label:$1 ~/.local/share/icons/$1.png file=~/.local/share/applications/$1-noko.desktop echo [Desktop Entry] > $file echo Name=$1 >> $file echo Comment=noko-made >> $file echo Exec=$1 >> $file echo Terminal=false >> $file echo Icon=~/.local/share/icons/$1.png >> $fi…

The desktop entries also control which application is used to "open" a file. Writing and debugging them made me hate the xdg-open system.

Also, if you specify Terminal=true, your configured preference for your terminal emulator is ignored by all desktop environments.

Re: XFCE 4.20 Released

#16
post #9
post #4

Earlier quoted context omitted.

Wayland still intrigues me - it was first released 16 years ago but still support like in XFCE is "experimental". I really don't know much about Wayland but its initial goals and the excitement if caused (at first) seemed always very noble.

There's definitely a lesson to be learned from Wayland's rollout. Technically it's a vastly superior approach to system graphics. The major roadblock to its adoption has been that it didn't deal with all the "extras" that X provided to desktop distributions as well. Things like copy/paste, screen sharinf, and others don't have a single standard way of accomplishing through Wayland because those aren't things related…

FTFY: s/extras/essential features/

the decision to roll window management and keyboard management and screen management into one thing called "compositor" looks very cavalier to me. It resulted in a need to duplicate so many things that are modular and pluggable under X.

(Repeating myself, I wish somebody created a Wayland compositor that explicitly delegates most tasks to plugins, providing a stable interface, so that you could use your own WM, your own keyboard switcher, etc. Thankfully, screenshooting is using a similar approach already, but in a limited way. The idea is so obvious that somebody must have attempted this already.)

Re: XFCE 4.20 Released

#18
...And just the other day I was thinking about maybe trying XFCE out :)

Now, currently I'm using LXQt (which is probably even more bare bones and "get the job done" DE), what can XFCE give me? I mean, I certainly see a point when people switch to XFCE from Gnome or KDE. But what about if coming from the other side of the spectrum?

Re: XFCE 4.20 Released

#19
post #18

...And just the other day I was thinking about maybe trying XFCE out :) Now, currently I'm using LXQt (which is probably even more bare bones and "get the job done" DE), what can XFCE give me? I mean, I certainly see a point when people switch to XFCE from Gnome or KDE. But what about if coming from the other side of the spectrum?

> I certainly see a point when people switch to XFCE from Gnome or KDE. But what about if coming from the other side of the spectrum?

I think you basically answered it right there.

It sits between. For the lxde people it would be more of a full fledged desktop, but not with the full weight of KDE or Gnome.

Post reply on HN