don't laugh ok.. I think there's more to it than providing pwidgets for 4.2 users, or to be exact non-bling users, better to open it as independant project, Whodo's the one to decide for 4.2, but you Sigmund, you're the one to decide about pwidgets.., get my point?

Volunteers works for nothing...small or big the contribution is...if credit given then you should receive..if not? so what?

don't laugh ok.. I think there's more to it than providing pwidgets for 4.2 users, or to be exact non-bling users, better to open it as independant project, Whodo's the one to decide for 4.2, but you Sigmund, you're the one to decide about pwidgets.., get my point?

Volunteers works for nothing...small or big the contribution is...if credit given then you should receive..if not? so what?

I'm going back to 4.1.2 ...and install pwidgets in there...at least it's a done deal (and only Barry alone is entitled of credits)...

I got my pw1.9-10 in my 412..... did you notice the different screenies? Exactly the same issues though. I have every mod needed, plus my gimp and all else is there, dev_x, woof files, old 486 stuff bla, bla, bla, blan, blin, bling!_________________Puppy Linux Blog - contact me for access

I got my pw1.9-10 in my 412..... did you notice the different screenies? Exactly the same issues though. I have every mod needed, plus my gimp and all else is there, dev_x, woof files, old 486 stuff bla, bla, bla, blan, blin, bling!

Here is quick reference. Could may be put into the howto?
Creating a widgetA simple widget
Take a look at /root/.pwidgets/configs/ScrollText. Change the text at bottom of the file. Save new file with another name (keep it in /root/.pwidgets/configs/). Restart Pwidgets, and your new widget is available.
A more complex widget1.) ENGINE
Pwidgets supports 4 widget engines, but 3 of them are hardcoded for a unique widget. Conky is what we have used to build most of our widgets.
- conky (base engine)
- xli (Slideshow)
- xwinwrap (Tv)
- xonclock (Analog-clock)
2.) CONFIG
A widget MUST have a config file in /root/.pwidgets/configs/ (See examples). Normally this is a ordinary conky config file. The config filename will be the widgets name. Content of this directory shows up in 'Available widgets' list in the main gui.
3.) SCRIPTS
If external code needs to be run to fetch new info for the widget, call up the widgets script in /root/.pwidgets/scripts/. The script should have the same name as the config file. It is also possible to run a specified script before reading config file. 'Downspeed' is an example of this. The script file has the same name as the config file with a -pre ending (Downspeed-pre), and is placed in /root/.pwidgets/scripts/.
4.) THEME
Your new widget will follow the global theme settings. If you want to override this you can hardcode colors in config files. Though, the best solution is to make a unique theme for your widget. Themes are placed in /root/.pwidgets/themes/THEME/main. The main file works for all widgets. If a unique theme is specified, this one overrides the main theme. The unique theme should have the same name as the config file (widget name).

5.) PLUGIN
If the new widget requires user configuration to works properly, a plugin may do the job. A plugin is a small gui that edits the widget config file. Plugins are stored in /root/.pwidgets/plugins/, and has the same name as the config file. It will show up automatically when user adds your widget from 'Available widgets' to 'Widget list'. After user input, let the plugin execute:
. /usr/local/pwidgets/locals/english
. /usr/local/pwidgets/func -apply
fixwidgets
This builds the chosen widget tree including the changed info from this plugin._________________Stardust resourcesLast edited by zigbert on Wed 23 Sep 2009, 16:20; edited 3 times in total

Enough indeed! Please accept my apology for the treatment you received in trying to be helpful, and read my directive in the RC2 Bugs & Fixes thread about how I expect things to proceed from this point forward.

Again, my apologies to you trio. _________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

Here is quick reference. Could may be put into the howto?
Creating a widgetA simple widget
Take a look at /root/.pwidgets/configs/Puppylinux. Change the text at bottom of the file. Save new file with another name (keep it in /root/.pwidgets/configs/). Restart Pwidgets, and your new widget is available.
A more complex widget

1.) ENGINE
Pwidgets supports 4 widget engines. When you want to create a new widget, the first point is to define which engine to use.
- conky (Most common)
- xli (Slideshow)
- xwinwrap (Tv)
- xonclock (Analog-clock)
2.) CONFIG
A widget MUST have a config file in /root/.pwidgets/configs/ (See examples). The config filename will be the widgets name. Content of this directory shows up in 'Available widgets' list in the main gui.
3.) SCRIPTS
If external code needs to be run to fetch new info for the widget, call up the widgets script in /root/.pwidgets/scripts/. The script should have the same name as the config file. It is also possible to run a specified script before reading config file. 'Downspeed' is an example of this. The script file has the same name as the config file with a -pre ending (Downspeed-pre), and is placed in /root/.pwidgets/scripts/.
4.) THEME
Your new widget will follow the global theme settings. If you want to override this you can hardcode colors in config files. Though, the best solution is to make a unique theme for your widget. Themes are placed in /root/.pwidgets/themes/THEME/main. The main file works for all widgets. If a unique theme is specified, this one overrides the main theme. The unique theme should have the same name as the config file (widget name).

5.) PLUGIN
If the new widget requires user configuration to works properly, a plugin may do the job. A plugin is a small gui that edits the widget config file. Plugins are stored in /root/.pwidgets/plugins/, and has the same name as the config file. It will show up automatically when user adds your widget from 'Available widgets' to 'Widget list'. After user input, let the plugin execute:
. /usr/local/pwidgets/locals/english
. /usr/local/pwidgets/func -apply
fixwidgets
This builds the chosen widget tree including the changed info from this plugin.

Well HOWTO is my department so I can do, will simplify to the best of my ability.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum