pWidgets 2.5.8

Message

trio · #256 Post by **trio** » Thu 22 Jan 2009, 11:39

Micko

No prob. I am glad to help out. And I started from zero. Imagine! Now I am able to hack other's codes...even make one or two! How wonderful linux is. One input, please rename MONOFONT.TTF to monofont.ttf, some computers, like mine, cannot read the font. Also, I may have a solution of the clock moves to the left when clicked. Will try later...

#257 Post by MU » Thu 22 Jan 2009, 13:52

concerning the widescreen issue:
scale2png scales pictures in a fixed ratio, because it was made as utility to create thumbnails for websites.
So the width of the preview might change, depending on the aspect ration of the picture.
If you force it to use always "100" as height, the width may vary, it may be 200 or 240, depending on the original.
If you give a width of 200, the height might vary, in the deskicons this had the effect, that parts were not visible in the screenshot widget.
Solution:
use instead "resizepng".
Here you may give arguments, that will be taken exactly.
If you say:
resizepng test.jpg out.png 200 100 80, then the result always will be 200x100 pixel.

It is part of my deskicons, I attach binary+source.
Compiled in Puppy 4.12; to compile a new binay for other systems, simply run "make".
Mark

01micko · #258 Post by **01micko** » Fri 23 Jan 2009, 00:37

So Mark and trio I am thinking we can easily force the rezise of the clock if somone inadvertently chooses the wrong size? That might be a winner. Is resizepng included in Scale2pics Mark? If so, we already have it because our slide show uses Scale2pics, we have the full thing installed as part of Pwidgets-0.4 package. Anyway if not we have it now!

Trio, does it give you some ideas????

Mick

trio · #259 Post by **trio** » Fri 23 Jan 2009, 02:05

Micko,

1. The thing that I tried to fix the clock not to move to the left when clicked failed.

2. It is doable to force the size of the clock, but for what? If you use "clickonclock" fix rather then the "movewindow" fix......no need for that..

That's my opinion, you

01micko · #260 Post by **01micko** » Fri 23 Jan 2009, 02:23

trio

The most stable fix for now is the 'clickonclock'. I have always been of the opinion that this is just a workaround and not a fix. You have proven it is posiible to show clock correctly without the click. This, in the end, will be the better solution.

Like I said, "a developers job is never finished"!

What do you think?

Mick

01micko · #261 Post by **01micko** » Fri 23 Jan 2009, 02:31

Mark

I keep getting 'segmentation fault'. Syntax?

I typed, (with terminal open in current dir)

Code: Select all

resizepng 000_024.JPG new.png 200 150

and various other things and got that error.

Mick

trio · #262 Post by **trio** » Fri 23 Jan 2009, 02:43

Micko,

Maybe I can do something about the clock skin but the easiest and more logical way is to put a warning text message in /root/.pwidgtes/misc/ , for ex. warning.txt, that will consist of warnings such as:

- Clock skin has to be the size of 140x140 pixels
- frame has to be the size of .....x..... pixels
- bla bla

Because not only the clock skin that will have a problem with sizes, also the slideshow frame, maybe the weatherbg, etc (if more widgets with background to be included)

Again, that's my opinion

#263 Post by MU » Fri 23 Jan 2009, 03:11

01micko wrote:Mark

I keep getting 'segmentation fault'. Syntax?

I typed, (with terminal open in current dir)
Code: Select all
resizepng 000_024.JPG new.png 200 150
and various other things and got that error.

Mick

oh sorry, you must add the quality, too:
resizepng 000_024.JPG new.png 200 150 80

Mark

01micko · #264 Post by **01micko** » Fri 23 Jan 2009, 03:17

trio

Entirely up to you mate. I love your work but maybe you need a rest! You have been very busy trying to fix this and have succeeded.

I may try to resize the clock automatically from a different perspective through a separate script or config. I'll look into it.

Sometimes it is nice do do something completely different. I have many side projects, which at times, makes focus on one difficult.

