http://tubeguy.org/puppybg/spot_logo_bl ... rayeye.pngdejan555 wrote:I like this one the best
http://tubeguy.org/puppybg/spot_logo_blue_back.png
Not sure about the white eye though.
Better?
http://tubeguy.org/puppybg/spot_logo_bl ... rayeye.pngdejan555 wrote:I like this one the best
http://tubeguy.org/puppybg/spot_logo_blue_back.png
Not sure about the white eye though.
Thanks for the feedback!scsijon wrote:@tubeguy, personally what i'd to see happen (please):
1/ get rid of the pipe (anti-smoking legislation and all that stuff does include pipes in australia), really don't think puppy (and barry as it's public officer) needs those hastles;
2/ put a 'cloud' symbol above spup and have the version number appear in it (?could this be done as part of the loading or running rather than have to be manually recreated for each version), don't know the number of times i've had to search to find which one i'm using at that time when testing and found i'm testing on an old one;
3/ allow users to 'do' the background colour themselves (if possible) from a full colourset;
and
4/ Make it suitable to be the background image as well as spup 'icon'.
just my thoughts
scsijon
ps preferably not a white-spot in eye, usually associated with glaucomic blindness in both humans and animals.
Wrong;tubeguy wrote:scsijon wrote:@tubeguy, personally what i'd to see happen (please):
1-The pipe is a subhuman/slackware thing
Hi, thanks for the quick reply.tubeguy wrote:3-Do you mean multiple versions with different backgrounds?
4-Originals are 2000px wide so backgrounds are not a problem. Not sure how the rectangular format will translate to an icon though.
Subgenius. I meant Subgenius. Brain damage from past excesses.rjbrewer wrote:tubeguy wrote:Wrong;scsijon wrote:@tubeguy, personally what i'd to see happen (please):
1-The pipe is a subhuman/slackware thing
Slack and the pipe are from Reverend J.R.(Bob) Dobbs and the
Church of the Subgenius.
3- Not sure how that would be done. Transparent background is easy though, just has to be a png or gif or other format that can do transparency. With that anyone can open it in gimp and make their own background.scsijon wrote: Hi, thanks for the quick reply.
for 3/ I was considering if it could be userset, say like the 'base' as forground and fixed with the background setable by the user? Like having a transparent background, not sure if it could be done though.
for 4/ most people don't realize you can have any shape for an icon in linux, it's just having the config capable of displaying them. It's only by default that we use squares.
Part of the reason why I sugested all installs via ppm, it does at least some checking, like dependancies, and it's not only deb's for fairness, i've had early pets do the same, especially when found 'not what was thought it was' and uninstalled, lost access to others when bits have been uninstalled also. Maybe as part of the ppm changes some more rigorous checking could be added. It could even be a 2part install, 1stly unpack the package, check against existing or missing dependancies, report if so giving the right to stop, if a ok is pressed then 2-install. etc.rcrsn51 wrote:The ability to install a DEB package just by clicking on it should be removed. There are numerous confirmed cases of this action corrupting the Puppy file system.
I have a theory on why this happens.rcrsn51 wrote:The ability to install a DEB package just by clicking on it should be removed. There are numerous confirmed cases of this action corrupting the Puppy file system.
Code: Select all
# dpkg-deb --help
Usage: dpkg-deb [<option> ...] <command>
Commands:
-b|--build <directory> [<deb>] Build an archive.
-c|--contents <deb> List contents.
-I|--info <deb> [<cfile> ...] Show info to stdout.
-W|--show <deb> Show information on package(s)
-f|--field <deb> [<cfield> ...] Show field(s) to stdout.
-e|--control <deb> [<directory>] Extract control info.
-x|--extract <deb> <directory> Extract files.
-X|--vextract <deb> <directory> Extract & list files.
--fsys-tarfile <deb> Output filesystem tarfile.
-h|--help Show this help message.
--version Show the version.
--license|--licence Show the copyright licensing terms.
<deb> is the filename of a Debian format archive.
<cfile> is the name of an administrative file component.
<cfield> is the name of a field in the main `control' file.
Options:
--showformat=<format> Use alternative format for --show.
-D Enable debugging output.
--old, --new Select archive format.
--nocheck Suppress control file check (build bad
packages).
-z# Set the compression level when building.
-Z<type> Set the compression type used when building.
Allowed values: gzip, bzip2, lzma, none.
Format syntax:
A format is a string that will be output for each package. The format
can include the standard escape sequences \n (newline), \r (carriage
return) or \\ (plain backslash). Package information can be included
by inserting variable references to package fields using the ${var[;width]}
syntax. Fields will be right-aligned unless the width is negative in which
case left alignment will be used.
Use `dpkg' to install and remove packages from your system, or
`dselect' or `aptitude' for user-friendly package management. Packages
unpacked using `dpkg-deb --extract' will be incorrectly installed !
Code: Select all
*.deb)
DLPKG_MAIN="`basename $DLPKG_BASE .deb`"
PFILES="`dpkg-deb --contents $DLPKG_BASE | tr -s ' ' | cut -f 6 -d ' '`"
[ $? -ne 0 ] && exit 1
echo "$PFILES" > /root/.packages/${DLPKG_NAME}.files
install_path_check
dpkg-deb -x $DLPKG_BASE ${DIRECTSAVEPATH}/
if [ $? -ne 0 ];then
rm -f /root/.packages/${DLPKG_NAME}.files
exit 1
fi
Code: Select all
#!/bin/sh
#script name undeb
exec dpkg-deb -x "$@" .
Code: Select all
cd `dirname "$@"`
#-----------
#.deb
#-----------
if echo `basename "$@"` | grep -q '.deb$'; then
Xdialog --wrap --title "DEB" \
--yesno "Do you want to decompress $@ and make a new folder " 0 0
case $? in
0)
echo "Yes chosen."
mkdir -p `basename "$@" .deb`
cp `basename "$@"` `basename "$@" .deb`
cd `basename "$@" .deb`
undeb `basename "$@"`
rm `basename "$@"` .deb
;;
1)
echo "No chosen."
exit
;;
255)
echo "Box closed."
exit
;;
esac
fi
well the point here is because I placed valueI really want to draw on peoples strengths. Here's a thought I had. Joe (big_bass ) seriously dislikes the woof build system. That's fine by me. He likes the set standards and working to them and in some ways I tend to agree
LHP already includes Wine, Fatdog also has an option to install it. Green_dome's Wine versions for pup are kept up-to-date and they work on all pups that I've tried. IMO, it would be better to have an installer like Quickpet or an enhanced PPM that includes Wine for optional installation. Although, I use it daily, not everyone wants or needs to use Windows software.scsijon wrote:thought: I wonder if it's time puppy had Wine built in as part of it's standard packageset? I'm pretty sure green_dome would be willing to work on that bit if asked. http://murga-linux.com/puppy/viewtopic.php?t=53675[/url]
well if i may throw in my two cents, wouldn't it be more efficient/more user friendly to just make a little script that lets you pick between xarchive and deb2pet and just add the deb2pet script in the distro? i dont think its all that large and due to lupu people (like me ) have been getting used to deb packages.well if this is a slackware based distro, Installing Debian packages should be removed, since many of them won't work, a few will, Its just a bad practice to install debian packages on a slackware base and should be Outlawed yes I said Outlawed. But of course automatically sending .deb packages to archiver for extraction purposes only does make sense.
Just my point of view.
ttuuxxx