Woofy 0.91

Core libraries and systems
Message
Author
stu90

#61 Post by stu90 »

Hi sc0ttman,

Your fix to pick up the .sfs in the .iso worked 8)

And i just noticed what the problem is, for some reason the .sfs in the new .iso is being named wrong - new .sfs is called "puppy_sqzd_4.99.2.sfssqz.sfs" remove the "sqz.sfs" from the end and it boots just fine. :)

cheers.

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#62 Post by sc0ttman »

stu90 wrote:just noticed what the problem is, for some reason the .sfs in the new .iso is being named wrong - new .sfs is called "puppy_sqzd_4.99.2.sfssqz.sfs"
Glad it worked (of sorts!)....

Did you try to set a suffix in the main menu, at the start??
It will help me fix it if I know...
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#63 Post by nooby »

sc0ttman wow this Woofy looks very tempting to try out.

What makes me hesitate is there is no description on what one need.

Does it work on Full install? On frugal install? On USB install and how big should that USB be then? Does a 1GB RAM do or maybe 3GB or something needed or a big swap file to hold things in place? Such info? I have an Atom CPU and them are kind of single core? maybe it does not work on them does it?
I use Google Search on Puppy Forum
not an ideal solution though

stu90

#64 Post by stu90 »

sc0ttman wrote:Also Stu, just a quick question, this got me thinking...

Lots of your remasters do not JWM, is that correct? Have you ever tried editing themes and stuff through Woofy when remastering a non-JWM puppy, that uses OpenBox or whatever?

Would you like something that checks for the WM in use on the ISO, and lets you edit some settings for that WM? (Basically, support for non JWM Wms)..
lucid puppy has openbox as the default windows manager - if i recall i did try the theme setting through woofy but the desktop icons didn't display properly (they were just the normal script icon) - this wasn't a problem for me as i edit the filesystem anyway so just changed the theme, icons, wallpaper etc then.

I have noticed there has been a few puplets lately using openbox / tint2 - so i think it must be growing as a popular alternative to JWM it also as far as i can tell doesn't have the recurring fullscreen problem that JWM suffers ( i think that was one of the reasons lucid puppy used openbox as the default?)

The ability to set the openbox theme could be a nice feature to have in woofy :)
sc0ttman wrote:
stu90 wrote:just noticed what the problem is, for some reason the .sfs in the new .iso is being named wrong - new .sfs is called "puppy_sqzd_4.99.2.sfssqz.sfs"
Glad it worked (of sorts!)....

Did you try to set a suffix in the main menu, at the start??
It will help me fix it if I know...
No, no suffix - the input box is just left blank.

cheers.

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#65 Post by sc0ttman »

stu90 wrote:The ability to set the openbox theme could be a nice feature to have in woofy :)

No, (I added) no suffix - the input box is just left blank.

cheers.
OK thanks... I'll checkout the sfs naming part of the script... Also, if you have any details on how openbox themes work, it would help me in applying the feature to Woofy... Although I can of course check it out myself, but it might take longer... So, up to you...
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

stu90

#66 Post by stu90 »

sc0ttman wrote:
stu90 wrote:The ability to set the openbox theme could be a nice feature to have in woofy :)

No, (I added) no suffix - the input box is just left blank.

cheers.
OK thanks... I'll checkout the sfs naming part of the script... Also, if you have any details on how openbox themes work, it would help me in applying the feature to Woofy... Although I can of course check it out myself, but it might take longer... So, up to you...
I will try to help if i can, although i don't know how much use i will be - probably not much! :( :)

Here is how i manually change the openbox theme:
Open the file /root/.config/openbox/rc.xml and edit the openbox theme > name on line #36:

Code: Select all

   <theme>
    <name>SomeOpenboxThemeHere</name>

Openbox themes are located in /usr/share/themes/
Top directory is the openbox theme name (which is applied to the /root/.config/openbox/rc.xml file) all opebox themes as far
as i can tell have the theme name then the next directory is named openbox-3 which contains the themerc file.

In woof BarryK has a theme GUI with the option to set openbox themes - i think maybe that is set to read the default rc.xml file in the openbox package.

Maybe a command something like this would be needed if some one has changed the openbox theme in woof - that way you could obtain what ever the default openbox theme is in the .iso to change it?

Code: Select all

awk 'BEGIN{ RS="</name>"}{gsub(/.*<name>/,"");print;exit}' /root/.config/openbox/rc.xml
cheers.

stu90

#67 Post by stu90 »

