PekWM 1.15 Released

Window managers, icon programs, widgets, etc.
Message
Author
musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#61 Post by musher0 »

Hello, all.

Here is a little script to change the number of desktops in pekwm on the
fly. AFAIK, it is version-neutral. It requires replaceit as a dependency
(can be downloaded from http://www.pldaniels.com/replaceit/).
It goes in ~/.pekwm and should be named "def-pwm-wkspaces.sh".

Code: Select all

#!/bin/sh
# Nom et emplacement de ce script : ~/.pekwm/def-pwm-wkspaces.sh
# Dépendances : replaceit, pekwm
# (c) Christian L'Écuyer (alias / aka musher0), 
# Gatineau (Qc), Canada, 7 juin 2013. 
# Tous droits réservés, sauf usage privé et personnel ("ad usum privatum") 
# dans le contexte de ToutouLinux. / All rights reserved, except private
# and personnal use ("ad usum privatum") in the context of PuppyLinux.
####
case "$@" in
	1)WS="Workspaces =\"1\""
		WPR="WorkspacesPerRow =\"1\""
		WSN="WorkspaceNames =\"- 1 -\"" ;;
	2)WS="Workspaces =\"2\""
		WPR="WorkspacesPerRow =\"2\""
		WSN="WorkspaceNames =\"- 1 -;- 2 -\"" ;;
	3)WS="Workspaces =\"3\""
		WPR="WorkspacesPerRow =\"3\""
		WSN="WorkspaceNames =\"- 1 -;- 2 -;- 3 -\"" ;;
	4)WS="Workspaces =\"4\""
		WPR="WorkspacesPerRow =\"4\""
		WSN="WorkspaceNames =\"- 1 -;- 2 -;- 3 -;- 4 -\"" ;;
	5)WS="Workspaces =\"5\""
		WPR="WorkspacesPerRow =\"5\""
		WSN="WorkspaceNames =\"- 1 -;- 2 -;- 3 -;- 4 -;- 5 -\"" ;;
	6)WS="Workspaces =\"6\""
		WPR="WorkspacesPerRow =\"6\""
		WSN="WorkspaceNames =\"- 1 -;- 2 -;- 3 -;- 4 -;- 5 -;- 6 -\"" ;;
	7)WS="Workspaces =\"7\""
		WPR="WorkspacesPerRow =\"7\""
		WSN="WorkspaceNames =\"- 1 -;- 2 -;- 3 -;- 4 -;- 5 -;- 6 -;- 7 -\"" ;;
	8)WS="Workspaces =\"8\""
		WPR="WorkspacesPerRow =\"8\""
		WSN="WorkspaceNames =\"- 1 -;- 2 -;- 3 -;- 4 -;- 5 -;- 6 -;- 7 -;- 8 -\"" ;;
	9)WS="Workspaces =\"9\""
		WPR="WorkspacesPerRow =\"9\""
		WSN="WorkspaceNames =\"- 1 -;- 2 -;- 3 -;- 4 -;- 5 -;- 6 -;- 7 -;- 8 -;- 9-\"" ;;
	*) exit ;;
esac
R="replaceit --input=/root/.pekwm/config --wholeline"
$R Workspaces "    $WS" -"#"
$R WorkspacesPerRow "    $WPR"
$R WorkspaceNames "    $WSN"

