Changing stuff to get used to the code.
Q.
How to exclude
[xdg-shell]from OSD preview. (alt-tab)
![]()
man labwc-config
hit / and search for windowSwitcher
No need for wlrctl for that.
This is built in action in both Labwc and Openbox.
<action name="Iconify" />
Iconify (minimize) focused window.
![]()
Dragging the screenshot to FF window does not work.
I needed to use the buttons to attached this image.
I think i read something about the dragging issue.
At least one step futher in running with Nvidia drivers.
To be continuedā¦
![]()
edit: installed digital font for clock. updated preview.
Nice ![]()
If you want normal window decorations for Firefox, checkā¦
Normal window decorations in Firefox
@muzqs What are your impressions after a few days with Labwc?
Mine are very positive ![]()
But for now, Iām focusing on Openbox for a few days - we have a lot of cool improvements, and it would be good to release a refreshed ISO soon.
In the beginning I had to push myself a bit. Jumping into new syntax.
Mainly because I am so fond of your work with jgmenu etc.
But after fiddling around I am starting to really like it.
Thats one reason I wanted it running on my baremetal nvidia box.
With Qemu i did“t have sound etc. I did“t want to invest in Qemu to fix those things.
![]()
Do you have a link?
You can close Jgmenu also by Esc key.
Jgmenu is for X11ā¦
If I decide to use Jgmenu with Labwc, I will probably implement some kind of āclose buttonsā using widgets - but that a long way. I will probably spend the next few weeks thoroughly exploring the foundations of Labwc and programs designed for Wayland.
I did“t made a bookmark of the post. Need some time to look if i can find it again.
![]()
Donāt waste time looking for it, itās not important at this point. It was probably something like killall jgmenu.
Frustrating weird behaviour. things where partly working.
Then i found a stupid Typo at the top of the xml.
F4<?xml version="1.0"?>
Came there without notice. ![]()
I am checking jgmenu and vis. Replaced terminator for foot.
The weird thing is that some commands from rc.xml are not working.
I have hotkey for colorizer-vis . But wont work.
As other scripts are fine and others not.
colorizer-vis -s
![]()
mabox-labwc Dark-Blue preview and fuzzel command.
Labwc is quick in response. The display is Crips&Clear in colors. Vis runs better than ever.
Fuzzel App Launcher.
fuzzel --background=212121ff --font Source Code Pro:style=Bold --text-color=1EE4FFff 3A9E70ff --prompt-color=1EE4FFff --match-color=03FA35ff --selection-color=1E90FFff --input-color=C5E0D6ff --border-color=1E90FFff --selection-text-color=E7EDF2ff --selection-match-color=E7EDF2ff --border-width=3 --border-radius=2
![]()
What I experience is that when i move scripts to /usr/local/bin.
They seam to work better.
Some scripts wont allways launch from panel from ~/bin.
![]()
Add this line to environment file:
PATH=$HOME/bin:$PATH
After a long break (1.5 years), Iāve been experimenting heavily with LabWC and LabWC + Noctalia for over two weeks nowā¦
I think something cool will come out of it ![]()
I cant remember about the bin. Maybe it had todo for some scripts i needed the full path not the ~. But it 's a while ago. Because I think some other scripts where running fineā¦
The images you posted on show me desktop, looks really cool. I have no eye for labwc myself at the moment. Really curious about the development of labwc ![]()
Hi guys.
There is a lot of noise lately around Noctalia (v5, they dropped QT). I saw someone who mixed it with Labwc and got a nice, responsive system.
I wonder, @napcok , if that project may have relevance or any advantage in the future of Labwc Mabox.
![]()