Boron Graphics

johnraff · 2023-04-12 01:34:01

Are there any candidates for the default Boron wallpaper?
Decision about round corners, and/or icons on the menu?
Could something like this be done?

hhh · 2023-04-12 06:58:34

Give me a half hour to port it to Openbox.

hhh · 2023-04-12 07:16:44

Half an hour? Just find the wall and change the Yaru icon and GTK theme, jgmenu does the rest!

Pardon my wonky font sizes, I'm still setting this desktop up.

https://packages.debian.org/bookworm/yaru-theme-gtk

https://packages.debian.org/bookworm/yaru-theme-icon

Last edited by hhh (2023-04-12 07:21:38)

johnraff · 2023-04-13 05:38:39

^Quite fetching indeed.

Nit-picking:
It's a pity that thin white outline on the windows gets broken at the round corners.
That blue is beautiful - wallpaper highlights and and icons - but I wonder if some users might find it a bit distracting?
If it was desaturated and darkened slightly would it ruin the whole effect?

Can I (or you) post a link to that screenshot on the public forum? 8bit was asking: https://forums.bunsenlabs.org/viewtopic … 71#p127071

Last edited by johnraff (2023-04-13 05:41:45)

hhh · 2023-04-14 04:01:20

The outline shouldn't be white in the first place. This was the ten minute mock-up, it needs some tweaks! A dark outline will alleviate some of that harshness, I think.

Leave the blue alone, the idea is that you can blob to another Yaru color scheme with just a few clicks. A couple of them (the Yaru colors) are very mellow.

By all means, repost the scrot!

johnraff · 2023-04-14 06:35:02

^Yes you're right, we've got plenty of greyish unobtrusive themes easily available via BLOB. Good to have something a bit brighter as default this time.

---
bunsen-blob is now a separate package, just uploaded. An apt upgrade should fetch it in as a Recommends of bunsen-utilities.

Last edited by johnraff (2023-04-14 06:41:02)

johnraff · 2023-04-18 07:19:27

hhh wrote:

Half an hour? Just find the wall and change the Yaru icon and GTK theme, jgmenu does the rest!
https://imgur.com/R8Vof88t.png
Pardon my wonky font sizes, I'm still setting this desktop up.
https://packages.debian.org/bookworm/yaru-theme-gtk
https://packages.debian.org/bookworm/yaru-theme-icon

Any chance of a download link to that wallpaper so I can set it in my test VM?
(Just installed yaru theme and icons, and set both to Yaru-blue-dark.)

hhh · 2023-04-20 07:12:59

johnraff wrote:

Any chance of a download link to that wallpaper so I can set it in my test VM?
(Just installed yaru theme and icons, and set both to Yaru-blue-dark.)

I like that your liking this, John. The wall is B&W except for the flowers (nice editing by the content creator). This is how we can get our foot in the door to, you know, color on our desktop OOTB.

That and BLOB with more matching wallpapers for the different Yaru colors.

Last edited by hhh (2023-04-20 07:17:48)

johnraff · 2023-04-20 08:32:37

Thanks!

johnraff · 2023-04-24 07:34:02

@hhh what do you think of this icon theme?
https://forums.bunsenlabs.org/viewtopic … 15#p127115
https://github.com/rtlewis88/rtl88-Them … -Solarized

A bit extreme?
I guess the wallpaper would have to be tweaked to match the cyan too...

hhh · 2023-04-25 06:05:04

Dude, if you like it, I like it. Looks great. I'll spin a preview tomorrow.

johnraff · 2023-04-26 06:50:52

8bit found that Material-Solarized-Suru++ icon theme and posted his menu as a response to my comment about the icons previously looking like missing teeth. He cheated by making a menu where all the icons were present - I think we'd still likely have to make a few if we were going to have icons on the menu by default.

That luminous cyan is quite striking for sure. Not sure whether some people might find it a bit over the top.

The blue Yaru desktop is very pretty, but I'm not 100% sure about the blue yaru icon theme. The folder icons are beautiful but the various apps' systray icons look rather old-school.

Another alternative might be to recolour the Papirus Yaru icons to blue. They're svg so it might not be hard.

johnraff · 2023-05-06 01:42:47

johnraff wrote:

The blue Yaru desktop is very pretty, but I'm not 100% sure about the blue yaru icon theme. The folder icons are beautiful but the various apps' systray icons look rather old-school.
Another alternative might be to recolour the Papirus Yaru icons to blue. They're svg so it might not be hard.