Hi sc0ttman,

I have added option to select/set openbox themes to woofy - i also changed the GTK selection as well as it was picking up both GTK and openbox themes.

Did a quick remaster with woofy - just had a look in the filesystem (didn't boot) Openbox theme and GTK theme seem to be set correctly - will do another remaster later on today and boot into it to confirm.

Image

cheers.
Attachments
woofy.gz
updated /usr/bin/woofy script - updates are tagged with todatys date 25/5/11
(10.07 KiB) Downloaded 910 times

stu90

#68 Post by stu90 »

Just to update:

Fixed bug with setting icon theme.

Made a new remaster of Lucid 525 and booted into it - Openbox, JWM, GTK, icon and wallpaper themes are all set correctly. :)
Attachments
woofy.gz
woofy update v001
(10.1 KiB) Downloaded 839 times

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#69 Post by sc0ttman »

stu90 wrote:Just to update:

Fixed bug with setting icon theme.

Made a new remaster of Lucid 525 and booted into it - Openbox, JWM, GTK, icon and wallpaper themes are all set correctly. :)
Stu.... awesome!!

I will try to apply the changes today to my latest, double check them, test them, and hopefully re-post and updated Woofy today or tomorrow. (It may also include an initrd.gz editor as well... when I get it working with all types of initrd.gz files....)
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#70 Post by sc0ttman »

nooby wrote:sc0ttman wow this Woofy looks very tempting to try out.

What makes me hesitate is there is no description on what one need.

Does it work on Full install? On frugal install? On USB install and how big should that USB be then? Does a 1GB RAM do or maybe 3GB or something needed or a big swap file to hold things in place? Such info? I have an Atom CPU and them are kind of single core? maybe it does not work on them does it?
Sorry nooby, I missed this post... Whoops!

You can use Woofy with any PC, on any pup, full install or frugal, save file or no save file.
If you have a Linux partition, or a large save file (400mb+ free space), you do not even need much RAM.

The only requirement is you have enough space in your chosen working directory
(which could be your RAM, save file or a mounted linux partition)

... and of course, and ISO file to remaster ;)
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#71 Post by sc0ttman »

stu90 wrote:Just to update:

Fixed bug with setting icon theme.

Made a new remaster of Lucid 525 and booted into it - Openbox, JWM, GTK, icon and wallpaper themes are all set correctly. :)
Did you try your updated version with dpup squeezed? I am pretty sure that the main SFS will still not be named correctly on the new ISO, even though it is now found OK in the remaster process...

Here is the relevant code, which creates the SFS file name:

Code: Select all

	# test
	oldsfsname="puppy_sqzd_4.99.2.sfs"
	# create the real sfs name, which will be "$sfsprefix$sfsver$suffix.sfs"
	export sfsver=$(echo "$oldsfsname"| tr '_' '-'| cut -d'-' -f2| cut -b 1-3)
	export sfsprefix=${oldsfsname%%[0-9][0-9][0-9]*}
	export sfsname="$sfsprefix$sfsver$suffix.sfs"
	echo "The sfs created will be called '$sfsname', on the new iso"
I will have to look at this code again, to make it work OK - as the new SFS names coming out of Woof have much longer version numbers, and a new prefix...

If anyone can help improve the code above to create the name for SFS files for new Woof filenames, that would be great. I'll give it a go myself, but if you beat me to it, lovely ;)

Here are some example filenames, know to be created by Woof:

puppy_sqzd_4.99.2.sfs
puppy_spup_121.02.sfs
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

stu90

#72 Post by stu90 »

sc0ttman wrote:
stu90 wrote:Just to update:

Fixed bug with setting icon theme.

Made a new remaster of Lucid 525 and booted into it - Openbox, JWM, GTK, icon and wallpaper themes are all set correctly. :)
Stu.... awesome!!

I will try to apply the changes today to my latest, double check them, test them, and hopefully re-post and updated Woofy today or tomorrow. (It may also include an initrd.gz editor as well... when I get it working with all types of initrd.gz files....)
Sounds good sc0ttman 8)

Maybe hold off for a little bit first as i think i found a problem with fbpanel menu icons in Lucid puppy - as far as i can tell when an icon pack is changed by the puppy 'desktop icon switcher' it generates some resized or renamed icons in /usr/local/lib/X11/pixmaps these icons are missing from the base icon packs so are not present when copying over during the woof remaster - which leaves some of the menu categories in the fbpanel menu with out icons.
This problem doesn't seem to effect JWM menu and is resolved when changing the icon theme, them changing it back in the fbpanel menu.