### 30 ###
To make it accessible, place the following at the end of the pekwm sub-menu in the pekwm menu. (See attached picture if you don't know where that is.)

Code: Select all

		Submenu = " Number of desktops" {
# Pour un sous-titre en français, mettez un dièse devant la ligne 
# ci-dessus, et enlevez le dièse devant la ligne ci-dessous. 
#              Submenu = " Nombre de bureaux" {
			Entry = " - 1 - " { Actions = "Exec ~/.pekwm/def-pwm-wkspaces.sh 1;Restart" }
			Entry = " - 2 - " { Actions = "Exec ~/.pekwm/def-pwm-wkspaces.sh 2;Restart" }
			Entry = " - 3 - " { Actions = "Exec ~/.pekwm/def-pwm-wkspaces.sh 3;Restart" }
			Entry = " - 4 - " { Actions = "Exec ~/.pekwm/def-pwm-wkspaces.sh 4;Restart" }
			Entry = " - 5 - " { Actions = "Exec ~/.pekwm/def-pwm-wkspaces.sh 5;Restart" }
			Entry = " - 6 - " { Actions = "Exec ~/.pekwm/def-pwm-wkspaces.sh 6;Restart" }
			Entry = " - 7 - " { Actions = "Exec ~/.pekwm/def-pwm-wkspaces.sh 7;Restart" }
			Entry = " - 8 - " { Actions = "Exec ~/.pekwm/def-pwm-wkspaces.sh 8;Restart" }
			Entry = " - 9 - " { Actions = "Exec ~/.pekwm/def-pwm-wkspaces.sh 9;Restart" }
		}
You click on the number of desktops you require, pekwm re-launches (not the full re-start), and the number of desktops is adjusted (they will show in your taskbar).

Enjoy.

musher0
Attachments
def-pwm-wkspaces.sh.zip
(775 Bytes) Downloaded 595 times
N_bureaux_pekwm.jpg
(24.42 KiB) Downloaded 785 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
Nathan F
Posts: 1764
Joined: Wed 08 Jun 2005, 14:45
Location: Wadsworth, OH (occasionally home)
Contact:

#62 Post by Nathan F »

I updated my hack of openbox-menu at https://bitbucket.org/nfisher1226/pekwm-menu. This is a compiled app in C, and the link is just to the source. Please note Simargl did essentially the same thing a while back but based on an earlier release of openbox-menu and with the capability to display icons removed. Since you can easily turn off icon display in your pekwm config I left it in the program. It requires glib, gtk (for the icon lookup) and menu-cache (from lxde, but can be used separately). Nice and fast.

Usage is exactly as you would use any other Dynamic menu with pekwm.

This is essentially just a sync with upstream but while I was at it I fixed a couple compiler warnings.
Bring on the locusts ...

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#63 Post by musher0 »

Hello, pekwm lovers. :)

There is a way to make ROX panels pekwm friendly simply by inserting
some commands in the "mouse" configuration file. Under the heading
"ScreenEdge", then "Bottom", you can add a line like:

Code: Select all

   ButtonRelease = "Mod1 1" { Actions = "Exec rox -b=bottom-panel &" }
to add a rox panel at the bottom.
The action required is Alt-LeftClick at the bottom of the screen.

And then to remove it:

Code: Select all

   ButtonRelease = "Mod1 2" { Actions = "Exec rox -b= &" }
Here, the action required is Alt-MiddleClick at the bottom of the screen.

Or you can compose one switch script that will open or close the bottom
panel, depending on the contents of the "panels" file.

You can put whatever program you like in the bottom panel, not
forgetting ROX-Applets FreeFS, Load, Mem and Tasklist that will help you
build an informative panel similar the jwm or icewm panels.

This is probably the simplest route: since ROX is already in all Puppies,
the memory overhead will be minimal, as compared to lxpanel or fbpanel
or xfce-panel.

Please see: http://bkhome.org/blog/?viewDetailed=01241 and
http://distro.ibiblio.org/quirky/pet_packages-quirky/

Avoid the rox pager since it is unstable when closing and re-opening a rox
panel. If you intend to use a ROX panel at the bottom permanently,
it won't matter, but if you want to open and close a rox panel at the
bottom, use the very steady stalonetray instead. When you close it,
stalonetray preserves its icons from one time to the next.
http://stalonetray.sourceforge.net/

You can mimic the above approach for left-side and/or right-side panels,
since pekwm's mouse config has headers for left and right as well. And
then you put the other programs that you need in those panels.

That's all for now! TWYL.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

jimwg
Posts: 121
Joined: Mon 19 Aug 2013, 02:44

#64 Post by jimwg »

deleted

Gnuxo
Posts: 365
Joined: Thu 09 Feb 2012, 19:01

#65 Post by Gnuxo »

I didn't realize this but another new version of Pekwm was released.
Version 1.17.

https://www.pekwm.org/projects/pekwm/news

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#66 Post by musher0 »

Gnuxo wrote:I didn't realize this but another new version of Pekwm was released.
Version 1.17.
https://www.pekwm.org/projects/pekwm/news
Thanks, gnuxo.

However, I had trouble compiling that version on my wary 5.5, so
member Médor suggested that I use the git from
https://www.pekwm.org/projects/pekwm/repository
(the first "git" entry, just below the 1st paragraph). That git version
compiled just fine after use of "autogen.sh".