Tried that: https://forums.bunsenlabs.org/viewtopic … 53#p127453 and I thought it looked quite nice.

Getting a couple of provisional graphics decisions made in the next day or so will determine whether or not we can put out a first alpha iso in May: https://forums.bunsenlabs.org/viewtopic … 38#p127538

We can certainly revise all those choices for the iso(s) following, but it would enable us to get something out.

hhh · 2023-05-14 04:22:34

Umm.. https://i.imgur.com/luKCwk6.png

Freaking gorgeous. And use you Picom settings, that is some luscious rounding. Chill the shadow a bit, though.

Last edited by hhh (2023-05-14 04:22:51)

hhh · 2023-05-14 05:26:35

@John, if you get a moment, post your picom.conf.

johnraff · 2023-05-14 07:06:20

Here's the picom shadow section:

#################################
#
#  Shadows
#
#################################

# Enabled client-side shadows on windows. Note desktop windows
# (windows with '_NET_WM_WINDOW_TYPE_DESKTOP') never get shadow,
# unless explicitly requested using the wintypes option.
#
# shadow = false
shadow = true;

# The blur radius for shadows, in pixels. (defaults to 12)
# shadow-radius = 12
shadow-radius = 8;

# The opacity of shadows. (0.0 - 1.0,  defaults to 0.75)
shadow-opacity = 0.5

# The left offset for shadows, in pixels. (defaults to -15)
# shadow-offset-x = -15
shadow-offset-x = -4;

# The top offset for shadows, in pixels. (defaults to -15)
# shadow-offset-y = -15
shadow-offset-y = -4;

# Avoid drawing shadows on dock/panel windows. This option is deprecated,
# you should use the *wintypes* option in your config file instead.
#
# no-dock-shadow = false

# Don't draw shadows on drag-and-drop windows. This option is deprecated,
# you should use the *wintypes* option in your config file instead.
#
# no-dnd-shadow = false

#  Set if you want different colour shadows

# Red color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-red = 0

# Green color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-green = 0

# Blue color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-blue = 0

# Do not paint shadows on shaped windows. Note shaped windows
# here means windows setting its shape through X Shape extension.
# Those using ARGB background is beyond our control.
# Deprecated, use
#   shadow-exclude = 'bounding_shaped'
# or
#   shadow-exclude = 'bounding_shaped && !rounded_corners'
# instead.
#
# shadow-ignore-shaped = ''

# Specify a list of conditions of windows that should have no shadow.
#
# examples:
#   shadow-exclude = "n:e:Notification";
#
#  The shadow exclude options are helpful if you have shadows enabled.
#  Due to the way picom draws its shadows, certain applications will have visual glitches
#  (most applications are fine, only apps that do weird things with xshapes or argb are affected).
#  This list includes all the affected apps I found in my testing.
#  The "! name~=''" part excludes shadows on any "Unknown" windows, this prevents a visual glitch with the XFWM alt tab switcher.
#  The "_GTK_FRAME_EXTENTS@:c" entry is to fix dual shadows with GTK3 Client Side Decorations.
# shadow-exclude = []
shadow-exclude = [
    "! name~=''",
#    "name = 'jgmenu'",
    "name = 'tint2'",
    "name = 'Notification'",
    "name = 'wbar'",
#    "name = 'Plank'",
    "name = 'Docky'",
    "name = 'Kupfer'",
#    "name = 'xfce4-notifyd'",
    "name *= 'VirtualBox'",
    "name *= 'VLC'",
    "name *= 'picom'",
    "name *= 'Chromium'",
    "name *= 'Chrome'",
    "class_g ?= 'plank'", # see wintypes
    "class_g ?= 'Conky'",
    "class_g = 'Kupfer'",
    "class_g = 'Synapse'",
    "class_g ?= 'Notify-osd'",
    "class_g ?= 'Cairo-dock'",
#    "class_g ?= 'Xfce4-notifyd'",
    "class_g ?= 'Xfce4-power-manager'",
    "_GTK_FRAME_EXTENTS@:c"
];

# Specify a X geometry that describes the region in which shadow should not
# be painted in, such as a dock window region. Use
#    shadow-exclude-reg = "x10+0+0"
# for example, if the 10 pixels on the bottom of the screen should not have shadows painted on.
#
# shadow-exclude-reg = ""