Like they say, 'Rome wasn't built in a day'!

Regards,

Mick

trio · #265 Post by **trio** » Fri 23 Jan 2009, 04:05

I am thinking of that maybe we can use this thread, besides a forum for fixing and updating the pwidgets, but also as a forum to accomodate more people to create widgets in .pet, more like the yahoo widgets or google gadgets thing.....so, on the first page, Zigbert can always update "new widgets" in a "additional widgets" list .........when already tested by him that is.......

01micko · #266 Post by **01micko** » Fri 23 Jan 2009, 04:10

trio wrote:I am thinking of that maybe we can use this thread, besides a forum for fixing and updating the pwidgets, but also as a forum to accomodate more people to create widgets in .pet, more like the yahoo widgets or google gadgets thing.....so, on the first page, Zigbert can always update "new widgets" in a "additional widgets" list .........when already tested by him that is.......

I think that is a cool idea. There is a host of different widgets that could be adapted. Afterall Pwidgets is really a way to manage the widgets using conky as the engine.

trio · #267 Post by **trio** » Fri 23 Jan 2009, 05:47

Hi All,

I just modified the weather background to have transparency...yes..transparency...

Below is the pet package, as noted before, you"ll need to change the weather location code again, as the pet will make your local to be Jakarta

trio · #268 Post by **trio** » Fri 23 Jan 2009, 06:02

weather_bg transparent on a red wallpaper

Edit, made a new pet package....smaller in size

trio · #269 Post by **trio** » Fri 23 Jan 2009, 09:29

Hi, sorry, all the weatherbg.pet on page 17 and 18 are for those of you who uses "movewindow clock fix" for those of you who uses the click on clock fix, please edit usr/sbin/fixwidgets and remove the # on repected lines....I'll upload the pet for click on clock later....

edit: the pet below...warning, do not use the func file with windowmove xonclock fix, use the func file with slide fix only

01micko · #270 Post by **01micko** » Sat 24 Jan 2009, 09:17

Trio

I have thoroughly tested your fixes for 'clickonclock' and 'slide'

It is done now and all I did was increase sleep times for slower systems for the clock.

I had an issue where the slideshow would not appear. It was running, but behind the frame!
I added

Code: Select all

 echo  "sleep 1" >> $HOME/.pwidgets/tmp/pwidgets-exec

immediately before the slideshow and it worked! This is a reasonably fast system for puppy, athlon 2100+. 512ram but it needed that sleep. I also changed the dummy file in scaled images to '000_000.jpg' to try and avoid any conflict with digital camera naming of files.
I will pet it up tonight and pack it off to Whodo.

Again, many thanks for your help, 'teacher' will surely reward you!

Mick

trio · #271 Post by **trio** » Sat 24 Jan 2009, 09:53

Micko,

Yes, I never mentioned it to you, but I had the same problem and put sleep value just as you did...I thought that it was only my slow computer...but actually it will happen to all slow computer...better put the sleep then Mick...

01micko · #272 Post by **01micko** » Sat 24 Jan 2009, 11:52

disaster!

trio · #273 Post by **trio** » Sat 24 Jan 2009, 13:58

One of the most wonderful thing about puppy is we can utilize old laptops...so for those of us who has to type acpi=force in the grub menu.lst ...cannot use the standard pwidgets battery status..so I modified one for you who wants it

01micko · #274 Post by **01micko** » Sat 24 Jan 2009, 14:52

Grrrrrrrrrrrrr

The .pet I uploaded is buggy! I was testing cups and made some wrong settings and couldn't get rid of them so I did 4.2alpha as a "pfix=ram" boot. Ok saved everything elsewhere, no probs, installed pwidgets-fixes and the slideshow doesn't work! It is not building the images in /scaledimages. It was before, must be something trivial.

trio · #275 Post by **trio** » Sat 24 Jan 2009, 15:04

If I may Micko..try this pet

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

pWidgets 2.5.8