This new pekwm offers a screen capture utility, but there are many of
those already on Puppy, which are much more efficient and have
more options than the one in pekwm 1.17. I must say that the pekwm
utility creates very high quality pictures, but since screen captures are
usually used for examples on message boards, such a high quality of
picture is overkill.

Also, this brings up the question: should a screen capture utility be part of
a window manager? If so, you could just replace the pekwm capture with
one of Puppy's, and voilà!, you'd have upgraded pekwm? :roll:

IMO, pekwm version 1.17 is not worth changing to. One can stick to
version 1.16 until the authors of pekwm introduce more significant
changes.

Best regards.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

Gnuxo
Posts: 365
Joined: Thu 09 Feb 2012, 19:01

#67 Post by Gnuxo »

No, I actually don't care for screen capture, other then to report bugs online.
But I was hoping that there would some performance improvements.
Not to say that pekwm needs them, it's fast enough. But if it got even faster, that wouldn't be a bad thing.

jimwg
Posts: 121
Joined: Mon 19 Aug 2013, 02:44

#68 Post by jimwg »

musher0 wrote:Hello, pekwm lovers. :)

There is a way to make ROX panels pekwm friendly simply by inserting
some commands in the "mouse" configuration file. .... That's all for now! TWYL.

musher0

If there were a script that could totally and automatically configure all this for newbies to have custom desktop backgrounds you will make Puppy all that more outrageously attractive to Mac refugees!

Thanks for your great long work for the linux community!

Jim in NYC

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#69 Post by musher0 »

jimwg wrote:
musher0 wrote:Hello, pekwm lovers. :)

There is a way to make ROX panels pekwm friendly simply by inserting
some commands in the "mouse" configuration file. .... That's all for now! TWYL.

musher0

If there were a script that could totally and automatically configure all this for newbies to have custom desktop backgrounds you will make Puppy all that more outrageously attractive to Mac refugees!

Thanks for your great long work for the linux community!

Jim in NYC
Hi, jimwg.

Thanks for the thanks! :)

Shame on me, I am not advanced enough as a programmer to provide
you and other "refugees" with automated configuration of pekwm. I'm
doing what I can to popularize a wonderful window manager, that's all.

Like a lot of people here, I'm just an "amateur with a passion". I'm
learning everyday, though, so who knows.

An additional difficulty is that pekwm is very configurable, so that would
represent a lot of coding...

Maybe you could leave a message on the pekwm board. The authors
there certainly would have the knowledge to offer us some automatic
configuring. Just a thought.

Best regards.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#70 Post by musher0 »

Hello, all.

As you may know the sharing site I was using, limelinx, has shut down.

While I am retracing the pet packages I made for pekwm, those interested in pekwm
may wish to try one of the ready-made debian or ubuntu packages available at
http://pkgs.org/search/pekwm.

Best regards.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#71 Post by musher0 »

Hello, pekwimmers and wood-peckers! :)

