JWM 2.0.1 Enhancements and Fixes

[Patriot]

Hmmm .....

@joel

Transparency setting is a local setting (not a global setting) configured within each theme. CoolVG and gradient-brown-t2 themes are provided as an example how it can be done. The rest of the themes are default jwm themes included with the standard puppy and requires you to add the necessary transparency option.

The <Opacity> option is how you control transparency/translucency level (ex: 0.8 = 80% / 0.55 = 55%). <Opacity> option tag can be specified for WindowStyle, TrayStyle and MenuStyle. Find the /root/jwm/themes folder and add the necessary transparency settings to all the themes (files that ends with -jwmrc) that you like.

Rgds

[joel]

Thanks. I figured it was something simple like the other themes need to be configured. I like the work you put in to JWM. Thanks

PS: Does transparency slow things down for you? It seems when I have it on there is a 1-2 second delay to open windows. Any way to speed it up. I have a decent card so it shouldnt do it.

Thanks Again!

[`f00]

Well, unless you set the fade option .. actually it might well be the x/kcompmgr doing its thing (and that does seem to take a bit - mainmenu and trays not so much, but especially if the windows have translucency enabled individually via the taskbutton or header-menu). A more 'elegant' window-translucency (for windows as a focus group in sequence) seems to work nicely with the jwm-456-i386.pet(?) - Xorg may have lots of little hwr ideosyncracies that can affect performance .. depending
_________________
*

[Patriot]

Hmmm .....

..... PS: Does transparency slow things down for you? .....

I periodically do JWM translucency tests on older hardware such as i810 and S3virge vga cards. They run reasonably fast without the fade option. On older hardware, I normally turn on transparency for menu + taskbar plus only on certain (static/non-editing) apps like audacious where very little editing is needed. I do not recommend full time transparency for editors or file managers.

If you're running on a nice card (like nv gf2/gf4/gf5 above or ati 85/92 above) then the vendor driver should give better performance. If you really love the fade option then reduce the fade cycle by increasing the values.

`foo correctly states that Xorg performance can be affected by hardware+software driver mix. For example, the intel driver is well supported (by the manufacturer) and runs very well. The nv (nvidia) driver is not properly supported (by the manufacturer) and doesn't really maximize gpu/vga capabilities. Sometimes, tinkering with xorg/driver settings can give a boost here and there (but I'm no expert in these area and unable to advise how).

Rgds

[BarryK]

There is something that is on hold, as I left Upup to work on Ppup 4 series.

Using the latest official nightly snapshot of jwm, running in Upup which has Xorg 7.4, we have a problem with icons not displaying in the jwm menu. But, I think that problem was if 24-bit color was chosen, and the icons did display with 16-bit color.

But the question remains unanswered -- is that problem due to Xorg 7.4, or the latest jwm?

Note, in Upup 416 I have Xorg 7.3 and Patriot's slightly modified source ...um, what was that now... yes, version 2.0.1-pb-1.

[Patriot]

Hmmm .....

@BarryK

Interesting ...

Could you point me to the Upup iso in question? I wasn't following Upup progress and am unaware of the problem. I'd also like to know the vga driver being used (was it i810/intel?) ... It would be interesting to find out why the icons doesn't render at all ....

Rgds

[ttuuxxx]

Hi patriot I noticed something on the jwm in 416, say you have gimp installed and gimp is opened and minimized, you grab/drag a picture and want to drop on gimp that is minimized on the taskbar, gimp doesn't maximize? you have to let go of the image and max gimp then drop it on the main window, same with say a mp3, movie, doc etc, wouldn't it be nice if you could drop files on there min task window.?
ttuuxxx

[Patriot]

Hmmm .....

@ttuuxxx