# Crop shadow of a window fully on a particular Xinerama screen to the screen.
# xinerama-shadow-crop = false

I can't figure out what's happening when I change the shadow-radius and offset figures. Is opacity OK at 0.5? Maybe you could play with it a bit and find something you like better.

Here's the rounded corner section:

# test rounded corners
corner-radius = 6;

rounded-corners-exclude = [
  "window_type = 'menu'",
  "window_type = 'dropdown_menu'",
  "window_type = 'popup_menu'",
  "window_type = 'utility'",
  "class_g = 'Polybar'",
  "class_g = 'Rofi'",
  "class_g = 'Dunst'"
];

# Try to detect windows with rounded corners and don't consider them
# shaped windows. The accuracy is not very high, unfortunately.
#
# detect-rounded-corners = false
detect-rounded-corners = true;

For that matter, you might want to look at the whole picom file, maybe there's something else there that needs tweaking?
EDIT: cross-posted. But anyway here it is:

##  Picom user configuration file (~/.config/picom.conf)
##  written for BunsenLabs Beryllium
##  with reference to: /usr/share/doc/picom/examples/picom.sample.conf
##  http://duncanlock.net/blog/2013/06/07/how-to-switch-to-compton-for-beautiful-tear-free-compositing-in-xfce/
##  and https://forums.bunsenlabs.org/viewtopic.php?pid=61249#p61249
##
##  Various people have contributed to this file,
##  so the meaning of "I" is not well defined.
##
##  In most cases 'man picom' has more information.
##  See also: https://wiki.archlinux.org/title/Picom


#################################
#
#  Shadows
#
#################################

# Enabled client-side shadows on windows. Note desktop windows
# (windows with '_NET_WM_WINDOW_TYPE_DESKTOP') never get shadow,
# unless explicitly requested using the wintypes option.
#
# shadow = false
shadow = true;

# The blur radius for shadows, in pixels. (defaults to 12)
# shadow-radius = 12
shadow-radius = 8;

# The opacity of shadows. (0.0 - 1.0,  defaults to 0.75)
shadow-opacity = 0.5

# The left offset for shadows, in pixels. (defaults to -15)
# shadow-offset-x = -15
shadow-offset-x = -4;

# The top offset for shadows, in pixels. (defaults to -15)
# shadow-offset-y = -15
shadow-offset-y = -4;

# Avoid drawing shadows on dock/panel windows. This option is deprecated,
# you should use the *wintypes* option in your config file instead.
#
# no-dock-shadow = false

# Don't draw shadows on drag-and-drop windows. This option is deprecated,
# you should use the *wintypes* option in your config file instead.
#
# no-dnd-shadow = false

#  Set if you want different colour shadows

# Red color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-red = 0

# Green color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-green = 0

# Blue color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-blue = 0

# Do not paint shadows on shaped windows. Note shaped windows
# here means windows setting its shape through X Shape extension.
# Those using ARGB background is beyond our control.
# Deprecated, use
#   shadow-exclude = 'bounding_shaped'
# or
#   shadow-exclude = 'bounding_shaped && !rounded_corners'
# instead.
#
# shadow-ignore-shaped = ''

# Specify a list of conditions of windows that should have no shadow.
#
# examples:
#   shadow-exclude = "n:e:Notification";
#
#  The shadow exclude options are helpful if you have shadows enabled.
#  Due to the way picom draws its shadows, certain applications will have visual glitches
#  (most applications are fine, only apps that do weird things with xshapes or argb are affected).
#  This list includes all the affected apps I found in my testing.
#  The "! name~=''" part excludes shadows on any "Unknown" windows, this prevents a visual glitch with the XFWM alt tab switcher.
#  The "_GTK_FRAME_EXTENTS@:c" entry is to fix dual shadows with GTK3 Client Side Decorations.
# shadow-exclude = []
shadow-exclude = [
    "! name~=''",
#    "name = 'jgmenu'",
    "name = 'tint2'",
    "name = 'Notification'",
    "name = 'wbar'",
#    "name = 'Plank'",
    "name = 'Docky'",
    "name = 'Kupfer'",
#    "name = 'xfce4-notifyd'",
    "name *= 'VirtualBox'",
    "name *= 'VLC'",
    "name *= 'picom'",
    "name *= 'Chromium'",
    "name *= 'Chrome'",
    "class_g ?= 'plank'", # see wintypes
    "class_g ?= 'Conky'",
    "class_g = 'Kupfer'",
    "class_g = 'Synapse'",
    "class_g ?= 'Notify-osd'",
    "class_g ?= 'Cairo-dock'",
#    "class_g ?= 'Xfce4-notifyd'",
    "class_g ?= 'Xfce4-power-manager'",
    "_GTK_FRAME_EXTENTS@:c"
];