I was unhappy with kittykat's desktop.sh, suggested on the pekwm "Companions"
page (https://www.pekwm.org/projects/3/wikis/Companions) as a utility
to iconify all open windows on a particular desktop.

Problem is: kittykat's script does only part of the job. It hides only non-sticky
windows. I needed something that took charge of any and all windows located on a
particular desktop. So I made my own.

(May 27, 2014. Beginning of edit.)
~~~~~~~~~~~~~~~~~~~~~~~

Code: Select all

#!/bin/sh 
# /root/my-applications/bin/cache-fen3.sh ("Homme fort" / "Strong Man") 

# # Objectif : icônifier ou masquer les fenêtres ouvertes sur un bureau 
 # quand on se sert d'un gest. de fen. qui n'a pas cette fonction. / 
# # Purpose: iconify or shade windows open on a desktop when using a 
 # window manager that does not have that function. 

# # Requires / Requiert : wmctrl (http://tomas.styblo.name/wmctrl/) 

# # (c) Christian L'Écuyer (alias / aka musher0), Gatineau (Qc), Canada, 
 # 25 mai / May 25, 2014. Tous droits réservés / All rights reserved.
 # Edited / Révisé 26 et 27 mai 2014 / May 26 & 27, 2014 par CLÉ.
#### 

a="hidden" 
# Please note that on some wm's, this really means "hidden", not 
# just "iconified"... So, don't panic! (:-)
# a="shaded" 
 # Le paramètre "shaded" ne performe pas toujours aussi bien : il peut 
 # ignorer certaines fenêtres, telle l'Analog-Clock de GTK-Basic. /  
 # The "shaded" setting doesn't always perform as well: it may ignore 
 # some windows, such as GTK-Basic's Analog-Clock. 

bur="`wmctrl -d | awk '$2 == "*" { print $1 }'`"  
 # Dit sur quel bureau nous sommes. / Says on which desktop we are. 
 # ( +/- tiré du script de kittykat. Le reste est de moi.) / 
 # (Line from kittykat's script +/- verbatim. The rest is from me.) 

for i in `wmctrl -l | grep -v '+AT' | awk -v bur=$bur '$2 == bur || $2 == -1 { print $NF }'` 
 # Ci-dessus / Above, < ... || $2 == -1 ... > 
 # ramasse aussi les fenêtres "collantes". / also picks up sticky windows. 
 # Les fenêtres de ROX-Filer avec "+AT" dans sont traités ci-dessous. /
 # The ROX-Filer windows with "+AT" in the title are processed below.
 do 
	wmctrl -r "$i" -b toggle,$a
 done

# Vérifions maintenant les dossiers ouverts de ROX-Filer. / We now check for open ROX-Filer folders.
wmctrl -l | grep '+AT' | awk -v bur=$bur '$2 == bur || $2 == -1 { print $(NF-1)" "$NF }' | tr "\n" ";" > /tmp/rxflr
nchamps="`wmctrl -l | awk '$NF ~ /\+AT/ { print $(NF-1)" "$NF }' | wc -l`"
for i in `seq $nchamps`
do
	wmctrl -r "`awk -F";" -v i=$i '{ print $i }' /tmp/rxflr`" -b toggle,$a
done
rm -f /tmp/rxflr
# Le cas de / Geany's / case ! # Ses fenêtres secondaires / Its secondary windows.
[ "`wmctrl -l | awk '$NF ~ /Find/'`" ] && wmctrl -r "Find" -b toggle,$a
[ "`wmctrl -l | awk '$NF ~ /Replace/'`" ] && wmctrl -r "Replace" -b toggle,$a
As you can see, I added the possibility to use the script to shade windows instead
of hiding them. I left it at a possibility for now, for the reason mentioned in the comment.

Now this will work as advertised only if you have ticked "Short Title Flags" in the
ROX-Filer options.
An attached illustration shows where that setting can be set in
the ROX-Filer Options panel.

(End of edit.)
~~~~~~~~

It can be used with pekwm, with any wm lacking such a function, or with any wm that
does not have one as vigourous! It's well commented, so I'll leave you to it. :)

Enjoy! (Or shed a tear :cry: for all the years you lost trying to figure out how to do
this... Just kidding, speaking for myself! ) :)

BFN.

musher0
Attachments
cache-fen3.sh.zip
Same script, zipped.
(1.35 KiB) Downloaded 355 times
ShortTitleFlags.jpg
(22.55 KiB) Downloaded 321 times
before.jpg
(61.32 KiB) Downloaded 373 times
after.jpg
(61.63 KiB) Downloaded 358 times
Last edited by musher0 on Tue 27 May 2014, 15:37, edited 9 times in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#72 Post by musher0 »

Hello again !

In reference to the above, please note that there is a limitation in wmctrl concerning
multiple windows of the same executable on a desktop.

wmctrl will not iconify two urxvt terminals. If there are one or three or more, it will
iconify only the first one.

(Edited Monday, May 25th, 2014.)
~~~~~~~~~~~~~~~~~~~~~
If anyone knows of a workaround, I'll be grateful.

I thought it was the same with ROX-Filer windows until I discovered that wmctrl likes
to work with specifics when it comes to opened windows of a same program. So
see please amended script in above post: it now can hide or shade 16 likely folders a
ROX-Filer window may show.

(End of edit)
~~~~~~~~
BFN.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#73 Post by musher0 »

Hello.

Tonight, I edited my previous two posts in light of some new experiments I did with
wmctrl. Please re-read.

The edited script covers more cases than the previous one.

Thanks for your understanding.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#74 Post by musher0 »

Another update, using an array and a for...do...done loop while dealing with ROX windows.
~~~~~~~~~~~
Edit: Processing only 25 folders out of the 48,716 on this Puppy Precise-5.7.1... Oh well... :)
~~~~~~~~~~~
This script is now at version 2. BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#75 Post by musher0 »

Hello, everyone.

