JWM 2.0.1 Enhancements and Fixes

[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?

[pstef]

Will I be able to keep my windows after rotating screen with your script?

Sit Heel Speak, answer to your question is: /etc/X11/xorg.conf is not modified when I run xrandr -o left.

[disciple]

Will I be able to keep my windows after rotating screen with your script?

Yes.

[disciple]

Speaking of modifying jwm, some of the responses on this thread http://www.murga-linux.com/puppy/viewto ... 461#328461 confirm my experience that users get confused/annoyed by jwm shading a window when they scroll on the window border. It would be great if we could make it only shade when they scroll on the title-bar, and it might be good to have an option to disable shading too.

[pstef]

I saved your files muppywm, prandr-left and prandr-normal to /bin and did chmod +x on all of them. Closed X and typed xwin muppywm jwm. JWM's tray or whatever it is called, didn't show up and cursor remained to look like 'please wait,' but I was able to run rxvt from ROX's pinboard. After typing prandleft (this is how I named the file in my system), JWM started and I got normal arrow cursor. No single window lost while switching it back to normal. However, this is what I saw in the console:

Code: Select all

# prandleft 
killall: jwm: no process killed
DEBUG: main.c[108]: debug mode started
# DEBUG: shape extension enabled
DEBUG: render extension enabled
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
asapm: open_apm_device_file: The file does not exist.
asapm: Neither ACPI nor APM are available!
killall: blinky: no process killed
killall: freememapplet-tray: no process killed

# prandnorm 
DEBUG: main.c[108]: debug mode started
# DEBUG: main.c[203]: debug mode stopped
DEBUG: MEMORY: no memory leaks
DEBUG: shape extension enabled
DEBUG: render extension enabled
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
asapm: open_apm_device_file: The file does not exist.
asapm: Neither ACPI nor APM are available!
killall: blinky: no process killed
killall: freememapplet-tray: no process killed
# prandleft 
DEBUG: main.c[108]: debug mode started
# DEBUG: main.c[203]: debug mode stopped
DEBUG: MEMORY: no memory leaks
DEBUG: shape extension enabled
DEBUG: render extension enabled
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
asapm: open_apm_device_file: The file does not exist.
asapm: Neither ACPI nor APM are available!
killall: blinky: no process killed
killall: freememapplet-tray: no process killed

# prandnorm 
DEBUG: main.c[108]: debug mode started
# DEBUG: main.c[203]: debug mode stopped
DEBUG: MEMORY: no memory leaks
DEBUG: shape extension enabled
DEBUG: render extension enabled
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
asapm: open_apm_device_file: The file does not exist.
asapm: Neither ACPI nor APM are available!
killall: blinky: no process killed
killall: freememapplet-tray: no process killed

# prandleft 
DEBUG: main.c[108]: debug mode started
# DEBUG: main.c[203]: debug mode stopped
DEBUG: MEMORY: memory leaks follow
DEBUG:         30 bytes in misc.c at line 190
DEBUG:         24 bytes in icon.c at line 643
DEBUG:         9216 bytes in image.c at line 399
DEBUG:         12 bytes in image.c at line 398
DEBUG:         42 bytes in misc.c at line 190
DEBUG:         24 bytes in icon.c at line 643
DEBUG:         2304 bytes in image.c at line 229
DEBUG:         12 bytes in image.c at line 203
DEBUG:         40 bytes in misc.c at line 190
DEBUG:         24 bytes in icon.c at line 643
DEBUG:         960 bytes in image.c at line 399
DEBUG:         12 bytes in image.c at line 398
DEBUG: MEMORY: 12 memory leaks
DEBUG: shape extension enabled
DEBUG: render extension enabled
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
JWM: warning: could not load tray icon: "nothing.png"
asapm: open_apm_device_file: The file does not exist.
asapm: Neither ACPI nor APM are available!
/root/my-applications/freememapplet_tray_puppy215ce/freemem: line 3: 14219 Terminated              /ro                                       ot/my-applications/blinky-0.8-icewm/src/blinky -bg "#939191"
killall: freememapplet-tray: no process killed

# 

[disciple]

Hmmm.

JWM's tray or whatever it is called, didn't show up and cursor remained to look like 'please wait,'

Sorry - looks like I forgot what I actually did.
For the record, muppywm was borrowed from here http://murga-linux.com/puppy/viewtopic. ... 550#155550

So I missed this:

Edit /usr/X11R7/bin/xwin

around line 17, replace
echo -n "$1" > /etc/windowmanager
with
echo -n "muppywm $1" > /etc/windowmanager

And it looks like I still start X with `xwin jwm`, not `xwin muppywm jwm`

[disciple]

Code: Select all

DEBUG: main.c[108]: debug mode started
# DEBUG: shape extension enabled
DEBUG: render extension enabled
JWM: warning: could not load tray icon: "nothing.png" 

These are related to your X and jwm configuration, not to what we're doing. I think the JWM warning means you have a tray icon defined in your configuration, but the icon defined for it doesn't exist.

Code: Select all

asapm: open_apm_device_file: The file does not exist.
asapm: Neither ACPI nor APM are available! 

I believe this is a tray battery monitor failing to start - obviously you don't have a laptop, so it doesn't work. BTW are you running Puppy 4.2? I guess these things must be default there...

Code: Select all

killall: blinky: no process killed
killall: freememapplet-tray: no process killed 

Maybe they've put entries in the jwm configuration to kill blinky and freememapplet when when jwm is killed or something like that. Maybe you have freememapplet disabled? I don't know why they'd want to kill blinky - it works fine for me when I exit and restart jwm.
It looks like maybe blinky wasn't up yet until the last time you ran the script.

[disciple]

For anyone else reading this, if you try my screen rotation scripts and the freememapplet ends up detached from the taskbar in your puppy version, add

Code: Select all

killall freememapplet

before this line in the prandr-left and prandr-normal scripts

Code: Select all

killall jwm

.
Also, depending on the speed of your machine or something, you may find you need to add something like

Code: Select all

sleep 1

before

Code: Select all

jwm &

otherwise it may try to start jwm before it's finished killing jwm, in which case you get a message that the display is already managed, and no window manager. (and if there is a window in front of the rxvt icon on your desktop, and you don't have rxvt open, you need to switch to the other terminal (Ctrl-Alt-F2), login (puppy; woofwoof), start jwm, then switch back (Ctrl-Alt-F3) )