# Specify a X geometry that describes the region in which shadow should not
# be painted in, such as a dock window region. Use
#    shadow-exclude-reg = "x10+0+0"
# for example, if the 10 pixels on the bottom of the screen should not have shadows painted on.
#
# shadow-exclude-reg = ""

# Crop shadow of a window fully on a particular Xinerama screen to the screen.
# xinerama-shadow-crop = false


#################################
#           Fading              #
#################################

# Fade windows in/out when opening/closing and when opacity changes,
#  unless no-fading-openclose is used.
# fading = false
fading = true;

# Opacity change between steps while fading in. (0.01 - 1.0, defaults to 0.028)
# fade-in-step = 0.028
fade-in-step = 0.06;

# Opacity change between steps while fading out. (0.01 - 1.0, defaults to 0.03)
# fade-out-step = 0.03
fade-out-step = 0.06;

# The time between steps in fade step, in milliseconds. (> 0, defaults to 10)
# fade-delta = 4

#  Specify a list of conditions of windows that should not be faded.
#  (Some might need setting in wintypes below.)
fade-exclude = ["name = 'jgmenu'"];

#  Fade windows in/out when opening/closing
#no-fading-openclose = true;

#  Do not fade destroyed ARGB windows with WM frame. Workaround of bugs in Openbox, Fluxbox, etc.
no-fading-destroyed-argb = true;


#################################
#   Transparency / Opacity      #
#################################

# Opacity of inactive windows. (0.1 - 1.0, defaults to 1.0)
# inactive-opacity = 1
inactive-opacity = 0.8;

# Opacity of window titlebars and borders. (0.1 - 1.0, disabled by default)
# frame-opacity = 0.7;
frame-opacity = 1.0;

# Default opacity for dropdown menus and popup menus. (0.0 - 1.0, defaults to 1.0)
# Option `menu-opacity` is deprecated, and will be removed.
# Please use the wintype option `opacity` of `popup_menu` and `dropdown_menu` instead.
# menu-opacity = 1.0;

# Let inactive opacity set by -i override the '_NET_WM_OPACITY' values of windows.
# inactive-opacity-override = true
inactive-opacity-override = false;

# Default opacity for active windows. (0.0 - 1.0, defaults to 1.0)
active-opacity = 1.0;

# Dim inactive windows. (0.0 - 1.0, defaults to 0.0)
# inactive-dim = 0.2

# Specify a list of conditions of windows that should always be considered focused.
# focus-exclude = []
#focus-exclude = [ "class_g = 'Cairo-clock'" ];

# Use fixed inactive dim value, instead of adjusting according to window opacity.
# inactive-dim-fixed = 1.0

# Specify a list of opacity rules, in the format `PERCENT:PATTERN`,
# like `50:name *= "Firefox"`. picom-trans is recommended over this.
# Note we don't make any guarantee about possible conflicts with other
# programs that set '_NET_WM_WINDOW_OPACITY' on frame or client windows.
# example:
#    opacity-rule = [ "80:class_g = 'URxvt'" ];
#
# opacity-rule = []

# alpha-step seems no longer to be supported
# https://github.com/yshui/picom/pull/48 https://github.com/yshui/picom/issues/359
# alpha-step = 0.06;


#################################
#     Background-Blurring       #
#################################

# Parameters for background blurring, see the *BLUR* section for more information.
# blur-method =
# blur-size = 12
#
# blur-deviation = false

# Blur background of semi-transparent / ARGB windows.
# Bad in performance, with driver-dependent behavior.
# The name of the switch may change without prior notifications.
#
# blur-background = false

# Blur background of windows when the window frame is not opaque.
# Implies:
#    blur-background
# Bad in performance, with driver-dependent behavior. The name may change.
#
# blur-background-frame = false

# Use fixed blur strength rather than adjusting according to window opacity.
# Do not let blur radius adjust based on window opacity.
blur-background-fixed = false;

# Specify the blur convolution kernel, with the following format:
# example:
#   blur-kern = "5,5,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1";
#
# blur-kern = ''
blur-kern = "3x3box";