The cache-fen script now has a new version codenamed "Strong Man"... Because this one
can handle any of the nearly 49,000 folders that ROX-Filer can show on your computer,
not just a meager 25 . Consequently, the fourth post above has been edited.

Enjoy!

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#76 Post by musher0 »

Hello, all.

I found this yesterday: http://akita.scottjarvis.com/pekwm-0.1.16-i486.pet
in the akita repo, and it works great in my PuppyPrecise-5.7.1. Just underneath that
entry, you will also find some pekwm themes and some pekwm documentation.

So, following the advice of my medieval buddy Ockham (see under my sig), I will not
be "needlessly creating" another logical entity for pekwm! :D

Of course: thanks to Scott Jarvis (aka "scottman") for this, and generally for his steady
work evolving Puppy 4.20 into the "akita" derivative.

BFN.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#77 Post by musher0 »

Hello, all.

I discovered that you could have an urxvt console "a la kuake" in pekm. "kuake-
type" consoles drop down from the top edge of the screen when you hover your
mouse at the very top (line 0).

Now it's not a clone, but close enough. I for one find it quite handy to have so to
speak immediate access to a terminal to do a files listing, or generally to use any
CLI utility, and always at the same place on the screen.

-- How-to --
A) The configuration file at /root/.pekwm/mouse. It's there expressly to allow the
customization of such mouse movements or key/mouse-button bindings.

1) I used the mouse scripting capacity that pekwm provides in its "mouse" config file.
I added the following in the mouse config file.

Code: Select all

ScreenEdge {
	Up {
	ButtonRelease = "Mod4 1" { Actions = "Exec /root/my-applications/bin/console.sh &" }
	}
}
2) I had to enter the full path and filename, because the variables in pekwm's
"vars" config file do not seem to work here. I have
$MBINS="~/my-applications/bin"
in my vars config file, but it didn't work. However the variables in vars work fine
in the pekwm menu.

2) You have to re-start pekwm from the initial black console with

Code: Select all

xwin pekwm
for the new mouse definition to be effective. The "Reload" and "Restart" in the
pekwm menu do not appear to be powerful enough to reinitialize pekwm's mouse
configuration.

3) "Mod4" designates the "window" key. The "1" after it means the left button of
the mouse.

So for this terminal to appear, you have to move your cursor to the very top of the
screen and press the window key on your keyboard and the left mouse button
at the same time.

B) An "on/off" script for urxvt.

Code: Select all

#!/bin/ash
# $MBINS/console.sh et $MBINS/console (lien)
# Also required (dependency): wmctrl
# musher0, 4 janv. 2015.
####
A="`wmctrl -lxp | grep "Console1" | cut -d'C' -f2`"
case $A in
	onsole1) 
	kill "`pidof -s urxvt`" &>/dev/null
	;;
    *)
     G="g 80x20+250+0"
	COL="bg #271F0C -fg black -bd #BDBDBD -tr -tint AntiqueWhite3 -sh 120"
	FNT="fn xft:Monaco:pixelsize=15:antialias=true:hinting=true"
	urxvt -cd /root -b 18 -sr -T "Console1" -$COL -$FNT -$G &
	sleep 1.5s
	;;
esac
Why I use wmctrl to define the title of the window in variable A, is because it allows
me to have a second terminal controlled (I mean opened and closed) the usual way,
and optionally with another type of background. You can find wmctrl at:
Image

Note: I find the MONACO fixed font the most appropriate for terminals, but each
user may have a preference. There are a number of "monaco" fonts on the web,
and the more recent ones seem to be proportional fonts -- in other words useless
in a terminal, proportional fonts turn a terminal into an accordeon. :)

Number 4 here http://lowing.org/fonts/ is the one I'm talking about. You
can download it from: http://www.gringod.com/wp-upload/MONACO.TTF
Other distinguishing features: Its name is all in caps, and it weighs 65K.

As I mentioned, the script above is an on/off switch. You use the same key /
mouse-button combination (< window key + left mouse button >) to open and
close this console in pekwm.

The result is illustrated below.

~~~~~~~~~

BFN

musher0
Attachments
urxvt-a-la-kuake.jpg
Open.
(30.8 KiB) Downloaded 650 times
urxvt-a-la-kuake(1).jpg
You can also shade it. Visually, it then balances the presence of your regular tray &amp;
bar at the bottom of the screen.
(8.09 KiB) Downloaded 645 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#78 Post by musher0 »