Maybe what ever command is used to copy/rename/resize or what ever it does in the puppy desktop icon switcher' could be used in woofy to set the icons?

I also added a new option to the theme setting GUI the ability to set a PuppyPin / Desktop icon layout theme like with 01micko's Desktop Template application.

Right now there is the default .iso layout
Minimal layout - Terminal, browser, text editor, media player, file manager + drive icons.
Bare - Drive icons but no application icons.

Image
Attachments
woofy.gz
update - v002
(10.77 KiB) Downloaded 837 times

stu90

#73 Post by stu90 »

sc0ttman wrote:
stu90 wrote:Just to update:

Fixed bug with setting icon theme.

Made a new remaster of Lucid 525 and booted into it - Openbox, JWM, GTK, icon and wallpaper themes are all set correctly. :)
Did you try your updated version with dpup squeezed? I am pretty sure that the main SFS will still not be named correctly on the new ISO, even though it is now found OK in the remaster process...

Here is the relevant code, which creates the SFS file name:

Code: Select all

	# test
	oldsfsname="puppy_sqzd_4.99.2.sfs"
	# create the real sfs name, which will be "$sfsprefix$sfsver$suffix.sfs"
	export sfsver=$(echo "$oldsfsname"| tr '_' '-'| cut -d'-' -f2| cut -b 1-3)
	export sfsprefix=${oldsfsname%%[0-9][0-9][0-9]*}
	export sfsname="$sfsprefix$sfsver$suffix.sfs"
	echo "The sfs created will be called '$sfsname', on the new iso"
I will have to look at this code again, to make it work OK - as the new SFS names coming out of Woof have much longer version numbers, and a new prefix...

If anyone can help improve the code above to create the name for SFS files for new Woof filenames, that would be great. I'll give it a go myself, but if you beat me to it, lovely ;)

Here are some example filenames, know to be created by Woof:

puppy_sqzd_4.99.2.sfs
puppy_spup_121.02.sfs
No the only updated change i tried with Dpup squeezed so far was the one you posted on page 4:

Code: Select all

 [ ! "$oldsfspath" ] && oldsfspath=`find /mnt/oldiso -name puppy_sqzd_\*.sfs -o -name puppy_sqzd_\*.sfs`
This picked up the .sfs location - but the resulting .iso still had the wrong name for the .sfs

8)

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#74 Post by sc0ttman »

stu90 wrote:the only updated change i tried with Dpup squeezed so far was the one you posted on page 4:

Code: Select all

 [ ! "$oldsfspath" ] && oldsfspath=`find /mnt/oldiso -name puppy_sqzd_\*.sfs -o -name puppy_sqzd_\*.sfs`
This picked up the .sfs location - but the resulting .iso still had the wrong name for the .sfs

8)
OK... I think I fixed it. :) Replace the stuff around line 467 with this:
(I left the first and last lines the same, so you know where to put it)

Code: Select all

	echo "The sfs to edit: $oldsfsname"

	# get version, works for puppy_sqzd_4.99.2.sfs, puppy_spup_1.21.02.sfs, etc
	export sfsver=$(echo "${oldsfsname%%.sfs}" | tr '_' '-' | cut -d '-' -f3)
	# if $sfsver still empty, use old style SFS file names
	if [ "$sfsver" = "" ];then
		# this one works for pup_420.sfs, pup_431.sfs, etc
		export sfsver=$(echo "${oldsfsname%%.sfs}" | tr '_' '-' | cut -d '-' -f2)
	fi

	# get the prefix (all characters before the numbers.. example, 'pup_', 'eee-', or 'puppy_spup_')
	export sfsprefix=${oldsfsname%%[0-9]*}

	## create the new sfs name, which will be "$sfsprefix$sfsver$suffix.sfs"
	export sfsname="$sfsprefix$sfsver$suffix.sfs"
	echo "The sfs created will be called '$sfsname', on the new iso"
I will post an new woofy very soon, just got to run a few more tests..

OOH EDIT: missed your previous post... Gonna look at that too.. And you said you won't be much help! ha! :)
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#75 Post by sc0ttman »

Stu,

About the missing icons, I found the key part of the Icon switcher script - it seems to trawl through the given theme dir, then copy or convert the icons, depending on their size and filetype...

I see no reason why I cannot put this in Woofy, hacked up a little bit of course... But before I do, I need to know if you have something similar in your "/usr/sbin/icon_switcher" file...