# Exclude conditions for background blur.
# blur-background-exclude = []
blur-background-exclude = [
  "window_type = 'dock'",
  "window_type = 'desktop'",
  "_GTK_FRAME_EXTENTS@:c"
];


#################################
#       General Settings        #
#################################

# Enable remote control via D-Bus. See the *D-BUS API* section in the manual for more details.
# The D-Bus methods and signals are not yet stable, thus undocumented right now.
# dbus = false

# Try to detect WM windows (a non-override-redirect window with no
# child that has 'WM_STATE') and mark them as active.
#
# mark-wmwin-focused = false
mark-wmwin-focused = true;

# Mark override-redirect windows that doesn't have a child window with 'WM_STATE' focused.
# mark-ovredir-focused = false
mark-ovredir-focused = true;

# test rounded corners
corner-radius = 6;

rounded-corners-exclude = [
  "window_type = 'menu'",
  "window_type = 'dropdown_menu'",
  "window_type = 'popup_menu'",
  "window_type = 'utility'",
  "class_g = 'Polybar'",
  "class_g = 'Rofi'",
  "class_g = 'Dunst'"
];

# Try to detect windows with rounded corners and don't consider them
# shaped windows. The accuracy is not very high, unfortunately.
#
# detect-rounded-corners = false
detect-rounded-corners = true;

# Detect '_NET_WM_OPACITY' on client windows, useful for window managers
# not passing '_NET_WM_OPACITY' of client windows to frame windows.
# This prevents opacity being ignored for some apps.
# For example without this enabled my xfce4-notifyd is 100% opacity no matter what.
#
# detect-client-opacity = false
detect-client-opacity = true;

# Use EWMH '_NET_ACTIVE_WINDOW' to determine currently focused window,
# rather than listening to 'FocusIn'/'FocusOut' event. Might have more accuracy,
# provided that the WM supports it. (openbox should be OK)
#
use-ewmh-active-win = true;

# Unredirect all windows if a full-screen opaque window is detected,
# to maximize performance for full-screen windows. Known to cause flickering
# when redirecting/unredirecting windows.
# paint-on-overlay may make the flickering less obvious.
#
unredir-if-possible = true;

# Delay before unredirecting the window, in milliseconds. Defaults to 0.
# unredir-if-possible-delay = 0

# Conditions of windows that shouldn't be considered full-screen for unredirecting screen.
# unredir-if-possible-exclude = []

# Use 'WM_TRANSIENT_FOR' to group windows, and consider windows
# in the same group focused at the same time.
#
# detect-transient = false
detect-transient = true;

# Use 'WM_CLIENT_LEADER' to group windows, and consider windows in the same
# group focused at the same time. 'WM_TRANSIENT_FOR' has higher priority if
# detect-transient is enabled, too.
#
# detect-client-leader = false
detect-client-leader = true;

# Resize damaged region by a specific number of pixels.
# A positive value enlarges it while a negative one shrinks it.
# If the value is positive, those additional pixels will not be actually painted
# to screen, only used in blur calculation, and such. (Due to technical limitations,
# with use-damage, those pixels will still be incorrectly painted to screen.)
# Primarily used to fix the line corruption issues of blur,
# in which case you should use the blur radius value here
# (e.g. with a 3x3 kernel, you should use `--resize-damage 1`,
# with a 5x5 one you use `--resize-damage 2`, and so on).
# May or may not work with *--glx-no-stencil*. Shrinking doesn't function correctly.
#
# resize-damage = 1

# Specify a list of conditions of windows that should be painted with inverted color.
# Resource-hogging, and is not well tested.
#
# invert-color-include = []

# Disable the use of damage information.
# This cause the whole screen to be redrawn everytime, instead of the part of the screen
# has actually changed. Potentially degrades the performance, but might fix some artifacts.
# The opposing option is use-damage
#
# no-use-damage = false
use-damage = true

# Do not use EWMH to detect fullscreen windows.
# Reverts to checking if a window is fullscreen based only on its size and coordinates.
#
# no-ewmh-fullscreen = false

# Dimming bright windows so their brightness doesn't exceed this set value.
# Brightness of a window is estimated by averaging all pixels in the window,
# so this could comes with a performance hit.
# Setting this to 1.0 disables this behaviour. Requires --use-damage to be disabled. (default: 1.0)
#
# max-brightness = 1.0