Hello again, folks.

Here's another nicety, this time for the pekwm menu: RAM free.

The script goes in /root/.pekwm

Code: Select all

#!/bin/sh
# ~/.pekwm/mev-libr-pekwm.sh
# dynamic script for pekwm menu, to show the free RAM as you 
# progress through your pekwm session.
##
# musher0, 3 janv. 2015.
####
# Variables
MEMDISP="/tmp/MEV"
export MBINS="/root/my-applications/bin"
a="";a="`free | grep Mem | awk '{ print $2 }'`"
# ;echo $a
b="";b="`free | grep Mem | awk '{ print $4 }'`"
# ;echo $b
MEVDISP=`echo "scale=2;(($b / $a) * 100)" | bc -l`
# echo "$MEVDISP %"

# Langues # If not exist "fr", show entry in English.
if [ ${LANG:0:2} = "fr" ];then
	echo "Dynamic {"
	echo " Entry = \"   MEV : $MEVDISP %\" { Actions = \"Exec $MBINS/mem-libr.sh & \" } "
	echo " }"
	else
		echo "Dynamic {"
		echo " Entry = \"   RAM: $MEVDISP %\" { Actions = \"Exec $MBINS/mem-libr.sh & \" } "
		echo " }"
fi
The pekwm menu entry is as follows. You would place it normally second from the top,
right after the date & time dynamic menu entry

Code: Select all

	Entry = "" { Actions = "Dynamic $PEK/mev-libr-pekwm.sh"}
For the result, see the illustration below.

Now I've set it up to show the results of the "free" utility in less, but you could ask the
dynamic script to clean up RAM when it gets below a certain percentage. More about
this later.

I also made a variant for aewm's aemenu. More about this elsewhere. :)

BFN.

musher0
Attachments
Free_RAM_on_pekwm_menu.jpg
(21.95 KiB) Downloaded 624 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#79 Post by musher0 »

Hello, people.

Just an important note to mention: open the pekwm doc and go to the very bottom.
18.20. Why is nvidia dual-head misbehaving?

The nvidia proprietary driver provides dual head information both in Xinerama and
RANDR form. The RANDR information given by the driver is in the form of one large
screen, the Xinerama is divided up into multiple heads. To work around this the
HonourRandr option has been introduced in the Screen section of the main
configuration file. Set it to False making pekwm only listen on the Xinerama
information.

Screen {
...
HonourRandr = "False"
...
}
I quote it here because people never read docs all the way down to the end... ;)

Except that if you don't set the above parm in pekwm's config file, there's a good
chance your pekwm will refuse to work. It happened to me the other day when I
replaced my nVidia card with a "née Radeon" card .

Not being able to run pekwm is no fun, whatever the video card.

BFN.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#80 Post by musher0 »

Hello again, Puppyists.

I just discovered that "Taskbar" is an undocumented but recognized parameter in the
pekwm's autoproperties file. This, for example,

Code: Select all

Property = "^xclock,^XClock" {
	ApplyOn = "Start New"
 	Border = "True"; Titlebar = "False"
 	Sticky = "True"
 	Layer = "Normal"
 	Skip = "Taskbar Menus FocusToggle Snap"
}
will prevent xclock from showing in bmpanel2's taskbar, and probably other bars as
well (to be checked).

Another parm that appears to be undocumented is "Shaded = True". The following,
for example, will shade an urxvt terminal bearing the title "Console1".

Code: Select all

Property = "^urxvt,^URxvt" {
	Title = "Console1"
 	ApplyOn = "Start New"
#  	ClientGeometry = "560x137+120-137"
 	Border = "True"; Titlebar = "True"
 	Sticky = "False"
 	Shaded = "True"
 	Layer = "Normal"
}
-- A word also on the lesser known "Title =" parameter. --
The "Title = Console1" parameter above will be checked agains a "-T Console1" parm
in the urxvt command line. If true, the window will shade (wrap up or shrink vertically)
to the windows's title bar.

That's fine-tuning, actually. The advantage of this is that the Title parameter enables
you to launch a second terminal with no particular title, and this last one will display
on your monitor as a regular, unshaded window.

Finally, in both examples, the ClientGeometry parm is not used. In the first case, it's
simply not there, and in the second case, it's commented out. That's because it's
controlled from the command line, not through pekwm. If you had both, I believe the
pekwm one would have precedence (to be checked).

BFN.

musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

Post Reply