I am guessing that yours may include extra directories, containing svg files used by fbpanel, or something like that...
Or maybe it is the same... anyway.. Here's what I got, starting from line 67:

Code: Select all

 for ONESVG in `find /usr/local/lib/X11/themes/${NEWTHEME}/ -maxdepth 1 -type f -name \*.svg | tr '\n' ' '`
 do
  ONEBASENAME="`basename $ONESVG .svg`"
  rm -f /usr/local/lib/X11/pixmaps/${ONEBASENAME}48.png
  rsvg-convert -w 48 -h 48 -o /usr/local/lib/X11/pixmaps/${ONEBASENAME}48.png $ONESVG
  rm -f /usr/local/lib/X11/pixmaps/${ONEBASENAME}24.png
  #rsvg-convert -w 24 -h 24 -o /tmp/${ONEBASENAME}24.png $ONESVG
  ##if svg has transparency, JWM does not render properly in x16 bit color, screen out...
  #pngtopnm -mix /tmp/${ONEBASENAME}24.png | pnmtopng > /usr/local/lib/X11/pixmaps/${ONEBASENAME}24.png
  rsvg-convert -w 24 -h 24 -o /usr/local/lib/X11/pixmaps/${ONEBASENAME}24.png $ONESVG
 done
 for ONEPNG in `find /usr/local/lib/X11/themes/${NEWTHEME}/ -maxdepth 1 -name \*.png | tr '\n' ' '` #removed -type f (zigbert - Puppy 4.2)
 do
  ONEBASENAME="`basename $ONEPNG .png`"
  cp -f $ONEPNG /usr/local/lib/X11/pixmaps/
  touch -m /usr/local/lib/X11/pixmaps/${ONEBASENAME}.png #v3.98
  xONEBASENAME="`basename $ONEBASENAME 48`"
  if [ "$xONEBASENAME" != "$ONEBASENAME" ] && [ ! -f /usr/local/lib/X11/themes/${NEWTHEME}/$ONEPNG];then #scale to 24 pixels...
   pngtopnm -alpha $ONEPNG > /tmp/temp.pbm #separate transparency channel.
   pnmscale -reduce 2 /tmp/temp.pbm > /tmp/temp2.pbm
   pngtopnm $ONEPNG | pnmscale -reduce 2 | pnmtopng -alpha=/tmp/temp2.pbm > /usr/local/lib/X11/pixmaps/${xONEBASENAME}24.png
   touch -m /usr/local/lib/X11/pixmaps/${xONEBASENAME}24.png #v3.98
  fi
 done
Barry K, about icon_switcher and the theme directories:
When you choose a theme, and in the 'official' Puppy 4.x the choices are 'FlatOrange', 'Original' and 'StarDust', what actually happens? The chosen theme gets copied into /usr/local/lib/x11/pixmaps. The current theme is whatever is in the 'pixmaps' directory.

Notice that they have '24' or '48' in the name. These are to designate that the icons are 24x24 pixels or 48x48 pixels. The '24' images are only used in the window manager (or tray) menu, not on the desktop -- take a look at the top-level of the 'Menu' (button in the tray, bottom-left of screen).

The 'Original' theme is all PNG images, however you can create a theme with SVG images. The Desktop icon switcher GUI application will convert them to PNG images. The 'FlatOrange' is an example -- note that it has a mix of SVG and PNG images. The SVG files do not have a '24' or '48' in their name as they are scalable.
Also about the Icon layout, it may need some more error checking for other puppy versions, but that is a great addition, too! Just a quixk question though... After each icon layout, you've commented out the wallpaper updates made to PuppyPin...
Any reason for this?

And does anyone know if the file name of the zdrv for puppy_spup or puppy_sqzd?? I reaaally hope it didn't change.. again!
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

stu90

#76 Post by stu90 »

Hi sc0ttman - just a quick comment as i am about to cook tea - will post again later :)

For the icon layout the minimal configuration is formated wrong in my v002 update above - around about line #254 it needs to be changed to:

Code: Select all

  if [ "$minimal" = true ]; then
	echo "Applying minimal desktop icon layout"
    touch -f /tmp/woofyPuppyPin
  cat >> /tmp/woofyPuppyPin <<EOF