XDrag-n-drop (XDnD) is not supported by JWM. Not one single line of code for XDnD is in JWM (if I'm not mistaken). It's possible to add this functionality ..... needs time, a good plan, some patience and lotsa coffee to implement it properly ... I'll put it on KIV list and see how it goes (need to load up another tonne on my motivation)... no promises ...

Rgds

[ttuuxxx]

Hey Patriot don't worry about it, I don't want to be a pain, still would rather freememory,clock,blinky being a part of JWM code,lol I know you said no, but even on the latest 416 just released last week, if you type "fixmenus" then restart JWM as you do, Freememory flies off the taskbar and lands in the upper left hand corner of the screen, I know put a delay etc, thats just another added script really what would be nice is to figure out why the clock never ever has left the taskbar and the rest all have in the past, what makes the clocks code so special, That it doesn't need a delay and just works 100% of the time.
ttuuxxx

[Patriot]

Hmmm .....

..... Freememory flies off the taskbar and lands in the upper left hand corner of the screen, I know put a delay etc, thats just another added script really what would be nice is to figure out why the clock never ever has left the taskbar and the rest all have in the past, what makes the clocks code so special, That it doesn't need a delay and just works 100% of the time.
ttuuxxx

Ok, external applets do occasionally gets "orphaned" from the systray ... The clock on the other hand is an internal "applet" with no extra dependency, just a simple clock display with an option to call an external program. Freemem/blinky is not a so-simple external applet. They uses GTK+ and tries to hook onto the systray upon starting. They have layers ....

At first, I see a memory hungry absvolume. After looking at the layers, it dawned upon me that the actual memory usage for absvolume is roughly 680KB (binary+stack+data). The rest are mostly GTK+ and related libs ... layers ... Ogre has layers ... errr ... uh, modern programming has layers ... just like onions, it has layers ...

The most stable applet in the sense that it reliably gets to the systray is absvolume. I'm hoping to make a new template based on a cleaned up absvolume and then re-base all these applets using the new template. This will make them easier to maintain, whack, whatever ...

Now, let me find another tonne of motivation ...

Rgds

[01micko]

About that issue where the menu icons don't show...

I have no such problem in 4.2.1 k2.6.15.16 running JWM 2.0.1-pe (Alpha preview) and in Slaxer-pup with JWM-456. ( I compiled that with src2pkg and then dir2pet especially for Slaxer-pup). Slaxer-pup just uses the standard 412 xorg driver.

I think I was one of the first to report the issue if you choose the 24 option in upup, then someone reported that 16 was ok, so I switched to that. Are there any logs you want for comparison?

I can test in any pup you want ... I have more running than the full card at the Dapto Dogs...

[pstef]

Hi. I am owner of Samsung SyncMaster 740N monitor which is able to rotate its screen so I can use 1024x1280 resolution with xrandr -o left. However, JWM still thinks that it's 1280x1024 so the taskbar is too wide and placed too high. I have managed to modify JWM's source to support 'rotated' resolution but I'd like to have it as an option (manual option would be sufficient for me). I tried, but I failed so I'm asking you for some help.

Oh, and what I did was just swapping rootWidth with rootHeight in OpenConnection().

[Patriot]

Hmmm .....

..... xrandr -o left. .....

AFAIK, JWM has no xrandr support and it detects screen resolution on startup. So, forget about swapping rootWidth and rootHeight.

Your best bet is either:
1. Put xrandr -o left in .xinitrc before JWM.
-or-
2. Make a script in ~/Startup to do xrandr -o left.

Of course, take a pinch of salt with the above as I have no rotating CRT monitor to play with ...

Rgds

[pstef]

forget about swapping rootWidth and rootHeight

Why? Since

I have managed to modify JWM's source to support 'rotated' resolution

I just need it to become an option, not hardcoded feature.

[Sit Heel Speak]

Hi. I am owner of Samsung SyncMaster 740N monitor which is able to rotate its screen so I can use 1024x1280 resolution... with xrandr -o left. However, JWM still thinks that it's 1280x1024...

I don't have a rotateable monitor either, but am curious: when you run xrandr -o left, is /etc/X11/xorg.conf modified to give

Code: Select all

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	(...some lines...)
        Option      "PreferredMode" "1024x1280"
	EndSection

and

Code: Select all

Section "Screen"
   Identifier "Screen0"
   (some lines...)
   Modes       "1024x1280"
EndSubsection
EndSection

???

[disciple]

Why? Since
Quote:
I have managed to modify JWM's source to support 'rotated' resolution

I just need it to become an option, not hardcoded feature.

Unless we all misunderstood what your modification is, it doesn't need to be a jwm option. Like Patriot said, jwm already works with a rotated screen if you start X rotated. It doesn't work if you start X and then change the rotation. Do you always want to use the screen in portrait orientation? If so, try the advice above, or there are options you can put in xorg.conf - I think this in the device section:

Code: Select all

   Option     "Rotate" "CCW"  

Or CW to rotate the other way.
And maybe you also need

Code: Select all

Option "RandRRotation" "on"

If you want to be able to switch the screen rotation sometimes, I suggest using this as a window manager (thanks MU):

Code: Select all

#!/bin/ash

$1 &

while [ 1 ]
do

sleep 10000

done

Call it muppywm or something and start X with

Code: Select all

xwin muppywm jwm

. I do this, and then use a script I call prandr-left to rotate the screen right

Code: Select all

#!/bin/bash
   killall jwm
   xrandr -o left
   jwm &
   exit 0

and prandr-normal to rotate it back again

Code: Select all

#!/bin/bash
   killall jwm
   xrandr -o normal
   jwm &
   exit 0

Ah - but then I think you can't use the options in the jwm menu that exit X etc. This is the current version I'm using of my shutdown dialogue

Code: Select all

#! /bin/bash

export MAIN_DIALOG="
<window title=\"Turn the computer off?\"icon-name=\"gtk-quit\">
<hbox>
   <vbox>
   <text>
   <label>This is your last chance to stop and save any open files!</label>
   </text>
      <hbox>
      <button cancel></button>
      <button>
      <input file>/usr/share/midi-icons/shutdown24.png</input>
      <label>Turn the computer off</label>
      <action>wmpoweroff</action>
      </button>
      </hbox>
   </vbox>
   <vbox>
   <text>
   <label>Or you can:</label>
   </text>
      <button>
      <label>Rotate the screen left</label>
      <action>prandr-left</action>
      <action>Exit:1</action>
      </button>
      <button>
      <label>Rotate the screen normal</label>
      <action>prandr-normal</action>
      <action>Exit:1</action>
      </button>
      <button>
      <label>Reboot</label>
      <action>wmreboot</action>
      </button>
      <button>
      <label>Suspend</label>
      <action>apm -S</action>
      </button>
      <button>
      <label>Restart the ROX filer</label>
      <action>restartrox</action>
      <action>Exit:1</action>
      </button>
      <button>
      <label>Restart the JWM window manager</label>
      <action>jwm -restart</action>
      <action>Exit:1</action>
      </button>
      <button>
      <label>Exit X to a command prompt</label>
      <action>exitjwm</action>
      </button>
   </vbox>
</hbox>
</window>"

export HELP_DIALOG="
<window title=\"Info\"icon-name=\"gtk-info\">
<vbox>
<text>
<label>JWM is Puppy's default window manager. It controls the Start menu and taskbar, and window decorations (the border and title bar).  You can restart JWM safely without saving your work.</label>
</text>
<text>
<label>\"\"</label>
</text>
<text>
<label>ROX is Puppy's default file browser. It also controls the icons on the pinboard (desktop).  You will want to restart rox if the little windows for renaming files are greyed out and not working.</label>
</text>
<text>
<label>\"\"</label>
</text>
<text>
<label>X is the graphical windowing environment used in Unix/Linux.  You must save any open files before restarting X.</label>
</text>
<button ok></button>
</vbox>
</window>
"

gtkdialog3 -c --program MAIN_DIALOG 

This is my exitjwm script - probably originating with MU

Code: Select all

Option "RandRRotation" "on"

I don't think I had to edit wmpoweroff or wmreboot... but I'm not certain.

[disciple]

Forgot to mention that I edited /etc/xdg/templates/_root_.jwmrc so the menu ended like this, and then ran `fixmenus`.

Code: Select all

  <Program label="Help" icon="help24.png">exec defaulthtmlviewer file:///usr/share/doc/index.html</Program>

  <Program label="Shutdown" icon="shutdown24.png">shutdowndialogue</Program>

 </RootMenu>

I believe Puppy 4.2.x has something similar to my shutdown dialogue, so I image the menu is already something like that?

[disciple]

Obviously it would be simpler if jwm recognised when you run xrandr - I've no idea how much code that would involve

[pstef]

Thank you for your effort, disciple. It may be solution for some people, but unfortunately not for me, since it requires restarting X, which in my case means reopening over 50 windows.

Sit Heel Speak, I don't know but I will answer your question as soon as I find out.

[disciple]

No - Patriot's solution requires restarting X.
My solution is to start X with a little loop instead of a window manager, so that you can close and restart the window manager without restarting X.
Unless you're complaining about a one-off restart of X when you set it up initially?