Fvwm-pdaxrom 0.3.x

[Zumi]

After more than 7 months of developing, fvwm-pdaXrom team proudly presents *drumroll*...
...the new pdaXrom tuned Fvwm config files!

Download the 0.3.1 release:

See the post about the new release here!

Old releases:
Download the 0.3.0 release:

fvwm_pdaxrom_0.3.0_armv5tel.ipk

It depends on fvwm package, that you can find in the RC10 feed.
You can install it to CF or SD card too, it seems to be working, but it's not extensively tested.

Let this be the bugreport thread, so feel free to report bugs here, suggest changes and express delight.
Zumi

[Zumi]

Here's the release notes/documentation/help for the 0.3.0 release:

Welcome to fvwm-pdaXrom version 0.3.0!

1. Goal

The goal for this package is to make an alternative WM (Window manager) for the pdaXrom, that uses Openbox + Matchbox by default.

We want to reach the functionality level that the default WM gives and extend it (with real taskbar, for example). Our other goal is to stay below the default WM's memory consumption. At the moment it looks like this:

    * Fvwm: 9356 KB
    * Openbox + Matchbox* : 12560 KB
      (* Matchbox-desktop is not counted, the Fvwm setup doesn't use desktop icons either.)

2. How to change things to fit your needs

One of the best aspect of using Fvwm is that you can change every tiny bit of the User Interface.

   1. You want one more buttonbar on the top of the screen with your favourite applications? No problem, FvwmButton module is yours.
   2. Want to use a pager to handle more Virtual screens efficiently? FvwmPager module is waiting for you.
   3. You always dreamed about you bring up your secret World Domination plans menu by clicking on a window's titlebar with Control-Alt-Shift-Middle mouse button? Your dreams can come true. (No World domination plans included.)

Oookay, I know you got interested. Keep reading.
Open .fvwm/.fvwm2rc file (.fvwm directory is located in your home directory, usually /home/root under pdaXrom) with your favourite text editor. We tried to keep this file well documented, it holds most of the configuration options. If you don't find what you need, for example you want to change the background image, try reading the .fvwm/clamshell/fvwm-landscape.sh file too.

If you don't find what you need, try reading the Fvwm manual:
http://www.fvwm.org/documentation/manpages/unstable/

This manual is getting more useful when you start to know Fvwm better, so remember to use it when you got familiar with the .fvwm2rc config file in this distribution.

If you just can't find the part you need, try searching Google for the solution.
Okay, so you Read Those F...ine Manuals, searched the net, made a seance with the spirit of your grand grandfather and you just can get it work, ask it on some Fvwm related forum or mailing list or the OESF forums:
https://www.oesf.org/forums/index.php?showforum=73

3. Things that work

    * landscape-portrait change is working almost perfectly (the pdaXrom menu does pops up in the right place when rotated to portrait)
    * pdaXrom menu which is automatically generated from the /usr/share/applications/*.desktop files.
    * new set of mouse cursors
    * quite good integration of the onscreen keyboard when using portrait mode (maximization is aware of the running xvkbd program, so they don't overlap eachother), you can switch on-off the virtual keyboard by click on it's icon on the taskbar (only appears in portrait mode)
    * working taskbar applet called ztaskbar (there's a problem with the font handling that hasn't been solved, that's why it looks ugly now)
    * titlebar and taskbar that mimic the Openbox + Matchbox style, to ease the switch from the default WM :)
    * task manager that displays the running icons on the taskbar for easy selecting the needed one

4. Default keybindings

    * Menu button - Popup the pdaXrom menu under the cursor
    * Alt-A - Prev. desktop
    * Alt-Z - Next destop
    * Alt-4 - Close window (it want to be something like Alt-F4)
    * Alt-Control-R - Restart Fvwm (after intalling an application, to update the pdaXrom menu without quitting)
    * Alt-Control-M - Maximize the current window

5. Last line

This stuff comes with ABSOLUTELY NO WARRANTY. Most of the things I used were released under the General Public License, so I think I will release this bunch of scripts and config files under GPL too.


Have fun using Fvwm!

The fvwm-pdaxrom team (actually it's only me, Zumi :)

[gab74]

I've installed on my SL6000L

When i type startx

fvwm remains with no background and no menu....
When i try to logout Zaurus Hungs....

Any helps ?

[Zumi]

I've installed on my SL6000L

When i type startx

fvwm remains with no background and no menu....
When i try to logout Zaurus Hungs....

Any helps ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88130\"][{POST_SNAPBACK}][/a][/div]

I tried to start X in portrait mode, it worked for me, but I guess it there's some difference between SL-Cxx0 and SL6000L...
If you contact me with an instant messenger, I can help you find out the source of the problem and I hope we can get a SL6000L compatible version at the end.

Zumi

[Christoph]

Hi zumi,

just installed fvwm-pdaxrom and, as you said, it is a feed for bug fixing    
I have to admid that I am used to my own configuration, so take the points below more like suggestions/wishes ;-)
1. when the keyboard shows up, the windows that you maximize AFTER that get
    maximized the right way. Those that are already maximized aren`t altered. You
    may remaximize them after showup/hiding of the keyboard
2. same with rotation.
  you may achieve that by altering the ZaurusMaximize
  AddToFunc ZaurusMaximize I Maximize $0 xxxp yyyp
  and do a "ZaurusMaximize true" at the apropriate time
3. why not bind the "Home" key to switch to the next window? :-),
  fn + home iconifies all windows and shows the desktop
4. fn + 1 iconifies and fn + 2 maximizes
5. cool: fn + 3,4 works!
6. The root menu in portrait mode shows up at y=480.
   I do not have a suggestion how to solve that. It seems that fvwm always moves
   the menus in sight. As fvwm in portrait mode still things the screen has 640x480,
   the menu shows up too high.

Christoph

[jerrybme]

Zumi great work!

I'm using your default config and a few things aren't working.
first it doesn't seem to sense the hinge change so rotating the screen doesn't switch it to protrait. I have to run the fvwm-portrait.sh to get it to do so.

When I kill the x server there are some fvwm error messages:
No such key: F1
No such key: XF86RotateWindows
No such key: XF86Start

Also in the task bar I have only the Menu button and the Aterm icon, no virtual Keyboard icon.

I was curious as to why you created the ztaskbar as an executable instead of a fvwm module? Not sure how to modify the taskbar.

Cheers,
Jerry

[Zumi]

Hi zumi,

just installed fvwm-pdaxrom and, as you said, it is a feed for bug fixing   
I have to admid that I am used to my own configuration, so take the points below more like suggestions/wishes ;-)
1. when the keyboard shows up, the windows that you maximize AFTER that get
    maximized the right way. Those that are already maximized aren`t altered. You
    may remaximize them after showup/hiding of the keyboard
2. same with rotation.
  you may achieve that by altering the ZaurusMaximize
  AddToFunc ZaurusMaximize I Maximize $0 xxxp yyyp
  and do a "ZaurusMaximize true" at the apropriate time

This problem came in my mind, too. I think what you wrote doesn't solve the problem (but good idea, I will add that $0 in the function, it can come handy). The problem is, that I have no idea how to run the ZaurusMaximize command on all the maximized apps at the appropriate time.
If I put simply "ZaurusMaximize true" in the rotater scripts, it lets me pick a window that will be remaximized.

3. why not bind the "Home" key to switch to the next window? :-),

Very good idea! Thanks.
I used Home as "home" and Mail as "end" but today I realized that home-end can be used with Fn-leftkey, Fn-rightkey.

  fn + home iconifies all windows and shows the desktop

Because there are no icons on the desktop, this has no use at the moment, but with ROX it makes sense.

4. fn + 1 iconifies and fn + 2 maximizes

Hehe, nice interpretation of the magnifier above the buttons. Logical, easy to remember, I like it.

5. cool: fn + 3,4 works!
6. The root menu in portrait mode shows up at y=480.
   I do not have a suggestion how to solve that. It seems that fvwm always moves
   the menus in sight. As fvwm in portrait mode still things the screen has 640x480,
   the menu shows up too high.

Christoph
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88199\"][{POST_SNAPBACK}][/a][/div]

Yes, it seems that fvwm is not aware of the rotation until it gets restarted (what takes much too long, so I try to avoid it). I think I will look into the code of Fvwm and see what I can do about it. Xrandr surely raises some X event that Fvwm can catch and refresh its ideas about the screen size.  Maybe. This looks like a serious hacking to me.

You are a true Fvwm zealot. I can recognize one from a mile.
On the way of the glorious quest for the perfect Fvwm setup.

I like your ideas, keep it coming!
Zumi

[Zumi]

Zumi great work!

I'm using your default config and a few things aren't working.
first it doesn't seem to sense the hinge change so rotating the screen doesn't switch it to protrait. I have to run the fvwm-portrait.sh to get it to do so.

When I kill the x server there are some fvwm error messages:
No such key: F1
No such key: XF86RotateWindows
No such key: XF86Start

Check whether you are using the lastest corgi.xmodmap file. In the RC10 version, there are these lines:

Code: [Select]

! This is the screen swivel sensor

keycode 110 = XF86RotateWindows

Code: [Select]

! Menu
keycode 37 = XF86StartThe first one is needed to get the rotation work, because I binded to this the fvwm-hinge command, that decides in what state the screen is and executes the needed script.

Also in the task bar I have only the Menu button and the Aterm icon, no virtual Keyboard icon.

I don't see a reason to waste the space on a button in landscape mode that you never use. It appears in portrait mode, when you need it.

I was curious as to why you created the ztaskbar as an executable instead of a fvwm module? Not sure how to modify the taskbar.

Cheers,
Jerry
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88234\"][{POST_SNAPBACK}][/a][/div]

Imagine you are executing cat and echo commands, every second. FvwmScript opened a shell, executed the command, got the results, etc... It was terrible resource eating. First I haven't realized, because these processes rarely appear in the output of top or ps, however I noticed a lot of slowing (while playing movies, application load times and others symptoms) while using this script-taskbar. I realized that FvwmScript is not a solution for Zaurus.
So I started to write ztaskbar in the most resource friendly graphical user interface I knew. That's FLTK.

Now it virtually doesn't use any resouce. All file reads/writes are within the program, no parent process called. So it's slick and fast, and I plan to redesign the layout (no need to show the CPU speed always), add functions like volume control and solve that bug that doesn't let me use nice fonts, only "fixed".

Zumi

Ps.: fvwm-hinge is just a slight modification of the chkhinge program, included in the base distribution; I submitted ztaskbar with sources in an other thread, but if somebody want to help me/modify the program, contact me and I send the most recent sources (General Pubic License rocks )

[jerrybme]

Zumi:
Hmm, my corgi.xmodmap has those lines so for some reason the keymap is not getting loaded properly. Fn key and mouse mappings also aren't working either. I'll have to poke around some more. Any ideas on the best way to debug the init script .xinitrc.fvwm?
Thanks,
Jerry

[Christoph]

Hi Zumi,

This problem came in my mind, too. I think what you wrote doesn't solve the problem (but good idea, I will add that $0 in the function, it can come handy). The problem is, that I have no idea how to run the ZaurusMaximize command on all the maximized apps at the appropriate time.
If I put simply "ZaurusMaximize true" in the rotater scripts, it lets me pick a window that will be remaximized.

If you just call plain "ZaurusMaximize" fvwm doesn't know which window to maximize, but

Code: [Select]

All (Maximized) ZaurusMaximize trueshould do it (That was the reason I suggested the $0 within the function).

But here is another little suggestion:
On fvwm startup, you call your python script to create the menu. So if someone wants to add something to the menu he has to change your script. If you created
an fvwm function like that

Code: [Select]

DestroyFunc CreateMenuFvwmRoot
AddToFunc CreateMenuFvwmRoot
+ I DestroyMenu MenuFvwmRoot
+ I Piperead $[HOME]/.fvwm/menu-generator.py
+ I AddToMenu MenuFvwmRoot "Nop"
+ I AddToMenu MenuFvwmRoot "%24x24/cancel.png%Exit" Module FvwmForm FvwmForm-QuitVerifywithout the call of DestroyMenu within the script, you can add menu items by changing .fvwmrc

You can add the function to FvwmStartFunc by
+ I Test (Init) CreateMenuFvwmRoot

You are a true Fvwm zealot. I can recognize one from a mile.

I'm far away from that, I'm afraid.  

Christoph

[Zumi]

Zumi:
Hmm, my corgi.xmodmap has those lines so for some reason the keymap is not getting loaded properly. Fn key and mouse mappings also aren't working either. I'll have to poke around some more. Any ideas on the best way to debug the init script .xinitrc.fvwm?
Thanks,
Jerry
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88265\"][{POST_SNAPBACK}][/a][/div]

You can try to manually start this command: "xmodmap /etc/X11/kb/corgi.xmodmap" when Fvwm is running and see with xev whether you got XF86RotateWindows when you rotate the screen.
But there's the part of the .xinitrc that do this at startup:

Code: [Select]

MODEL=`cat /proc/deviceinfo/product`
echo 'MODEL:'$MODEL
case "$MODEL" in
    SL-C860|SL-C760)
    test -f /etc/X11/kb/corgi.xmodmap && xmodmap /etc/X11/kb/corgi.xmodmap
;;
    SL-6000)
    test -f /etc/X11/kb/tosa.xmodmap && xmodmap /etc/X11/kb/tosa.xmodmap
;;
    *)
    cat /proc/cpuinfo | grep 'Sharp-Collie' 2>/dev/null >/dev/null && test -f /etc/X11/kb/collie.xmodmap && xmodmap /etc/X11/kb/collie.xmodmap
;;
esacUsually the best way to debug a bash script is to start it this way: $ bash -x myscript.sh
or change the first line from "#!/bin/bash" to "#!/bin/bash -x"
This gives good output of everything the script does while it's running.

Zumi

[Zumi]

Hi Zumi,

If you just call plain "ZaurusMaximize" fvwm doesn't know which window to maximize, but

Code: [Select]

All (Maximized) ZaurusMaximize trueshould do it (That was the reason I suggested the $0 within the function).

I'm always suprised that Fvwm really can do everything I want.  Thanks, wonderful solution for the problem! =)

But here is another little suggestion:
On fvwm startup, you call your python script to create the menu. So if someone wants to add something to the menu he has to change your script. If you created
an fvwm function like that

Code: [Select]

DestroyFunc CreateMenuFvwmRoot
AddToFunc CreateMenuFvwmRoot
+ I DestroyMenu MenuFvwmRoot
+ I Piperead $[HOME]/.fvwm/menu-generator.py
+ I AddToMenu MenuFvwmRoot "Nop"
+ I AddToMenu MenuFvwmRoot "%24x24/cancel.png%Exit" Module FvwmForm FvwmForm-QuitVerifywithout the call of DestroyMenu within the script, you can add menu items by changing .fvwmrc

You can add the function to FvwmStartFunc by
+ I Test (Init) CreateMenuFvwmRoot

Okaay, I tought that's it's quite easy to edit the menu generator script, too, but I guess it's still easier this way. Accepted.

You are a true Fvwm zealot. I can recognize one from a mile.

I'm far away from that, I'm afraid.  

Christoph
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88278\"][{POST_SNAPBACK}][/a][/div]

I refered to the attitude. You are not far away from that. Are you using Fvwm on destop or not yet?

[jerrybme]

But there's the part of the .xinitrc that do this at startup:

Code: [Select]

MODEL=`cat /proc/deviceinfo/product`
echo 'MODEL:'$MODEL
case "$MODEL" in
    SL-C860|SL-C760)
    test -f /etc/X11/kb/corgi.xmodmap && xmodmap /etc/X11/kb/corgi.xmodmap

Found it, you only needed the SL-C750 to be added to the script. Now it works on my C750  

The code below works.

Code: [Select]

MODEL=`cat /proc/deviceinfo/product`
echo 'MODEL:'$MODEL
case "$MODEL" in
    SL-C860|SL-C750|SL-C760)
    test -f /etc/X11/kb/corgi.xmodmap && xmodmap /etc/X11/kb/corgi.xmodmap
Thanks,
Jerry

[Christoph]

Hi zumi,

This problem came in my mind, too. I think what you wrote doesn't solve the problem (but good idea, I will add that $0 in the function, it can come handy). The problem is, that I have no idea how to run the ZaurusMaximize command on all the maximized apps at the appropriate time.
If I put simply "ZaurusMaximize true" in the rotater scripts, it lets me pick a window that will be remaximized.

You were right. I tested it. An "All (Maximized) Maximize true Xp Yp" worked on all maximized windows but they are only restored, even with the "true" parameter.
But a

$FVWMCOMMAND "All (Maximized) ResizeMaximize Xp Yp"

works for me.

Maybe you could try that.

Christoph

[gab74]

On my SL600L (thanks to Zumi for helping me !) i cannot resize the windows, on matchbox i push on the window's corner and i can resize,
in fwm there is no corner to push and if i try to use RESIZE from window menu i'm not able to resize....
Any helps