<?xml version="1.0"?>
<pinboard>
  <backdrop style="Stretched">/usr/share/backgrounds/default.jpg</backdrop>
  <icon x="32" y="162" label="edit">/usr/local/bin/defaulttexteditor</icon>
  <icon x="32" y="354" label="console">/usr/bin/urxvt</icon>
  <icon x="32" y="450" label="browse">/usr/local/bin/defaultbrowser</icon>
  <icon x="32" y="66" label="file">/usr/local/bin/rox</icon>
  <icon x="32" y="258" label="play">/usr/local/bin/defaultmediaplayer</icon>
</pinboard>
EOF
cheers.

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#77 Post by sc0ttman »

Thanks Stu, I never even noticed... But corrected now ;)

Another question, is there any reason you put the puppypin_options() function inside the get_themes() function? I think it can safely be moved out to the main script, and then there should be no need to re-declare 'set -a' ... Unless I am missing something..
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

stu90

#78 Post by stu90 »

sc0ttman wrote:Thanks Stu, I never even noticed... But corrected now ;)

Another question, is there any reason you put the puppypin_options() function inside the get_themes() function? I think it can safely be moved out to the main script, and then there should be no need to re-declare 'set -a' ... Unless I am missing something..
hey sc0ttman,
good news - Applied your .sfs fix on the previous page and have done a remaster of squeezed puppy .sfs automatically detected and renamed correctly and boots ok :D

Just looked at Barrys download page for squeezed puppy there is a zdrv .sfs to download named "zdrv_sqzd_4.99.2.sfs" - i didn't try with a separate zdrv so am unsure what woofy calls it?
http://distro.ibiblio.org/quirky/test/squeezed-4.99.2/

Regarding the PuppyPin setting - no you won't be missing anything - I should have probibly warned you, what i know about writing scripts you could fit on the back of a postage stamp so best to prepare for unusual oddities, errors and wtf's :P

The commented out lines - i thought they might be needed but looking in some .iso the entry in /root/.config/wallpaper/bg_img doesn't always match the wallpaper that is in the /root/Choices/ROX-Filer/PuppyPin file.

Maybe what is needed is instead to use what ever background is in then PuppyPin - this would mean woofy would need to replace the wallpaper that is in PuppyPin with the new custom wallpaper if one is selected.

Then for setting the Desktop icon layout could maybe do something like below under the EOF - i think this should get any custom wallpaper or if no custom wallpaper used then the .iso default that is in PuppyPin?

Code: Select all

EOF
# display wallpaper line of puppypin #
wall=` grep "<backdrop" $basedir/root/Choices/ROX-Filer/PuppyPin`     
 
# replace woofypuppypin wallpaper line with that of puppypin #
sed -i "
/<backdrop/ c\
$wall" $basedir/tmp/woofyPuppyPin

# replaces puppypin with woofypuppypin #
p -a -v $basedir/tmp/woofyPuppyPin $basedir/root/Choices/ROX-Filer/PuppyPin
fi

Im not quite sure how woofy applies custom wallpapers but maybe something like this could be added to it?

Code: Select all

   
# $woofywallpaper being /path/to/woofy/wallpaper.jpg #
woofywall="<backdrop style="Stretched">$woofywallpaper</backdrop>"
   
   sed -i "
/<backdrop/ c\
$woofywall" $basedir/root/Choices/ROX-Filer/PuppyPin
Looking in /usr/sbin/icon_switcher mine seems to be the same.

Code: Select all

if [ "$NEWTHEME" != "" ];then
 for ONESVG in `find /usr/local/lib/X11/themes/${NEWTHEME}/ -maxdepth 1 -type f -name \*.svg | tr '\n' ' '`
 do
  ONEBASENAME="`basename $ONESVG .svg`"
  rm -f /usr/local/lib/X11/pixmaps/${ONEBASENAME}48.png
  rsvg-convert -w 48 -h 48 -o /usr/local/lib/X11/pixmaps/${ONEBASENAME}48.png $ONESVG
  rm -f /usr/local/lib/X11/pixmaps/${ONEBASENAME}24.png
  #rsvg-convert -w 24 -h 24 -o /tmp/${ONEBASENAME}24.png $ONESVG
  ##if svg has transparency, JWM does not render properly in x16 bit color, screen out...
  #pngtopnm -mix /tmp/${ONEBASENAME}24.png | pnmtopng > /usr/local/lib/X11/pixmaps/${ONEBASENAME}24.png
  rsvg-convert -w 24 -h 24 -o /usr/local/lib/X11/pixmaps/${ONEBASENAME}24.png $ONESVG
 done
 for ONEPNG in `find /usr/local/lib/X11/themes/${NEWTHEME}/ -maxdepth 1 -type f -name \*.png | tr '\n' ' '`
 do
  ONEBASENAME="`basename $ONEPNG .png`"
  cp -f $ONEPNG /usr/local/lib/X11/pixmaps/
  touch -m /usr/local/lib/X11/pixmaps/${ONEBASENAME}.png #v3.98
  xONEBASENAME="`basename $ONEBASENAME 48`"
  if [ "$xONEBASENAME" != "$ONEBASENAME" ];then #scale to 24 pixels...
   pngtopnm -alpha $ONEPNG > /tmp/temp.pbm #separate transparency channel.
   pnmscale -reduce 2 /tmp/temp.pbm > /tmp/temp2.pbm
   pngtopnm $ONEPNG | pnmscale -reduce 2 | pnmtopng -alpha=/tmp/temp2.pbm > /usr/local/lib/X11/pixmaps/${xONEBASENAME}24.png
   touch -m /usr/local/lib/X11/pixmaps/${xONEBASENAME}24.png #v3.98
  fi
 done

