Carbon Themes (beta version)

PackRat · 2025-04-04 09:55:30

9 North Centre Vertical??
10 South Centre Vertical??

That is correct; "9;0;0" and the panel is centered at top (north), 10 is south.

johnraff · 2025-04-05 04:45:02

Of course a vertical panel centered L-R in the middle of the screen is not likely to be a popular user option.

So the built-in settings we'd be likely to offer would be

vertical on left, centered up-down:
mode=2 p=7,x=0,y=0

horizontal at bottom, centered L-R:
mode=0 p=10,x=0,y=0

or possibly
horizontal at top, centered L-R:
mode=0 p=9,x=0,y=0

I haven't been able to figure out if there's any difference between, for example, p=1 and p=2 for a top-aligned left vertical bar, or how to use the x= and y= settings with "floating" bars, but maybe we can just ignore those other details for now? Any non-default settings are going to be made by users via the panel settings GUI, not from a config file we ship.

Last edited by johnraff (2025-04-05 04:50:19)

hhh · 2025-04-05 12:07:46

Testing my xfce4-panel configs on a fresh carbon install (from a netinstall ISO, I didn't realize a floating panel only works if you have openbox desktop margins set, otherwise a maximized window falls behind the panel. That doesn't happen when the panel is against an edge.

I'll test that bark theme today, @johnraff. Sorry for the delay.

johnraff · 2025-04-06 06:27:23

xfce4-panel confs - instant gratification

Make sure you've got xfconf installed, and you can change eg that position p= value to p=3 with:

xfconf-query -c xfce4-panel -p /panels/panel-1/position --set 'p=3;x=0;y=0'

The panel will change immediately.

To see all the settings:

xfconf-query -c xfce4-panel -lv

johnraff · 2025-04-06 07:18:00

Found this position reference from 2023, but the mode= setting has arrived more recently and seems to have changed the p= values, so I don't know how valid it is now:
https://forum.xfce.org/viewtopic.php?pid=72748#p72748

Also tried to apply a css margin but it moved only the systray, destroyed the app icons and left the vertical panel where it was:

.panel-1 .vertical {margin-left: 20px}

https://forum.xfce.org/viewtopic.php?pid=78598#p78598

A left margin on the vertical panel might be more trouble than it's worth?
It looks OK up against the left hand side of the screen maybe?

hhh · 2025-04-06 08:48:47

johnraff wrote:

A left margin on the vertical panel might be more trouble than it's worth?
It looks OK up against the left hand side of the screen maybe?

It looks fine against the screen edge. The margin is visually pleasing but is wasted screen space.

johnraff · 2025-04-06 09:04:21

OK, we're getting close to finishing xfce4-panel.
I'll post my suggested config.txt soon. It's the same as yours except for the positioning and changing the middle-click to 1. That allows clicking on a task icon to toggle minimization, as it is in our tint2 to date.

Oh, and cleaning out your residual wifi network settings from the systray.

hhh · 2025-04-07 01:04:05

johnraff wrote:

Oh, and cleaning out your residual wifi network settings from the systray.

Much obliged.

You got the bark theme right, another thank you!

johnraff · 2025-04-10 07:56:08

johnraff wrote:

I'll post my suggested config.txt soon...

Wasn't all that soon, but here are my two suggested replacements for config.txt inside the carbon and carbon_custom tarballs:

carbon

/configver 2
/panels [<1>]
/panels/dark-mode false
/panels/panel-1/enter-opacity uint32 75
/panels/panel-1/leave-opacity uint32 75
/panels/panel-1/length 97.222222222222229
/panels/panel-1/length-adjust false
/panels/panel-1/mode uint32 2
/panels/panel-1/plugin-ids [<6>, <2>, <9>, <1>, <3>, <4>, <5>, <8>]
/panels/panel-1/position 'p=7;x=0;y=0'
/panels/panel-1/position-locked true
/panels/panel-1/size uint32 52
/plugins/clipman/settings/save-on-quit false
/plugins/plugin-1 'tasklist'
/plugins/plugin-1/flat-buttons false
/plugins/plugin-1/include-all-workspaces true
/plugins/plugin-1/middle-click uint32 1
/plugins/plugin-1/show-handle false
/plugins/plugin-1/show-labels false
/plugins/plugin-1/show-wireframes false
/plugins/plugin-1/sort-order uint32 4
/plugins/plugin-1/window-scrolling false
/plugins/plugin-2 'pager'
/plugins/plugin-2/miniature-view false
/plugins/plugin-2/rows uint32 2
/plugins/plugin-2/workspace-scrolling false
/plugins/plugin-2/wrap-workspaces false
/plugins/plugin-3 'separator'
/plugins/plugin-3/expand true
/plugins/plugin-3/style uint32 0
/plugins/plugin-4 'systray'
/plugins/plugin-4/icon-size 24
/plugins/plugin-4/known-items [<'blueman'>]
/plugins/plugin-4/known-legacy-items [<'xfce4-power-manager'>, <'pnmixer'>, <'clipman'>, <'networkmanager applet'>]
/plugins/plugin-4/single-row false
/plugins/plugin-5 'clock'
/plugins/plugin-5/digital-layout uint32 3
/plugins/plugin-5/digital-time-font 'Sans Bold 12'
/plugins/plugin-5/digital-time-format '<span color="#7C7C62">%l:%M</span>'
/plugins/plugin-5/mode uint32 2
/plugins/plugin-6 'separator'
/plugins/plugin-6/style uint32 0
/plugins/plugin-8 'separator'
/plugins/plugin-8/style uint32 0
/plugins/plugin-9 'separator'
/plugins/plugin-9/style uint32 0

carbon_custom

/configver 2
/panels [<1>]
/panels/dark-mode false
/panels/panel-1/enter-opacity uint32 75
/panels/panel-1/leave-opacity uint32 75
/panels/panel-1/length 97.222222222222229
/panels/panel-1/length-adjust false
/panels/panel-1/mode uint32 2
/panels/panel-1/plugin-ids [<6>, <2>, <7>, <9>, <1>, <3>, <4>, <5>, <8>]
/panels/panel-1/position 'p=7;x=0;y=0'
/panels/panel-1/position-locked true
/panels/panel-1/size uint32 52
/plugins/clipman/settings/save-on-quit false
/plugins/plugin-1 'tasklist'
/plugins/plugin-1/flat-buttons false
/plugins/plugin-1/include-all-workspaces true
/plugins/plugin-1/middle-click uint32 1
/plugins/plugin-1/show-handle false
/plugins/plugin-1/show-labels false
/plugins/plugin-1/show-wireframes false
/plugins/plugin-1/sort-order uint32 4
/plugins/plugin-1/window-scrolling false
/plugins/plugin-2 'pager'
/plugins/plugin-2/miniature-view false
/plugins/plugin-2/rows uint32 2
/plugins/plugin-2/workspace-scrolling false
/plugins/plugin-2/wrap-workspaces false
/plugins/plugin-3 'separator'
/plugins/plugin-3/expand true
/plugins/plugin-3/style uint32 0
/plugins/plugin-4 'systray'
/plugins/plugin-4/icon-size 24
/plugins/plugin-4/known-items [<'blueman'>]
/plugins/plugin-4/known-legacy-items [<'xfce4-power-manager'>, <'pnmixer'>, <'clipman'>, <'networkmanager applet'>]
/plugins/plugin-4/single-row false
/plugins/plugin-5 'clock'
/plugins/plugin-5/digital-layout uint32 3
/plugins/plugin-5/digital-time-font 'Sans Bold 12'
/plugins/plugin-5/digital-time-format '<span color="#7C7C62">%l:%M</span>'
/plugins/plugin-5/mode uint32 2
/plugins/plugin-6 'separator'
/plugins/plugin-6/style uint32 0
/plugins/plugin-7 'systemload'
/plugins/plugin-7/cpu/color [<0.96078431372549022>, <0.76078431372549016>, <0.066666666666666666>, <1.0>]
/plugins/plugin-7/cpu/enabled true
/plugins/plugin-7/cpu/label ''
/plugins/plugin-7/memory/color [<0.90196078431372551>, <0.38039215686274508>, <0.0>, <1.0>]
/plugins/plugin-7/memory/label ''
/plugins/plugin-7/network/enabled false
/plugins/plugin-7/swap/enabled false
/plugins/plugin-7/system-monitor-command 'x-terminal-emulator -e htop'
/plugins/plugin-7/uptime/enabled false
/plugins/plugin-8 'separator'
/plugins/plugin-8/style uint32 0
/plugins/plugin-9 'separator'
/plugins/plugin-9/style uint32 0

Almost identical to the original @hhh versions except for the positioning that should work for all screen dimensions, click icon to toggle minimization, and tidied up network in systray. I've also made 'x-terminal-emulator -e htop' the command for the systemload plugin.

Some day we might consider the best colours for CPU and RAM if we decide to add the systemload plugin to the default panel. Default colours were a bit hard to see on our desktop.

johnraff · 2025-04-24 04:42:37

@hhh could you take a quick look at https://forums.bunsenlabs.org/viewtopic … 23#p142423 and choose either labbe-min-bark or material-solarized-suruplusplus-bark for our provisional default icon theme? Once that's decided I don't think there's much stopping me pushing out an updated bunsen-configs that configures a desktop close to what Carbon will be like.

Oh yes, default highlight and background colours for things like dmenu and the terminal. I can probably find those in the gtk or openbox theme files...

hhh · 2025-04-25 14:46:37

@johnraff, it has to be Material-Solarized-bark++ and sage++ because labbe-min* inherits a bunch of icons from those.

If you push the package it will make it easier to see what's still incomplete. Nice work, dudes!

micko01 · 2025-04-25 21:17:02

hhh wrote:

@johnraff, it has to be Material-Solarized-bark++ and sage++ because labbe-min* inherits a bunch of icons from those.
If you push the package it will make it easier to see what's still incomplete. Nice work, dudes!

The way it is set up is that labbe-min-${flavour} inherits Material-Solarized-${flavour}++ and therefore each labbe flavour has a hard depend on each S++ flavour. The reason I did this is because:

the 'folder' icon was deemed 'chubby' so labbe's folder icon is default
it's far easier to add icons to labbe, although it's fairly trivial to add symlinks to S++

BTW, each S-${flavour}++ inherits S-common++ (emotes, emblems etc) which in turn inherits adwaita which in turn inherits hicolor, so really we should never rarely miss an icon.

So from a user perspective, simply installing any labbe-min-$flavour will grab the corresponding S-$flavour++ and S-common++ at a minimum.

johnraff · 2025-04-26 04:30:31

So we do have a choice of the labbe-min- or material-solarized- icons for default.
@hhh Which do you think? labbe-min for the convenience reasons @micko01 posted, or solarized if you prefer the appearance?
Easy to change the default later on if we want to.

hhh · 2025-04-26 16:39:49

I missed the "chubby" folder discussion (and I won't fat-shame a folder ), but if @micko is willing to maintain an icon set, let it be the easiest one (labbe).

micko01 · 2025-04-26 21:08:58

hhh wrote:

I missed the "chubby" folder discussion (and I won't fat-shame a folder ), but if @micko is willing to maintain an icon set, let it be the easiest one (labbe).

I found the post https://forums.bunsenlabs.org/viewtopic … 34#p141434

johnraff wrote:

plain directory icons look a bit chubby

micko01 · 2025-04-26 23:03:36

Just added some more mimetypes that were missing. Uploaded to github/labbe-min-ng and the boron and carbon-trixie repos

The kernel one requires some code. ~/.local/share/mime/packages/application-linux-kernel.xml

<?xml version="1.0" encoding="UTF-8"?>
<mime-info xmlns="http://www.freedesktop.org/standards/shared-mime-info">
  <mime-type type="application/linux-kernel">
    <comment>new mime type</comment>
    <glob pattern="vmlinuz*"/>
  </mime-type>
</mime-info>

Then

update-mime-database -n ~/.local/share/mime

Are we interested in adding that for Carbon?

Last edited by micko01 (2025-04-27 02:18:07)

johnraff · 2025-04-27 04:47:27

^Looks good!
You've created a new mimetype for kernel vmlinuz files, right?

Since this is something - I imagine - that will be installed by bunsen-configs, it might be cleaner to do it at the system level than adding something to each user's config. (I don't see a new mimetype as something individual users will have any reason to tweak. Anyway a user can still override it with a file in ~/.local/share/mime/packages/ if they really want to.)

ie install that xml file in /usr/share/mime/packages/ ?
It might need a bit of code in debian/postinst to get it registered, although debhelper is usually pretty good at picking up this kind of thing by itself.

PS did you have to declare an icon in a .desktop file in /usr/share/applications/ or /.local/share/applications to get the icon associated?

PS2 I've also seen a (2011) case where an icon reference is added to the xml file - maybe this allows non-standard icon naming?

Last edited by johnraff (2025-04-27 05:04:25)

micko01 · 2025-04-27 05:49:05

johnraff wrote:

^Looks good!
You've created a new mimetype for kernel vmlinuz files, right?

Not a new mine-type but a glob pattern vmlinuz* (based on the filename) that matches to "application/linux-kernel".

johnraff wrote:

Since this is something - I imagine - that will be installed by bunsen-configs, it might be cleaner to do it at the system level than adding something to each user's config. (I don't see a new mimetype as something individual users will have any reason to tweak. Anyway a user can still override it with a file in ~/.local/share/mime/packages/ if they really want to.)
ie install that xml file in /usr/share/mime/packages/ ?
It might need a bit of code in debian/postinst to get it registered, although debhelper is usually pretty good at picking up this kind of thing by itself.

I'll try it to see if it overrides the the silly windows icon as well by installing system wide. Then we could still add it to bunsen-configs just with a /usr/share/mime/packages/ install path. I'm pretty sure update-mime-database runs at boot anyway, but I suppose it would be fine in a postinstall if a user installs configs later.

johnraff wrote:

PS did you have to declare an icon in a .desktop file in /usr/share/applications/ or /.local/share/applications to get the icon associated?

Nope.

johnraff wrote:

PS2 I've also seen a (2011) case where an icon reference is added to the xml file - maybe this allows non-standard icon naming?

Yes that is what that case's answer implies at least. No such shenanigans with my simple approach. I think I'll change the comment though as is it's non descriptive.

EDIT: I knocked up a quick package and removed my ~/.local/mime dir and rebooted. First I checked and the ugly windows icon was my on /vmlinuz. Installed my package, simply just the xml file and it worked fine - no postinst - apt takes care of mime-database in any install anyway. My nice tux interpretation is now the mime-icon for vmlinuz*. If you like I'll add it to bunsen-configs. I mean what genius decided these mime associations when a linux kernel image no less gets a smelly windows icon?

Last edited by micko01 (2025-04-27 06:44:08)

johnraff · 2025-04-27 09:16:45

micko01 wrote:

johnraff wrote:
You've created a new mimetype for kernel vmlinuz files, right?
Not a new mine-type but a glob pattern vmlinuz* (based on the filename) that matches to "application/linux-kernel".

The mimetype "application/linux-kernel" does not exist on my Boron system.

john@boron:/usr/share/mime$ grep -ri kernel .
john@boron:/usr/share/mime$ find . -iname '*linux*'
./application/x-font-linux-psf.xml
./application/x-gz-font-linux-psf.xml

Installed my package, simply just the xml file and it worked fine - no postinst - apt takes care of mime-database in any install anyway.

I suspect it might be debhelper at the package build time, rather than apt at install time, but not 100% sure. In the built binary, is there a postinst file inside DEBIAN/? Maybe a update-mime-database command there?

...what genius decided these mime associations when a linux kernel image no less gets a smelly windows icon?

john@boron:/boot$ file -i vmlinuz-6.1.0-31-amd64
vmlinuz-6.1.0-31-amd64: application/octet-stream; charset=binary
john@boron:/boot$ xdg-mime query filetype vmlinuz-6.1.0-31-amd64
application/x-ms-dos-executable

Note how in this case 'file' and 'xdg-mime' give different results.
'file' just looks at the file content, ignoring the filename: "application/octet-stream" is the fallback when no mimetype can be determined.
'xdg-mime' is a bash script in xdg-utils that first looks for a file extension, then (as in this case) if there isn't one it reverts to calling 'gio info /boot/vmlinuz-6.1.0-31-amd64' and parsing the output to find

standard::content-type: application/x-ms-dos-executable

So it's coming from gio. I guess that's its best guess for a binary blob.

Anyway, no utility seems to have any concept of a "application/linux-kernel" mimetype.

---

I installed your xml file as /usr/share/mime/packages/bunsen-configs.xml and ran 'sudo update-mime-database -n /usr/share/mime'

Now:

john@boron:/boot$ file -i vmlinuz-6.1.0-31-amd64
vmlinuz-6.1.0-31-amd64: application/octet-stream; charset=binary
john@boron:/boot$ xdg-mime query filetype vmlinuz-6.1.0-31-amd64
application/linux-kernel

And temporarily (this is Boron) changed the icon theme to labbe-material-bark to see the penguin icons on the vmlinuz files.

My nice tux interpretation is now the mime-icon for vmlinuz*. If you like I'll add it to bunsen-configs.

Yes please.

For anyone who wants to dig into mime types:
https://www.baeldung.com/linux/file-mime-types
https://wiki.archlinux.org/title/XDG_MIME_Applications
https://wiki.debian.org/MIME
https://wiki.debian.org/MimeTypesSupport
https://docs.oracle.com/cd/E19957-01/81 … index.html

EDIT: forgot to include the useful Arch Wiki page.

Last edited by johnraff (2025-04-27 23:48:18)

micko01 · 2025-04-27 10:57:29

johnraff wrote:

The mimetype "application/linux-kernel" does not exist on my Boron system.

Then I suppose I did create a mime-type

johnraff wrote:

Installed my package, simply just the xml file and it worked fine - no postinst - apt takes care of mime-database in any install anyway.
I suspect it might be debhelper at the package build time, rather than apt at install time, but not 100% sure. In the built binary, is there a postinst file inside DEBIAN/? Maybe a update-mime-database command there?

Absolutely nothing. It's all apt running update-mime-database.

johnraff wrote:

john@boron:/boot$ file -i vmlinuz-6.1.0-31-amd64
vmlinuz-6.1.0-31-amd64: application/octet-stream; charset=binary
john@boron:/boot$ xdg-mime query filetype vmlinuz-6.1.0-31-amd64
application/x-ms-dos-executable
Note how in this case 'file' and 'xdg-mime' give different results.
'file' just looks at the file content, ignoring the filename: "application/octet-stream" is the fallback when no mimetype can be determined.
'xdg-mime' is a bash script in xdg-utils that first looks for a file extension, then (as in this case) if there isn't one it reverts to calling 'gio info /boot/vmlinuz-6.1.0-31-amd64' and parsing the output to find
---
So it's coming from gio. I guess that's its best guess for a binary blob.
Anyway, no utility seems to have any concept of a "application/linux-kernel" mimetype.

Glad we cleared that up. Thanks

johnraff wrote:

I installed your xml file as /usr/share/mime/packages/bunsen-configs.xml and ran 'sudo update-mime-database -n /usr/share/mime'
Now
john@boron:/boot$ file -i vmlinuz-6.1.0-31-amd64
vmlinuz-6.1.0-31-amd64: application/octet-stream; charset=binary
john@boron:/boot$ xdg-mime query filetype vmlinuz-6.1.0-31-amd64
application/linux-kernel
And temporarily (this is Boron) changed the icon theme to labbe-material-bark to see the penguin icons on the vmlinuz files.

Nice .

johnraff wrote:

My nice tux interpretation is now the mime-icon for vmlinuz*. If you like I'll add it to bunsen-configs.
Yes please.

Working on it.

#61 2025-04-04 09:55:30

Re: Carbon Themes (beta version)

#62 2025-04-05 04:45:02

Re: Carbon Themes (beta version)

#63 2025-04-05 12:07:46

Re: Carbon Themes (beta version)

#64 2025-04-06 06:27:23

Re: Carbon Themes (beta version)

#65 2025-04-06 07:18:00

Re: Carbon Themes (beta version)

#66 2025-04-06 08:48:47

Re: Carbon Themes (beta version)

#67 2025-04-06 09:04:21

Re: Carbon Themes (beta version)

#68 2025-04-07 01:04:05

Re: Carbon Themes (beta version)

#69 2025-04-10 07:56:08

Re: Carbon Themes (beta version)

#70 2025-04-24 04:42:37

Re: Carbon Themes (beta version)

#71 2025-04-25 14:46:37

Re: Carbon Themes (beta version)

#72 2025-04-25 21:17:02

Re: Carbon Themes (beta version)

#73 2025-04-26 04:30:31

Re: Carbon Themes (beta version)

#74 2025-04-26 16:39:49

Re: Carbon Themes (beta version)

#75 2025-04-26 21:08:58

Re: Carbon Themes (beta version)

#76 2025-04-26 23:03:36

Re: Carbon Themes (beta version)

#77 2025-04-27 04:47:27

Re: Carbon Themes (beta version)

#78 2025-04-27 05:49:05

Re: Carbon Themes (beta version)

#79 2025-04-27 09:16:45

Re: Carbon Themes (beta version)

#80 2025-04-27 10:57:29

Re: Carbon Themes (beta version)

Board footer