[disciple]

Removed (for non-technical reasons).

[Patriot]

Hmmm .....

One weird weekend I'm having ...

*swish* ... plenus screen mico ...

Finally JWM will be able to have youtube flash full screen working right ...

It all started with a different problem I'm having ... Of all the apps I have to work with this weekend, I was pretty annoyed with vncviewer (TightVNC-1.3.10) full screen toggling ... The pesky viewer won't let me get out of full screen properly (hmm, the love-hate thing) ... It annoyed me so much so that I loaded half a tonne of motivation to give it a good whack ... and I now have a patched vncviewer that toggles full screen just the way it was meant to be ....

Then it got me thinking that youtube flash could be something similar ... errrkkk ... nope, it was a totally different thing ... tracing here, tracing there, tracing everywhere and then Hermione reminded me again ... it's Levi-O-sa , not leviosa ... Eureka! ... struck one out of my list ...

Well, me apologize for me rant ... and for not having posted any binaries yet ... please consider this to be alpha testing stage. I have some major code cleanup to do with JWM before posting the binaries. It'll be sometime next week before I'll get some beta test versions out ...


Rgds

[ttuuxxx]

Hmmm .....

One weird weekend I'm having ...

*swish* ... plenus screen mico ...

Finally JWM will be able to have youtube flash full screen working right ...

It all started with a different problem I'm having ... Of all the apps I have to work with this weekend, I was pretty annoyed with vncviewer (TightVNC-1.3.10) full screen toggling ... The pesky viewer won't let me get out of full screen properly (hmm, the love-hate thing) ... It annoyed me so much so that I loaded half a tonne of motivation to give it a good whack ... and I now have a patched vncviewer that toggles full screen just the way it was meant to be ....

Then it got me thinking that youtube flash could be something similar ... errrkkk ... nope, it was a totally different thing ... tracing here, tracing there, tracing everywhere and then Hermione reminded me again ... it's Levi-O-sa , not leviosa ... Eureka! ... struck one out of my list ...

Well, me apologize for me rant ... and for not having posted any binaries yet ... please consider this to be alpha testing stage. I have some major code cleanup to do with JWM before posting the binaries. It'll be sometime next week before I'll get some beta test versions out ...


Rgds

youtube has worked fullscreen since the rounded corners version downloaded from jwm site in puppies 4.2 no blling, it has also always worked in 2.14X series since it uses the same jwm. Then only difference between fullscreen and normal is the conversion of video size, it plays much slower on fullscreen, usually its best to wait until the whole video is done downloading by watching the progress bar at the bottom, then once its finished replay it and it plays more smoothly fullscreen. but if your watching the progressbar you can notice that the buffer is way ahead of the playing video. so that's a clear indication that its the conversion from normal to fullscreen that's delaying the smooth video. But when you compare it to a online pdf viewer, which is also flash based, you'll notice that scrolling fullscreen is much slower fullscreen, So I would say the actual slowdown is flash and not jwm
ttuuxxx