OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Zumi on July 12, 2005, 08:54:03 pm
-
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: [ You are not allowed to view attachments ]
See the post about the new release here (https://www.oesf.org/forums/index.php?showtopic=13821&view=findpost&p=88585)!
Old releases:
Download the 0.3.0 release: [ You are not allowed to view attachments ]
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
-
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/ (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 (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 :)
-
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 ?
-
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
-
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
-
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
-
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 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:
! This is the screen swivel sensor
keycode 110 = XF86RotateWindows! 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 )
-
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
-
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
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
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:
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:
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
-
Hi Zumi,
If you just call plain "ZaurusMaximize" fvwm doesn't know which window to maximize, but
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
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?
-
But there's the part of the .xinitrc that do this at startup:
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.
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
-
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
-
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 ???
-
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 ???
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88496\"][{POST_SNAPBACK}][/a][/div]
The window borders got a little thin in the 0.3.0 version. There will be a 3 pixel wide one in the next release.
But if you change your .fvwm2rc this way (diff style, so add lines with +, remove that begin with -):
-Style * BorderWidth 1, HandleWidth 1
+Style * BorderWidth 3, HandleWidth 3
-+ BorderStyle Simple -- NoInset Flat
-#+ BorderStyle Active Solid black -- NoInset HiddenHandles
-#+ BorderStyle Inactive Solid black -- NoInset HiddenHandles
+#+ BorderStyle Simple -- NoInset Flat
++ BorderStyle Active Solid black -- NoInset HiddenHandles
++ BorderStyle Inactive Solid black -- NoInset HiddenHandlesthen it will work instantly.
Zumi
-
Thank you very much Zumi for your help:
I make you mods and now i can resize all my windows, the only i cant is GPSDRIVE, strange under matchbox i've no problem....
1.Can you tell me when fvwm starts problem will be fixed on SL6000?
2.Is it possible having in the bar the controllers for SD/CF an WIFI MEMORY/CPU as in matchbox ?
-
Thank you very much Zumi for your help:
I make you mods and now i can resize all my windows, the only i cant is GPSDRIVE, strange under matchbox i've no problem....
I can't try that now. I will compile a new cvs version from gpsdrive in the near future and I will try this out with that.
1.Can you tell me when fvwm starts problem will be fixed on SL6000?
Here's a 0.3.1-pre1 version. I will write changelog, futher plans and updated readme for the 0.3.1, but this is without "support".
http://web.interware.hu/radon/pda/fvwm-pda...e1_armv5tel.ipk (http://web.interware.hu/radon/pda/fvwm-pdaxrom_0.3.1-pre1_armv5tel.ipk)
2.Is it possible having in the bar the controllers for SD/CF an WIFI MEMORY/CPU as in matchbox ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88541\"][{POST_SNAPBACK}][/a][/div]
It will be supported, later, when I will concentrate on writing that FLTK ztaskbar applet.
If somebody has an idea, how to use matchbox applets under fvwm, that will come handy until there's proper support for everything in ztaskbar.
The reason why I really want to write every applet in one application is this:
Memory usage according to "ps x" command output):
ztaskbar: 2000KB
---
mp-applet-clock: 1968KB
mb-applet-battery: 1388KB
mb-applet-menu-launcher (this is the menu button): 2232KB
mb-applet-launcher (this launches an aterm): 1372KB
(others are like these)
So, every little knob on matchbox taskbar use a little less or as much memory as ztaskbar itself.
I don't expect that when there will be all the other applets integrated in ztaskbar (volume control, cpu/mem monitor, cf/sd monitor, wireless monitor, power saving options), its memory usage will go wild, so about 10-15MB... I think it won't be more than 5MB, in the worst case. So I vote for improving ztaskbar.
Zumi
-
Hi,
If somebody has an idea, how to use matchbox applets under fvwm, that will come handy until there's proper support for everything in ztaskbar.
http://freshmeat.net/projects/xystray/ (http://freshmeat.net/projects/xystray/) does the job. I will post an arm version later.
Christoph
-
fvwm-pdaxrom 0.3.1 released!
You can download it here: fvwm-pdaxrom_0.3.1_armv5tel.ipk (https://www.oesf.org/forums/index.php?act=Attach&type=post&id=744)
I made a ThanksTo file (what I post it here for the first time, updates will be in the ipk, .fvwm/ThanksTo file), updated Readme/manual and ChangeLog
======================
fvwm-pdaxrom ChangeLog
======================
0.3.1 (2005-07-17)
* SL6000L support
* corrected xmodmap loading error with SL-C750
* added "Rotate" to the pdaXrom menu
* silkscreen buttons are working (set them with the Input setup
tool)
* the border of the windows are thicker now (3 pixel)
* changed placement policiy to MinOverlapPercentPlacement
* added new keyboard shortcuts
* better maximization, windows get resized after screen is
rotated or when xvkbd started/stoppedThanksTo file:
This a file for thank the people who helped me developing fvwm-pdaxrom.
I try to make a more or less chronological order.
If you think your name should be here, or if you would like to see your
real name and/or email address here, instead of your OESF.org forum
nickname, please send me an e-mail to
Darazs Attila
Thanks to...
============
Everyone who have downloaded fvwm-pdaxrom. I appreciate people using it,
and any feedback you have.
My girlfriend, Szandra, who always hears and watches the "newest and
coolest feature" of fvwm-pdaxrom without saying that it's boring.
Sashz and Laze - for developing pdaXrom and for helping me to continue
my developments on Zaurus.
Jerrybme - for using and testing fvwm-pdaxrom with enthusiasm, for his
encouragements after the releases that kept me going.
Christoph - for a lot of very-very good suggestions and solutions.
Doppiaemme - for helping me with testing the SL6000L support.
Zumi
-
Zumi new release work well on SL-6000 !
-
Hi,
here is the ipk of xystray.
To use it in the ZaurusTaskbar of fvwm, you have to change
the scripts fvwm-portrait.sh and fvwm-landscape.sh
old (landscape):
$FVWMCOMMAND '*ZaurusTaskbar: (25x1, Swallow FvwmIconMan `FvwmIconMan`)
new (landscape):
$FVWMCOMMAND '*ZaurusTaskbar: (21x1, Swallow FvwmIconMan `FvwmIconMan`)
$FVWMCOMMAND '*ZaurusTaskbar: (4x1, Swallow (Respawn) Xystray `Exec exec xystray -iconrows 1 -iconcols 2 -iconsize 32`)
mb-applet-cards
mb-applet-whateveryouwant
old (portrait):
$FVWMCOMMAND '*ZaurusTaskbar: (13x1, Swallow FvwmIconMan `FvwmIconMan`)
new (portrait):
$FVWMCOMMAND '*ZaurusTaskbar: (9x1, Swallow FvwmIconMan `FvwmIconMan`)
$FVWMCOMMAND '*ZaurusTaskbar: (4x1, Swallow (Respawn) Xystray `Exec exec xystray -iconrows 1 -iconcols 2 -iconsize 32`)
mb-applet-cards
mb-applet-whateveryouwant
This will make the icon bar narrower and add the system tray which can hold two icons from matchbox.
It is not perfect but at least it works until the ztaskbar is complete.
Christoph
-
does it work with C1000 (akita)?
if so, you made my day.
if not, the day will most likely come soon
-
does it work with C1000 (akita)?
if so, you made my day.
if not, the day will most likely come soon
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88669\"][{POST_SNAPBACK}][/a][/div]
Dunno. Nobody said anything about trying it on akita here and I only have an SL-C860...
What you have to do:
1. See what's in your /proc/deviceinfo/product file ("SL-C1000", probably)
2. Edit these files:
.xinitrc, .fvwm/fvwm-rotate.sh, .fvwm/model-startup, .fvwm/clamshell/*3. and add the text from /proc/deviceinfo/product, as I did it here (if it's "SL-C1000"):
case "$MODEL" in
SL-C1000|SL-C860|SL-C760|SL-C750|SL-C700)
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
;;
esac
Tell us your results, please!
Zumi
-
Hi,
here is the ipk of xystray.
[...]
Christoph
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88604\"][{POST_SNAPBACK}][/a][/div]
Thank you for the ipk and the code parts!
I'll integrate it in the next version.
Zumi
-
I’ve installed Fvwm-pdaxrom 0.3.1 on SL-C760
I can’t switch keyboard layout from english to russian
When I start FBReader-qt_0.6.3_pdaxrom I see ?????? in book header instead russian word
In full-screen mode (FBReader-qt_0.6.3_pdaxrom) text bottom close with panel
Please help my
-
I’ve installed Fvwm-pdaxrom 0.3.1 on SL-C760
I can’t switch keyboard layout from english to russian
Rename /etc/X11/kb/corgi.xmodmap -> /etc/X11/kb/corgi.xmodmap_en
and /etc/X11/kb/corgi.xmodmap_ru -> /etc/X11/kb/corgi.xmodmap
I think that's the easiest way, but I think you got the idea.
When I start FBReader-qt_0.6.3_pdaxrom I see ?????? in book header instead russian word
In the .fvwm/.fvwm2rc file, there are font definitions like this:
Font "xft:Arial:size=14:encoding=iso8859-1"Change encoding to your preferred russian encoding. (there are different fonts for menu/titlebar, so search for them in the config file)
In full-screen mode (FBReader-qt_0.6.3_pdaxrom) text bottom close with panel
Please help my
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88688\"][{POST_SNAPBACK}][/a][/div]
I don't understand this last part. (And don't know which package is this.)
-
To use it in the ZaurusTaskbar of fvwm, you have to change
the scripts fvwm-portrait.sh and fvwm-landscape.sh
old (landscape):
$FVWMCOMMAND '*ZaurusTaskbar: (25x1, Swallow FvwmIconMan `FvwmIconMan`)
new (landscape):
$FVWMCOMMAND '*ZaurusTaskbar: (21x1, Swallow FvwmIconMan `FvwmIconMan`)
$FVWMCOMMAND '*ZaurusTaskbar: (4x1, Swallow (Respawn) Xystray `Exec exec xystray -iconrows 1 -iconcols 2 -iconsize 32`)
mb-applet-cards
mb-applet-whateveryouwant
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88604\"][{POST_SNAPBACK}][/a][/div]
Christoph:
Thanks for compiling Xystray !
A quick question though...
Where should I put the mb-applet commands? They work fine if I run them from a terminal within fvwm. However
+ I Exec exec /usr/bin/mb-applet-cardsdoesn't work in the .fvwm2rc file
adding to the .xinitrc.fvwm almost worked
/usr/bin/fvwm &
/usr/bin/mb-applet-cardsHowever when you go to portrait mode the X server crashes.
Thanks,
Jerry
-
Hi,
Where should I put the mb-applet commands? They work fine if I run them from a terminal within fvwm. However
+ I Exec exec /usr/bin/mb-applet-cardsdoesn't work in the .fvwm2rc file
I suggested to put them in the scripts fvwm-landscape.sh and fvwm-portrait.sh
(Look at the last two lines I added).
I don't know, perhaps .fvwm2rc is too early as the Taskbar may still not be
running when the applets are launched.
adding to the .xinitrc.fvwm almost worked
/usr/bin/fvwm &
/usr/bin/mb-applet-cardsHowever when you go to portrait mode the X server crashes.
Try the brutal method and do a
...
# We set the size of the maximized windows
$FVWMCOMMAND 'KillModule FvwmButtons ZaurusTaskbar'
$FVWMCOMMAND 'DestroyFunc ZaurusMaximize'
$FVWMCOMMAND 'AddToFunc ZaurusMaximize I Maximize $0 640p 448p'
killall mb-applet-cards
killall the-other-applets
killall xystray
# This is the definiton for the landscape taskbar
$FVWMCOMMAND 'DestroyModuleConfig ZaurusTaskbar: *'
$FVWMCOMMAND '*ZaurusTaskbar: ButtonGeometry 16x32+0-0'
...
Christoph
-
I suggested to put them in the scripts fvwm-landscape.sh and fvwm-portrait.sh
(Look at the last two lines I added).
Christoph
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88725\"][{POST_SNAPBACK}][/a][/div]
That's where I first tried them but they didn't work in the script when I added them like this:
mb-applet-cards
mb-applet-blankerI just found that if I add the path to the applets in the script it works. I also have to add the '&' so that the second applet will load.
So now I've got:
/usr/bin/mb-applet-cards &
/usr/bin/mb-applet-blankerat the end of the landscape & protrait scripts. And they seem to be working fine. No X crashes as I flip the screen back & forth
Thanks for your help.
Jerry
-
With Openbox + Matchbox FBReader-qt_0.6.3_pdaxrom in full-screen mode view such as screenshot1.gif [ You are not allowed to view attachments ]
With Fvwm FBReader-qt_0.6.3_pdaxrom do such as screenshot2.gif (bottom of the text is enclosed with panel)
[ You are not allowed to view attachments ]
Thank you for your help.
-
Zumi:
I've installed the latest version but can't seem to get either the silk screen buttons nor the shortcut buttons to work
I tried altering the .xinitrc.fvwm file to call the userdefined.xmodmap instead of your fvwm.xmodmap but still doesn't work.
Any ideas?
Thanks,
Jerry
EDIT:
Also, I'm noticing that the light & power settings aren't working in fvwm. I've got mine set to not dim the screen when on AC, but in fvwm the screen will blank after several minutes of inactivity.
-
Hi?
What is the name of that virtual keyboard program that
appears in the screenshot in post#1? I'm trying the
SL-5500 pdaXrom, and hoping it is available.
Thanks for any info, John
-
Hi?
What is the name of that virtual keyboard program that
appears in the screenshot in post#1? I'm trying the
SL-5500 pdaXrom, and hoping it is available.
Thanks for any info, John
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=88765\")
xvkbd - [a href=\"http://homepage3.nifty.com/tsato/xvkbd/]http://homepage3.nifty.com/tsato/xvkbd/[/url]
Zümi
-
With Openbox + Matchbox FBReader-qt_0.6.3_pdaxrom in full-screen mode view such as screenshot1.gif [ You are not allowed to view attachments ]
With Fvwm FBReader-qt_0.6.3_pdaxrom do such as screenshot2.gif (bottom of the text is enclosed with panel)
[ You are not allowed to view attachments ]
Thank you for your help.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88729\"][{POST_SNAPBACK}][/a][/div]
Oh, now I understand! Thanks for the screenshots.
It's because the taskbar is always on top, so the applications can't cover it.
If you remove StaysOnTop from this part of the .fvwm2rc file:
Style ZaurusTaskbar NoTitle, NoHandles, BorderWidth 0, Sticky, WindowListSkip, NeverFocus
Style ZaurusTaskbar CirculateSkip, StaysOnTop, FixedPosition, FixedSize, !Iconifiablewell, than it doesn't StaysOnTop. As this isn't perfect solution, we can start thinking on a better one.
Zumi
-
Zumi:
I've installed the latest version but can't seem to get either the silk screen buttons nor the shortcut buttons to work
Maybe you still have a bad xmodmap file... Try xev, what does it say when you hit the silkscreen buttons? It should call them XF86Launch1-5. If the problem is not this, run the .fvwm/menu-generate.py and maybe it generates some errors for you.
I tried altering the .xinitrc.fvwm file to call the userdefined.xmodmap instead of your fvwm.xmodmap but still doesn't work.
I changed that userdefinied.xmodmap -> fvwm.xmodmap because I made keybindings for the "Home" button and I wanted to make sure that it won't be mapped as alt or ctrl.
Any ideas?
Thanks,
Jerry
EDIT:
Also, I'm noticing that the light & power settings aren't working in fvwm. I've got mine set to not dim the screen when on AC, but in fvwm the screen will blank after several minutes of inactivity.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88741\"][{POST_SNAPBACK}][/a][/div]
Short answer: I know.
Longer: It's because ztaskbar (the systray program; I know it's pretty confusing, I'm planning a name change ), so that ztaskbar doesn't aware of it yet. It won't be hard to add it that when there's an AC - battery change it run the xset program with the proper arguments but I haven't done this yet.
Zumi
-
Maybe you still have a bad xmodmap file... Try xev, what does it say when you hit the silkscreen buttons? It should call them XF86Launch1-5. If the problem is not this, run the .fvwm/menu-generate.py and maybe it generates some errors for you.
Hmm, xev show it calling XF86Launch and the buttons worked as mapped in Matchbox, so I don't think its the xmodmap.
.fvwm/menu-generate.py runs fine, no errors.
Are there any model specific calls related to the xmodmap somewhere else? Any body out there with a C750 with similar issues?
I hate it when I can't figure this stuff out
-
Zumi & Christoph:
I've found that I had multiple instances of the same process running after when switching back & forth from landscape & portrait several times. I had 5 instances of the mb-applet-blanker and 2 instances of xystray. Xystray & the mb-applets were easy to take care of by adding
killall xystray
killall mb-applet-blanker
killall mb-applet-cardsto the begining of the landscape & portrait scripts
Now, I notice that there are several instances of the fvwm-hinge running is that normal? I never seem to have more than 2 running at the same time.
1606 root 1488 S aterm -bg black -fg green -geomet
1607 root 1456 S -bash
2021 root 348 S /usr/lib/fvwm/2.5.12/FvwmCommandS
2136 root 292 S /home/root/.fvwm/fvwm-hinge
2137 root 1100 S /bin/bash /home/root/.fvwm/clamsh
2170 root 292 S /home/root/.fvwm/fvwm-hinge
2171 root 1104 S /bin/bash /home/root/.fvwm/clamsh
2181 root 4136 S /usr/bin/mb-applet-blanker
2201 root 1780 S /usr/lib/fvwm/2.5.12/FvwmButtons
2202 root 3616 S /usr/bin/mb-applet-cards
2203 root 2052 S /usr/lib/fvwm/2.5.12/FvwmIconMan
2204 root 1180 S xystray -iconrows 1 -iconcols 2 -
2205 root 1988 S /home/root/.fvwm/ztaskbar 13 4 no
Here's a screen shot of current config. I haven't gone too crazy yet. Waiting for the release to have a few more twitches worked out.
[ You are not allowed to view attachments ]
Thanks Zumi & Christoph for all your great work. Keep it up!
-
Hi jerrybme,
I've found that I had multiple instances of the same process running after when switching back & forth from landscape & portrait several times. I had 5 instances of the mb-applet-blanker and 2 instances of xystray. Xystray & the mb-applets were easy to take care of by adding
killall xystray
killall mb-applet-blanker
killall mb-applet-cardsto the begining of the landscape & portrait scripts
Just to be sure: If you kill xystray while the taskbar (I mean the whole one as fvwm module, not ztaskbar ) is still running, it may be restarted because of the Respawn option for the swallowing. Maybe you should remove the Respawn (if you haven't done it yet) or do the killall after the module has been stopped in the script.
Christoph
-
@Jerrybme:
This thing looks foobar. (http://www.catb.org/~esr/jargon/html/F/foo.html)
I'll implement xystray and other stuff in a bit more user friendly way in the next version.
Try to debug those scripts you edited. I think you haven't put some applet in the background so the fvwm-landscape.sh doesn't end, that's why you have that much process.
Zumi
Ps.: @Christoph: I applied the patch you sent for the persistent user config files and easier menu editing, thanks!
-
Zumi:
Haven't heard from you in a while. I'm enjoying R12 and wondering if you're planning any updates to your scripts?
Cheers,
-
Zumi:
Any luck getting your ztaskbar app to display fonts better? I've been playing with jefklak's fvwm config
here (http://fvwm.lair.be/viewtopic.php?t=925). I like your ztaskbar for controling the backlight, it works great. I'm in the process of merging your solution for rotating the screen with jefklak's breaking up the config file into seperate parts. With perl & imagemagick installed I've even got screenshot thumbnailing working
Here's some screenshots showing jefklak's modified menu, notice screenshot thumbnail in 2nd screenshot
Still lots to do to, ie merge your menu creation script, create multiple themes, etc.
Cheers,
Jerry