pWidgets 2.5.8
conky config cpu-ram bar
as the widgets keep building up, i made one pwidget item which consist of cpu-ram monitor in bars. it will give more space for pwidgets user to show more widgets on the list. Anyhow for you experienced users, this is just a child's drawing, but for new users, just copy the lines below and save it in the /root/.pwidgets/configs/ , you'll get a new widget instantly on the list when you start pwidgets control panel from the desktop start menu. and you can get so much more by making conky config files like this by yourself, please look up on the net....
#this is a Pwidgets config file
#the actual building of the graphics is defined in bottom of this file, - after 'TEXT'.
#Cpu-ram monitor
#### PWIDGETS #####
HEIGHT=65
OFFSET_X=20
#### CONKY ####
#color0:headings color1:base-info color2:extra-info color3:markers color5:green color6:red
color0 9C8F5B
color1 777777
color2 white
color3 ffab00
color5 499D3A
color6 red
background no
own_window yes
own_window_type override
#own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
own_window_transparent yes
#own_window_colour hotpink
double_buffer yes
total_run_times 0
update_interval 1
minimum_size 160 5
draw_shades yes
draw_outline no
draw_borders no
stippled_borders 2
border_margin 4
border_width 1
default_color white
default_shade_color 333333
default_outline_color red
no_buffers yes
uppercase no
use_spacer none
use_xft yes
xftfont DejaVu :style=bold:size=9
TEXT
${color0}R A M ${color5}${membar 10,110}
${color0}C P U ${color3}${cpubar 10,112}
#this is a Pwidgets config file
#the actual building of the graphics is defined in bottom of this file, - after 'TEXT'.
#Cpu-ram monitor
#### PWIDGETS #####
HEIGHT=65
OFFSET_X=20
#### CONKY ####
#color0:headings color1:base-info color2:extra-info color3:markers color5:green color6:red
color0 9C8F5B
color1 777777
color2 white
color3 ffab00
color5 499D3A
color6 red
background no
own_window yes
own_window_type override
#own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
own_window_transparent yes
#own_window_colour hotpink
double_buffer yes
total_run_times 0
update_interval 1
minimum_size 160 5
draw_shades yes
draw_outline no
draw_borders no
stippled_borders 2
border_margin 4
border_width 1
default_color white
default_shade_color 333333
default_outline_color red
no_buffers yes
uppercase no
use_spacer none
use_xft yes
xftfont DejaVu :style=bold:size=9
TEXT
${color0}R A M ${color5}${membar 10,110}
${color0}C P U ${color3}${cpubar 10,112}
- Attachments
-
- mypwidgets.jpg
- (27.8 KiB) Downloaded 1404 times
Last edited by trio on Fri 02 Jan 2009, 04:38, edited 3 times in total.
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Hey that looks nice
ttuuxxx
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
@01micko, zigbert, and all
I think i found the best tweak for fixwidgets (start up):
sleep 3 #number of seconds before execution
xevent -a 0 100 #number of pixels for cursor to deviate right and down
sleep 0.1 ; xevent -b 1 2 #simulated left mouse click
sleep 0.1 ; xevent -a 512 5000 #move cursor far far away from anything
sleep 0.1 ; xevent -b 3 #simulated right mouse click
sleep 0.1 ; xevent -a 512 384 #move back cursor to the middle
I can put less sleep time (depending on your machine I guess, the most secure is 6), and also it eliminates the "won't release" mouse clicked which is very annoying (and for some who have startmenu bar on top of the screen, maybe use: sleep 0.1 ; xevent -a 512 -5000 #move cursor far far away from anything or sleep 0.1 ; xevent -a 900 80 #move cursor to the xonclock and right click there) I tried them all and works fine
Please try, thank you
@tuxxxx
Thank you for the comment
I think i found the best tweak for fixwidgets (start up):
sleep 3 #number of seconds before execution
xevent -a 0 100 #number of pixels for cursor to deviate right and down
sleep 0.1 ; xevent -b 1 2 #simulated left mouse click
sleep 0.1 ; xevent -a 512 5000 #move cursor far far away from anything
sleep 0.1 ; xevent -b 3 #simulated right mouse click
sleep 0.1 ; xevent -a 512 384 #move back cursor to the middle
I can put less sleep time (depending on your machine I guess, the most secure is 6), and also it eliminates the "won't release" mouse clicked which is very annoying (and for some who have startmenu bar on top of the screen, maybe use: sleep 0.1 ; xevent -a 512 -5000 #move cursor far far away from anything or sleep 0.1 ; xevent -a 900 80 #move cursor to the xonclock and right click there) I tried them all and works fine
Please try, thank you
@tuxxxx
Thank you for the comment
Last edited by trio on Fri 02 Jan 2009, 03:41, edited 2 times in total.
My desktop with a new Rolex. I altered some parameters but need to know where the hands are kept.
- Attachments
-
- My-desktop.jpg
- (53.73 KiB) Downloaded 613 times
@trio and zigbert
What we need to do to speed up the slideshow loading is alter the script with this in mind;
we must find out what is in ~/.pwidgets/misc/scaledimages.
if /scaledimages contains the file 01.jpg then this part of the script can run
else run this
fi
I think I'm on the right track there. We'll see...
What we need to do to speed up the slideshow loading is alter the script with this in mind;
we must find out what is in ~/.pwidgets/misc/scaledimages.
if /scaledimages contains the file 01.jpg then this part of the script can run
Code: Select all
#The actual slideshow
TMP=$[$OFFSET_Y+7]
echo "xli -geometry +$X_POS2+$TMP -delay $DELAY -goto $SCALED_DIR/01.jpg $SCALED_DIR/*.jpg &" >> $HOME/.pwidgets/tmp/pwidgets-exec
;;
*)
Code: Select all
#build scaled images in a temporary storage
echo "scale2pics \"$IMAGE_DIRECTORY\" $SCALED_DIR 126 95 85 jpg" >> $HOME/.pwidgets/tmp/pwidgets-exec
#The actual slideshow
TMP=$[$OFFSET_Y+7]
echo "xli -geometry +$X_POS2+$TMP -delay $DELAY -goto $SCALED_DIR/01.jpg $SCALED_DIR/*.jpg &" >> $HOME/.pwidgets/tmp/pwidgets-exec
;;
I think I'm on the right track there. We'll see...
Puppy Linux Blog - contact me for access
Thanks Trio, unfortunately that's not it.
I had already altered the settings there for setting the clock centre and the hands dimensions.
It's the hands themselves I was trying to change. I was going to use the Rolex 'mercedes' hands.
I suspect they are hard coded in xonclock. In Clocx they are changeable in the seperate ini files.
I had already altered the settings there for setting the clock centre and the hands dimensions.
It's the hands themselves I was trying to change. I was going to use the Rolex 'mercedes' hands.
I suspect they are hard coded in xonclock. In Clocx they are changeable in the seperate ini files.
@tasmod:
Well in that case, I think you're right, the hands are not changeable, only the colors of the hands
@01micko:
Yeah, you might try that, but what I was thinking is more a GUI thing for new users (user friendly), and once the scaledimages are settled, the execution of scaled2pics is a no go. until the user open the GUI again
BTW: have you tried my suggestions of the xevent start up thing of fixwidgets?
Well in that case, I think you're right, the hands are not changeable, only the colors of the hands
@01micko:
Yeah, you might try that, but what I was thinking is more a GUI thing for new users (user friendly), and once the scaledimages are settled, the execution of scaled2pics is a no go. until the user open the GUI again
BTW: have you tried my suggestions of the xevent start up thing of fixwidgets?
With that mod to the script it should be automatic to bypass the original images folder and the slideshow will run immediately. I'm experimenting and hope to come up with something by Monday.trio wrote: @01micko:
Yeah, you might try that, but what I was thinking is more a GUI thing for new users (user friendly), and once the scaledimages are settled, the execution of scaled2pics is a no go. until the user open the GUI again
BTW: have you tried my suggestions of the xevent start up thing of fixwidgets?
I think zigbert has xevent clicking on the side of the screen now anyway to avoid conflict with the bar at the top of screen.
##########################
I've been testing Pwidgets in 'woof' too. It uses xfce. Very nice interface. It works perfect. You can see a shot on the "|misc|anyone tried woof yet" thread.
Puppy Linux Blog - contact me for access
[quote="01micko]
I think zigbert has xevent clicking on the side of the screen now anyway to avoid conflict with the bar at the top of screen.
##########################
I've been testing Pwidgets in 'woof' too. It uses xfce. Very nice interface. It works perfect. You can see a shot on the "|misc|anyone tried woof yet" thread.[/quote]
Well, from the pwidgets.04.pet sometimes the mouse click won't release in my computer...with the trick I mentioned, it releases...but anyway, if zigbert is happy with the current start up and no one complains, so let it be
I think zigbert has xevent clicking on the side of the screen now anyway to avoid conflict with the bar at the top of screen.
##########################
I've been testing Pwidgets in 'woof' too. It uses xfce. Very nice interface. It works perfect. You can see a shot on the "|misc|anyone tried woof yet" thread.[/quote]
Well, from the pwidgets.04.pet sometimes the mouse click won't release in my computer...with the trick I mentioned, it releases...but anyway, if zigbert is happy with the current start up and no one complains, so let it be
trio
Keep workng on it! It is difficult to reproduce every individuals cicumstance. Your code did not work for me in jwm. It opened the 'add icon' sidebar and the clock failed to appear. Seems what can work in Icewm may fail in Jwm. However, we must try to find a solution for both, in many different scenarios. It is not easy, but I'm sure the right solution is out there. Do not be discouraged!
Cheers,
Mick
Keep workng on it! It is difficult to reproduce every individuals cicumstance. Your code did not work for me in jwm. It opened the 'add icon' sidebar and the clock failed to appear. Seems what can work in Icewm may fail in Jwm. However, we must try to find a solution for both, in many different scenarios. It is not easy, but I'm sure the right solution is out there. Do not be discouraged!
Cheers,
Mick
Puppy Linux Blog - contact me for access
@micko:
No, it's ok. Clock won't appear just because of the sleep value, as usual, put bigger value like 5 or 6. The more important thing is the mouse click release. I used a simulated right click on something that won't open anything when clicked. Maybe zigbert can make a code to automatically calculate to move cursor on the xonclock center, as it won't open anything when right clicked. - I am not much of a coder...sorry to say
No, it's ok. Clock won't appear just because of the sleep value, as usual, put bigger value like 5 or 6. The more important thing is the mouse click release. I used a simulated right click on something that won't open anything when clicked. Maybe zigbert can make a code to automatically calculate to move cursor on the xonclock center, as it won't open anything when right clicked. - I am not much of a coder...sorry to say
So far I can print whether 01.jpg exists01micko wrote:@trio and zigbert
What we need to do to speed up the slideshow loading is alter the script with this in mind;
we must find out what is in ~/.pwidgets/misc/scaledimages.
if /scaledimages contains the file 01.jpg then this part of the script can runelse run thisCode: Select all
#The actual slideshow TMP=$[$OFFSET_Y+7] echo "xli -geometry +$X_POS2+$TMP -delay $DELAY -goto $SCALED_DIR/01.jpg $SCALED_DIR/*.jpg &" >> $HOME/.pwidgets/tmp/pwidgets-exec ;; *)
fiCode: Select all
#build scaled images in a temporary storage echo "scale2pics "$IMAGE_DIRECTORY" $SCALED_DIR 126 95 85 jpg" >> $HOME/.pwidgets/tmp/pwidgets-exec #The actual slideshow TMP=$[$OFFSET_Y+7] echo "xli -geometry +$X_POS2+$TMP -delay $DELAY -goto $SCALED_DIR/01.jpg $SCALED_DIR/*.jpg &" >> $HOME/.pwidgets/tmp/pwidgets-exec ;;
I think I'm on the right track there. We'll see...
Code: Select all
[ -e ~/.pwidgets/misc/scaledimages/01.jpg ] && echo "TRUE" || echo "FALSE"
Code: Select all
[ -e ~/.pwidgets/misc/scaledimages/01.jpg ] && echo "TRUE" || echo "FALSE"
#"File exists" = "$TRUE"
#"File does not exist" = "$FALSE"
if [ ~/.pwidgets/misc/scaledimages/01.jpg = "FALSE" ] ; sleep 1
then touch ~/.pwidgets/misc/scaledimages/01.jpg
sleep 1
scale2pics ~/images ~/.pwidgets/misc/scaledimages 126 95 85 jpg &
sleep 3 #time for Scale2pics to scale images
xli -geometry +870+600 -delay 5 -goto ~/.pwidgets/misc/scaledimages/01.jpg ~/.pwidgets/misc/scaledimages/*.jpg &
else [ ~/.pwidgets/misc/scaledimages/01.jpg = "TRUE" ] ; sleep 1
xli -geometry +870+600 -delay 5 -goto ~/.pwidgets/misc/scaledimages/01.jpg ~/.pwidgets/misc/scaledimages/*.jpg &
exit 0
fi
Back to the drawing board....
Puppy Linux Blog - contact me for access
I just wanted thank everyone for all the hard work on this project! I use the digital clock, the weather, calendar, and CPU PWidgets. It took my a little time to figure out the F/C weather conversion.
I still need to figure out why the digital clock is in military/metric 24 hour times instead of the 12 hour system we use here in the US. I'll go to the .onclock file and see if I can figure it out. I'm sure something is in there.
I still need to figure out why the digital clock is in military/metric 24 hour times instead of the 12 hour system we use here in the US. I'll go to the .onclock file and see if I can figure it out. I'm sure something is in there.