# Make transparent windows clip other windows like non-transparent windows do,
# instead of blending on top of them.
#
# transparent-clipping = false

# Set the log level. Possible values are:
#  "trace", "debug", "info", "warn", "error"
# in increasing level of importance. Case doesn't matter.
# If using the "TRACE" log level, it's better to log into a file
# using *--log-file*, since it can generate a huge stream of logs.
#
# log-level = "debug"
log-level = "warn";

# Set the log file.
# If *--log-file* is never specified, logs will be written to stderr.
# Otherwise, logs will to written to the given file, though some of the early
# logs might still be written to the stderr.
# When setting this option from the config file, it is recommended to use an absolute path.
#
# log-file = '/path/to/your/log/file'

# Show all X errors (for debugging)
# show-all-xerrors = false

# Write process ID to a file.
# write-pid-path = '/path/to/your/log/file'

#################################
#
#  Window type settings
#
#################################

# 'WINDOW_TYPE' is one of the 15 window types defined in EWMH standard:
#     "unknown", "desktop", "dock", "toolbar", "menu", "utility",
#     "splash", "dialog", "normal", "dropdown_menu", "popup_menu",
#     "tooltip", "notification", "combo", and "dnd".
#
# Following per window-type options are available: ::
#
#   fade, shadow:::
#     Controls window-type-specific shadow and fade settings.
#
#   opacity:::
#     Controls default opacity of the window type.
#
#   focus:::
#     Controls whether the window of this type is to be always considered focused.
#     (By default, all window types except "normal" and "dialog" has this on.)
#
#   full-shadow:::
#     Controls whether shadow is drawn under the parts of the window that you
#     normally won't be able to see. Useful when the window has parts of it
#     transparent, and you want shadows in those areas.
#
#   redir-ignore:::
#     Controls whether this type of windows should cause screen to become
#     redirected again after been unredirected. If you have unredir-if-possible
#     set, and doesn't want certain window to cause unnecessary screen redirection,
#     you can set this to `true`.
#
#wintypes:
#{
#  tooltip = { fade = true; shadow = true; opacity = 0.75; focus = true; full-shadow = false; };
#  dock = { shadow = false; }
#  dnd = { shadow = false; }
#  popup_menu = { opacity = 0.8; }
#  dropdown_menu = { opacity = 0.8; }
#};

wintypes:
{
  dock = { shadow = false; };
  tooltip = { fade = false; shadow = false; };
  menu = { fade = false; };
  dropdown_menu = { fade = false; opacity = 1.0; };
  popup_menu =  { fade = false; opacity = 1.0; };
};


########################################################################
###  "advanced" machine specific options  ###

#  It is possible to set these in /etc/bunsen/picom-startup
#  where they will be applied for all users, but can also be set here.
#  Any settings in /etc/bunsen/picom-startup will have priority.
#
#  Some old (2017) forum threads which might be of historical interest:
#  https://forums.bunsenlabs.org/viewtopic.php?id=4176
#  https://forums.bunsenlabs.org/viewtopic.php?pid=61249#p61249
#  https://forums.bunsenlabs.org/viewtopic.php?id=3699
#
#  Two graphics test pages:
#  This one is flashing green and red fast enough that it should look
#  like a flickery orange colour:
#  https://launchpadlibrarian.net/274755154/kenjo_vidtest_60fps.mp4
#  This is a screen tearing test for vsync:
#  https://www.youtube.com/watch?v=MfL_JkcEFbE

########################################################################

# Daemonize process. Fork to background after initialization. Causes issues with certain (badly-written) drivers.
# In a BunsenLabs sesssion, picom is forked anyway, so this setting is not needed.
# daemon = false


#################################
#
#  Backend
#
#################################

#  Backend to use: "xrender", "glx" or "xr_glx_hybrid". xrender is the default one.
#  GLX backend is typically much faster but depends on a sane driver.

#backend = "glx";

# Enable/disable VSync.
# vsync = false
# vsync = true


#################################
#
#  GLX backend
#
#################################

# GLX backend: Avoid using stencil buffer, useful if you don't have a stencil buffer.
# This may not work with --blur-background. Tests show a 15% performance boost.
# Might cause incorrect opacity when rendering transparent content (but never
# practically happened) and may not work with blur-background.
# "My tests show a 15% performance boost. Recommended."
#
# glx-no-stencil = true