cheers.

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#79 Post by sc0ttman »

stu90 wrote:hey sc0ttman,
good news - Applied your .sfs fix on the previous page and have done a remaster of squeezed puppy .sfs automatically detected and renamed correctly and boots ok :D
Good, thought it might... :D I've made lots of changes , yet to test any of it so far, but I think it should all work fine.. The next version should be a good one!
stu90 wrote:Just looked at Barrys download page for squeezed puppy there is a zdrv .sfs to download named "zdrv_sqzd_4.99.2.sfs"
Yeah good... I forgot the obvious, and stupidly asked where to find zdrv filename info - Barry says to look inside the DISTRO_SPECS in initrd.gz or in /etc (they should be the same) for the zdrv filename... Here is what spup is using, according to DISTRO_SPECS: "zdrv_spup_121.02.sfs", so that seems to be consistent..

Woofy does not support these zdrv names... yet... But it does support 2 kinds of zdrv naming already used in other pups and older Woof builds... :roll:

But getting the name from DISTRO_SPECS (if it is present) should be easy enough.. For older pups, without DISTRO_SPECS, that's easy too... So even zdrv creation will work for all puppies in the next Woofy :)

The commented out lines - i thought they might be needed but looking in some .iso the entry in /root/.config/wallpaper/bg_img doesn't always match the wallpaper that is in the /root/Choices/ROX-Filer/PuppyPin file.p
I've also found that the wallpaper value in PuppyPin does not seem to be accurate, or match what is used... So that's fine then, can leave that...

About wallpaper setting in Woofy, I think we can leave as is, cos Woofy just adds the new wallpaper image to /usr/share/backgrounds creates a symlink to it called default.jpg - as far as I am aware, this is always the chosen wallpaper on first boot in Puppy... I maybe wrong though, gonna test soon...

If you said that wallpaper changing worked for you, then that's fine...
Looking in /usr/sbin/icon_switcher mine seems to be the same.
Good, I think I will add the relevant code from icon_switcher into the set_themes function... Hopefully that will remove your problems with missing icons in fbpanel...
cheers.
No.... Thank you!
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#80 Post by sc0ttman »

updated to 0.7, see main post... Thanks Stu! :D

EDIT: Re-uploaded 0.7 - fixed important typo .. download again if u already got it

The good news: I am posting this from a remastered Spup alpha, mostly went well, had to do 2 remasters, 2nd one with no zdrv.. See issues below:

known issues with 0.7, will be fixed for 0.8

- do not create a zdrv for any ISO with a different kernel to the one you're using (named wrong)
- wallpaper needs fixing if themes are edited, but wallpaper NOT changed
- add fix for defaultaudioplayer

- in general the 'chroot' parts of the script need looking at, maybe I am doing it wrong
(CONFIRMED.. I'm doing it wrong... help appreciated)

I need something like

Code: Select all

KER=`chroot $basedir uname -r`
I need this to return the kernel version of the mounted SFS, not the host system! Alternatively I could get the kernel version from the /lib/modules dir ... But do I need the full version number, or the shortened symlink??

Please help if you can...

plans for future:

- fix above issues
- new: option to create SFS of removed files - use list
- update: localisation possible
- defaults-chooser 0.9 (GUI to add new default**, show all added, integrate MIME editor)
- choose a kernel pet to change kernel, in the new ISO
- option to make SFS of files removed from ISO
Last edited by sc0ttman on Tue 31 May 2011, 11:38, edited 1 time in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

Post Reply