Puppy Linux Discussion Forum

[sc0ttman]

[sc0ttman]

also, I read users of netbooks (and smaller screens in general) complaining that sub-menus are a real pain the neck... I personally feel no need for them, but dont mind having them.. So I'm not voting either way..

[sc0ttman]

EDIT: translations for french, german, russian and spanish here: http://www.murga-linux.com/puppy/viewtopic.php?p=555135#555135

[L18L]

[technosaurus]

v 0.4 is released with more translations and a bugfix that fixes broken keybindings. See initial post for .pet.

Would it be easier on everyone (read developers) if I return jwm_menu_create going to stdout instead of creating the jwmrc file directly? I could always include a wrapper script(s) for the general user.

This is a little template for my next jwm tool (jwm_image_view), I still need to write the script to go with it, but it will be similar to jwm_notify

[technosaurus]

Ok here is the next jwm tool as promised, you will need to add

[Bert]

JWM Menu categories Dutch translation.

[sc0ttman]

0.4 is looking awesome!!

[technosaurus]

jwm_tools-0.5 released see initial post for .pet
Changelog:
v 0.5
added jwm_image_view ... usage: jwm_image_view [images]
add drive tray ... usage jwm_create_drives
fixed a bug in jwm_notify -- used by the drive tray
removed static ${HOME}/.jwm/jwmrc-install - autogenerate with jwm_install_menu_create
blacklisted only BuildingBlock,DOC,DEV in jwm_install_menu_create (NLS should appear now)
added TODOs
- split out localizations in separate files to be sources
- background setting - already have image_viewer & gtk2jwm for the colors

[technosaurus]

Ok, I now have a goal for the 1.0 version

I am tired of simple little changes to the "static" xml files (which are still valid xml) borking some aspect of something. There a several different tools out there with various methods of poking/prodding the xml with the shell to beat it into submission and as many different styles of breaking it all out. So I tried to come up with the simplest way to fix/support all of these issues/concerns.

as I posted in the pupngo thread

I think I have come up with a way to let users (or pupleteers) choose and support everywhere from a single jwmrc to a separate include for every parameter. Almost too simple, so I am sure it will need tweaks....

just use a separate config file with

Var1=
Var2=
... where the vars are all the parameters covered in http://joewing.net/programs/jwm/config.shtml

Easily sourced by...for instance?
. $HOME/.JWMRC
A program could choose to use only 1 or all vars to generate 1 or many xml files

And it would be fast and easy to modify with the while read line case format.

Thoughts?

[maxerro]

From users' point of view the advantage would be that they could quickly define several jwm profiles that they could switch easily. Or the emphasis is on detail of customization?

[technosaurus]

not sure the question, but maybe this will answer it

v0.6 is released


1. monolithic configuration file that can easily be used by any program to know what the jwm settings are, use them, change them etc... without having to hack at xml files with the shell
2. script to modify the configuration file (up to 9 parameters at a time)
3. jwm_menu_create now uses the config file (at ${HOME}/.jwm/JWMRC) to set almost all parameters (tray, keys and groups not yet implemented - see ${HOME}/.jwm/jwmrc-extra)
4. Submenus and drive icon tray are now enabled/disabled via JWMRC
5. drive tray is now part of the main .jwmrc if enabled
6 removable drives now display a usb icon (devicehandler doesn't however have an unmount option... or other frills )
7. jwm_notify and jwm_image_view now share a temporary jwmrc file (${HOME}/.jwm/jwmrc-tmp)
8. add jwm_param_set to modify jwm settings
usage:
jwm_param_set 'DRIVES="true"'
jwm_menu_create && jwm -restart
#will rebuild the jwmrc and include a drive tray at bottom center
jwm_param_set 'DRIVES=""'
jwm_menu_create && jwm -restart
#will rebuild the jwmrc and exclude the drive tray at bottom center
even with the extra

a gui wrapper can just do this

[maxerro]

Yes, I can modify the JWMRC (among other things) to answer my question. Thanks.
You have a couple of suggestions in PM. Hope at least some of them will be useful.

[L18L]

As I had some difficulties applying jwm_param_set I was using sed again

[technosaurus]

cut/sed can normally replaced by string manipulations

lets say:

VARNAME='BG="/usr/share/backgrounds/default.jpg"'

and you want this value
NEWVAL=/usr/share/backgrounds/newbg.jpg

echo ${VARNAME//${VARNAME#*=}/\"$NEWVAL\"}


(for more info google bash substring manipulation)

but if you would rather use jwm_param_set, I probably wasn't clear enough on the format

jwm_param_set 'VAR1="value1"' 'VAR2="value2"'
#note double quotes (blue) around value and single quotes (red) around each parameter
I am sure there is a better way to set them, this was the first one I came up with to change multiple parameters while respecting # (in colors) and spaces (font names)