# GLX backend: Avoid rebinding pixmap on window damage.
# Probably could improve performance on rapid window content changes,
# but is known to break things on some drivers (LLVMpipe, xf86-video-intel, etc.).
# "This option causes lockups in Virtualbox."
# Recommended if it works.
#
# glx-no-rebind-pixmap = true

# GLX backend: Use specified GLSL fragment shader for rendering window contents.
# See `compton-default-fshader-win.glsl` and `compton-fake-transparency-fshader-win.glsl`
# in the source tree for examples.
#
# glx-fshader-win = ''

# Force all windows to be painted with blending. Useful if you
# have a glx-fshader-win that could turn opaque pixels transparent.
#
# force-win-blend = true

#################################

# Use X Sync fence to sync clients' draw calls, to make sure all draw
# calls are finished before picom starts drawing. Needed on nvidia-drivers
# with GLX backend for some users.
#
# xrender-sync-fence = false

# Specify refresh rate of the screen. If not specified or 0, picom will
# try detecting this with X RandR extension.
#
# refresh-rate = 60
#refresh-rate = 0

# Limit picom to repaint at most once every 1 / 'refresh_rate' second to
# boost performance. This should not be used with
#   vsync drm/opengl/opengl-oml
# as they essentially does sw-opti's job already,
# unless you wish to specify a lower refresh rate than the actual value.
#
# sw-opti =

Last edited by johnraff (2023-05-14 07:07:31)

johnraff · 2023-05-14 07:34:00

Yes I think the recoloured papirus icons with matching green look quite good with that Yaru theme. Maybe we can go with that?

Here's my lo-res VM. I've provisionally used the lithium-vertical tint2 and bigClock-lithium-light conky, but I'm sure you can do something better. Haven't touched the picom shadows at all.

Note also, the icons in the menu are that Material-Solarized-Suru++ that 8bital found. I've just discovered that it's possible for jgmenu to have a separate icon theme, and I think those cyan icons fit in quite well with the Yaru green, no? Of course whether to have menu icons or not is yet to be decided, but if we do then that looks to me a possible option. We'd have to add some symlinks to the icon theme, or change the icon names in the menu, so as not to have any missing icons, at least in the top-level menu.

Icons in pipemenus are impossible anyway, so there is still an argument that for consistency we should be icon-free throughout the menu. Users who switch to other themes might prefer not to have to reconfigure jgmenu every time too.

Maybe you could play with this stuff while I'm away and we should be in pretty good shape by late June?

Last edited by johnraff (2023-05-14 07:36:01)

hhh · 2023-05-24 03:31:41

Sorry for the delayed response.. I'll look at this in depth tomorrow. Thanks for the configs!

hhh · 2023-06-02 00:07:15

I've been doing some work, finding an Oomox version that actually produces a usable theme, then tweaking the Oomox-generated OB theme, and especially tweaking picom. Let me know what you think...

https://forums.bunsenlabs.org/viewtopic … 54#p127854

Last edited by hhh (2023-06-02 00:10:41)

hhh · 2023-06-02 00:17:51

^ Here's a less cluttered screenshot for your viewing pleasure...

#1 2023-04-12 01:34:01

Boron Graphics

#2 2023-04-12 06:58:34

Re: Boron Graphics

#3 2023-04-12 07:16:44

Re: Boron Graphics

#4 2023-04-13 05:38:39

Re: Boron Graphics

#5 2023-04-14 04:01:20

Re: Boron Graphics

#6 2023-04-14 06:35:02

Re: Boron Graphics

#7 2023-04-18 07:19:27

Re: Boron Graphics

#8 2023-04-20 07:12:59

Re: Boron Graphics

#9 2023-04-20 08:32:37

Re: Boron Graphics

#10 2023-04-24 07:34:02

Re: Boron Graphics

#11 2023-04-25 06:05:04

Re: Boron Graphics

#12 2023-04-26 06:50:52

Re: Boron Graphics

#13 2023-05-06 01:42:47

Re: Boron Graphics

#14 2023-05-14 04:22:34

Re: Boron Graphics

#15 2023-05-14 05:26:35

Re: Boron Graphics

#16 2023-05-14 07:06:20

Re: Boron Graphics

#17 2023-05-14 07:34:00

Re: Boron Graphics

#18 2023-05-24 03:31:41

Re: Boron Graphics

#19 2023-06-02 00:07:15

Re: Boron Graphics

#20 2023-06-02 00:17:51

Re: Boron Graphics

Board footer