Suggestions for Puppy 2.18
Suggestions for Puppy 2.18
- Icons: I personally don't like the 2.16 icons. I feel like I'm colorblind looking at them. The 2.13 icons were great, splashy and playfull
- idem for the background which is bland. Sure I can change it but it will make a much better initial impression on people if there's a nice esthetically pleasing background. Note: I do like the new 'Mac' like buttons and scrollbars in 2.16.
- a 'Show Desktop' button just like 2.15CE
- TrueCrypt compiled into the kernel plus OneKript GUI
- the default application icon is an 'X' how about changing it to something more playfull?
- replace Mozilla mail with Sylpheed.
- better usabillity. Puppy does most things great but it would only take a small amount of tweaking to make it truly noob-proof. I've suggested a better HD installer in another post. Networking support could be better too by simply loading the module for a detected network card and connecting automatically via DHCP, for example.
- idem for the background which is bland. Sure I can change it but it will make a much better initial impression on people if there's a nice esthetically pleasing background. Note: I do like the new 'Mac' like buttons and scrollbars in 2.16.
- a 'Show Desktop' button just like 2.15CE
- TrueCrypt compiled into the kernel plus OneKript GUI
- the default application icon is an 'X' how about changing it to something more playfull?
- replace Mozilla mail with Sylpheed.
- better usabillity. Puppy does most things great but it would only take a small amount of tweaking to make it truly noob-proof. I've suggested a better HD installer in another post. Networking support could be better too by simply loading the module for a detected network card and connecting automatically via DHCP, for example.
RutilTv0.14 is released a while back
tktris only 10k compressed
tktris only 10k compressed
[img]http://img230.imageshack.us/img230/8595/ubd6467dp2.png[/img]
[url=http://www.tinyurl.com/54tu74]Visit The Repository[/url] - Helpful and hard-to-find treats for Puppy 3.
[url=http://www.tinyurl.com/c5a68f]Click Here for Puppy Support Chat, + Helpful Links.[/url]
[url=http://www.tinyurl.com/54tu74]Visit The Repository[/url] - Helpful and hard-to-find treats for Puppy 3.
[url=http://www.tinyurl.com/c5a68f]Click Here for Puppy Support Chat, + Helpful Links.[/url]
BigPilot I hope this helps
search for
# Show 'show desktop' button on taskbar
TaskBarShowShowDesktopButton=0 # 0/1
change it to a 1
and now you don't have to wait
really you can change this anytime by just copying the old icons over I think even the names are the same so just overwrite themIcons: I personally don't like the 2.16 icons. I feel like I'm colorblind looking at them. The 2.13 icons were great, splashy and playfull
you can dload some really Great puppy papers at puppylinux.orgidem for the background which is bland. Sure I can change it but it will make a much better initial impression on people if there's a nice esthetically pleasing background. Note: I do like the new 'Mac' like buttons and scrollbars in 2.16.
you can turn this on very easy just edit the file found at /root/.icewm/preferences- a 'Show Desktop' button just like 2.15CE
search for
# Show 'show desktop' button on taskbar
TaskBarShowShowDesktopButton=0 # 0/1
change it to a 1
you can patch the kernel I belive the prepatched kernel source is availabe as a sfs file hereTrueCrypt compiled into the kernel plus OneKript GUI
I belive you can change this by changing these Icons /root/.icewm/icons/app_16x16 /root/.icewm/icons/app_32x32- the default application icon is an 'X' how about changing it to something more playfull?
try the package at http://puppyfiles.org/dotpupsde/dotpups ... 5.0.10.pupreplace Mozilla mail with Sylpheed
and now you don't have to wait
implement the windows key and some common shortcuts to help windoze deserters and mouse haters. eg
win key on its own brings up the 'start menu', with M minimises all apps etc...
for frugal installs, allow all necessary files (vmlinuz, initrd.gz, pup_218.sfs, zdrv_218.sfs, pup_save.2fs, plus other downloaded sfss) to reside in a puppy version folder
(eg kernel parameter PHOME=/pup218 )
win key on its own brings up the 'start menu', with M minimises all apps etc...
for frugal installs, allow all necessary files (vmlinuz, initrd.gz, pup_218.sfs, zdrv_218.sfs, pup_save.2fs, plus other downloaded sfss) to reside in a puppy version folder
(eg kernel parameter PHOME=/pup218 )
I'd like to see Puppy go back to smaller programs (Sylpheed instead of whatever the Mozilla/Firefox email app is called, etc.) by default, with the option to download bloatware later and separately. Internetbloat.sfs, officebloat.sfs, graphbloat.sfs, mediabloat.sfs, anon.
Oh, and less of them. I'm not sure about the version I'm using, but I remember being utterly bewildered by the profusion of calculators and vector graphics editors in my first Puppy. Pick one good one and throw the rest into an sfs.
Just because DSL is ugly as sin and has a useless spreadsheet app and non-functional setup wizard doesn't mean Puppy should give up on small and simple!
Oh, and less of them. I'm not sure about the version I'm using, but I remember being utterly bewildered by the profusion of calculators and vector graphics editors in my first Puppy. Pick one good one and throw the rest into an sfs.
Just because DSL is ugly as sin and has a useless spreadsheet app and non-functional setup wizard doesn't mean Puppy should give up on small and simple!
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
The conclusion of this thread up to now for me is:
You can't please everybody.
Some like this others that.
Some like smaller distro's others want every thing in there.
I think it's time to bring out a modular approach and have people build the functionality they want at boot time or having it prepared before a next boot. f.e. the bootmanager is already something interesting in this aspect.
You can't please everybody.
Some like this others that.
Some like smaller distro's others want every thing in there.
I think it's time to bring out a modular approach and have people build the functionality they want at boot time or having it prepared before a next boot. f.e. the bootmanager is already something interesting in this aspect.
D actually:joki wrote:implement the windows key and some common shortcuts to help windoze deserters and mouse haters. eg
win key on its own brings up the 'start menu', with M minimises all apps etc...
D-Desktop
E-Explorer
R-Run
F-Find
L-Lock
I loooked into it with Rox Key binding, but I don't know what the key's name is or if they even implement it.
Beem, I think you can already do what you describe. I think Barry addressed this same subject recently in another thread. If I remember what he said correctly, you can basically assemble your own custom Puppy from Puppy Unleashed. The disadvantage of doing it that way is that Puppy Unleashed is a much larger download than the standard Puppy ISO. Only a fraction of the total available software in Unleashed will be used to make up a custom Puppy. Someone has to pay for all that wasted bandwidth. Of course, you can order an Unleashed CD from Barry.Béèm wrote:...I think it's time to bring out a modular approach and have people build the functionality they want at boot time or having it prepared before a next boot. f.e. the bootmanager is already something interesting in this aspect.
It would be cool if you could choose the applications you want from a menu, and the server would put together a custom Puppy ISO for you to download.
Last edited by Flash on Tue 29 May 2007, 09:48, edited 1 time in total.
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
I think my idea is misunderstood.
I don't need a large download like unleashed, on the contrary.
I am thinking of a basic distribution to which by prepared sfs files and the boot manager (very nice idea) you prepare to load the next boot.
f.e. right now I have prepared to load at boot office-2.2.0.sfs and a wine-0.9.28 ready. (hope a wine-0.9.35.sfs will be made later)
So I don't need the puppy-seamonkey.iso, but a puppy.iso and a seamonkey-1.1.1.sfs (f.e.) and for those wanting other ones a opera-x.x.sfs, a firefox/thunderbird.x.x.sfs etc....
Another benefit is, that newer releases of a product could come quicker to the users. f.e. right now SeaMonkey is still at 1.08, while the 1.1.1 (with spell checking) is out a certain time already.
A devx.sfs for compiling.
And in case more then 3 sfs files are needed that utility to combine sfs files (sorry can't remember for the moment who developed it).
So just a couple of sfs files are needed to cover quite some fields and everybody picks his poison to download. Not a big unleashed one thus.
I hope I made myself more clear now, or else shoot me.
I don't need a large download like unleashed, on the contrary.
I am thinking of a basic distribution to which by prepared sfs files and the boot manager (very nice idea) you prepare to load the next boot.
f.e. right now I have prepared to load at boot office-2.2.0.sfs and a wine-0.9.28 ready. (hope a wine-0.9.35.sfs will be made later)
So I don't need the puppy-seamonkey.iso, but a puppy.iso and a seamonkey-1.1.1.sfs (f.e.) and for those wanting other ones a opera-x.x.sfs, a firefox/thunderbird.x.x.sfs etc....
Another benefit is, that newer releases of a product could come quicker to the users. f.e. right now SeaMonkey is still at 1.08, while the 1.1.1 (with spell checking) is out a certain time already.
A devx.sfs for compiling.
And in case more then 3 sfs files are needed that utility to combine sfs files (sorry can't remember for the moment who developed it).
So just a couple of sfs files are needed to cover quite some fields and everybody picks his poison to download. Not a big unleashed one thus.
I hope I made myself more clear now, or else shoot me.
Suggestions for Puppy 2.18
There is a lot of merit in what Béèm says when he suggests that we start with a base OS and add to it to create a finished article of our own choosing. Flash and G2 agree on the desirability of being able to assemble packages and I similarly agree. G2s remark about this being done within our own system rather than from a server is very valid as far too often bandwidth is exceeded and we wait and wait for it to become available.
How we achieve this is the main stumbling block. So far sfs are being offered up as a solution but when they do not work within 2.16 for multi session nor with a HD install it is counter productive. Would it be possible to establish some means of having specific sfs files available for use and some means of co-joining sfs files into a complete package that each individual could then use to meet their specific needs?
Pupshock wrote “slow down the releases, the puppies are breeding too fast!
How we achieve this is the main stumbling block. So far sfs are being offered up as a solution but when they do not work within 2.16 for multi session nor with a HD install it is counter productive. Would it be possible to establish some means of having specific sfs files available for use and some means of co-joining sfs files into a complete package that each individual could then use to meet their specific needs?
Pupshock wrote “slow down the releases, the puppies are breeding too fast!
Yes, obviously you'd want to download only the drivers for your hardware, and I suppose a hardware probe can only be done by a program (like a minimal Puppy) running on your machine. Would you also need a minimal browser like dillo, to connect to the download repository, or is wget all you'd need? I suppose you'd need at least Xvesa in order to run a GUI? Certainly you'd need the drivers required to get online.GuestToo wrote:well, it might be better if you picked the packages in a program running locally on your own machine, and the program downloaded the necessary packages and assembled them on your own machine ... that is, it might be better if your own machine does the work, rather than the server
Edit: also you'd want the installation program to configure the menus and such to reflect the programs that were installed.
Last edited by Flash on Tue 29 May 2007, 20:07, edited 1 time in total.
My Humble
Should be a basic PUP with network connectivity the smallest 'one' of every application..then you can build + add whatever you want.
So 2 versions basic and the usual...perhaps this basic version would be maintained/released at same time, to keep in sync.
However I realise 2 versions 2x the work maintaining etc
The fact though that you can build your own version one could argue thats enough choice, but not sure all have the nouse/time or motivation to do this.
Thanks to all the devs/maintainers and all the volunteers related to Puppy
Should be a basic PUP with network connectivity the smallest 'one' of every application..then you can build + add whatever you want.
So 2 versions basic and the usual...perhaps this basic version would be maintained/released at same time, to keep in sync.
However I realise 2 versions 2x the work maintaining etc
The fact though that you can build your own version one could argue thats enough choice, but not sure all have the nouse/time or motivation to do this.
Thanks to all the devs/maintainers and all the volunteers related to Puppy
All very good suggestions...
MU's Samba server package is very small... So Puppy can share like Win.
Fix Puppy being booted with all it's files in a sub dir. (like /puppy218).
This allows booting of many Puppy versions that're on a single partition or CD.
Extra addon SFS files should be in a common dir. (like /sfs) for any Puppy to use.
This would also make it easy for the BootManager to find the extra SFS files.
Puppy should stop relying on anything being in the root of a partition.
Barry has already taken a first step to modularity, the zdrv SFS file.
This was a good idea, but I think it's mounted & the modules are used from it.
It should be mounted, the needed modules copied to the Save file & unmounted.
This reduces the number of union mounts by 1 (if it's not done this way already).
Have Puppy network boot with the normal SFS instead of a huge initrd.gz.
With a Samba share this could allow low ram PCs to network boot also.
A Samba share would also give any network boot setup a SAVE space.
And an option to load the boot & extra SFS files to ram for PCs with lots of it.
MU's Samba server package is very small... So Puppy can share like Win.
Fix Puppy being booted with all it's files in a sub dir. (like /puppy218).
This allows booting of many Puppy versions that're on a single partition or CD.
Extra addon SFS files should be in a common dir. (like /sfs) for any Puppy to use.
This would also make it easy for the BootManager to find the extra SFS files.
Puppy should stop relying on anything being in the root of a partition.
Barry has already taken a first step to modularity, the zdrv SFS file.
This was a good idea, but I think it's mounted & the modules are used from it.
It should be mounted, the needed modules copied to the Save file & unmounted.
This reduces the number of union mounts by 1 (if it's not done this way already).
Have Puppy network boot with the normal SFS instead of a huge initrd.gz.
With a Samba share this could allow low ram PCs to network boot also.
A Samba share would also give any network boot setup a SAVE space.
And an option to load the boot & extra SFS files to ram for PCs with lots of it.