Puppy 4.4 CE - Phase 1: pet tests
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
Puppy 4.4 CE - Phase 1: pet tests
For a number of reasons I wanted to go ahead and start testing some packages for the 4.4 Community Edition even before Barry releases 4.3.1.
Phase 1 testing pet packages on existing 4.3.X systems
Allowing people to test the proposed programs on their existing 4.3X system will help to identify any issues early on and reduce the number of full releases required. Once the pets have been sufficiently vetted (~1-2 weeks), I will release the first alpha.
Setting up the separate threads for side projects should help to keep the size of this thread from becoming overwhelming and allow for continuity on those projects as the alphas, betas and release candidates roll out. (I plan to start a new thread on each cycle and carry over the main pet and project posts as required)
This process will be repeated as necessary until all Milestones and Goals are sufficiently met. During the process I will consider reasonable requests, compare them against Puppy's overall goals and make my own determination as to whether it is feasible or not. Any optimizations or improvements that do not increase size are an easy decision, all others will require some reduction elsewhere that does not negatively affect usability in any way.
I already have at least 10 milestones and will post them here soon (probably in the 3rd post - "projects"), but if you want a preview of some of the pet updates, just browse puppylinux.asia/members/T/444. I haven't uploaded them all yet, but there is a good sampling so far. One thing that you will notice is that I have some development versions of some of our core apps. I think that this is appropriate at this phase and will have significant long term benefits if the developers receive our bug reports (and fixes where possible)
Phase 1 testing pet packages on existing 4.3.X systems
Allowing people to test the proposed programs on their existing 4.3X system will help to identify any issues early on and reduce the number of full releases required. Once the pets have been sufficiently vetted (~1-2 weeks), I will release the first alpha.
Setting up the separate threads for side projects should help to keep the size of this thread from becoming overwhelming and allow for continuity on those projects as the alphas, betas and release candidates roll out. (I plan to start a new thread on each cycle and carry over the main pet and project posts as required)
This process will be repeated as necessary until all Milestones and Goals are sufficiently met. During the process I will consider reasonable requests, compare them against Puppy's overall goals and make my own determination as to whether it is feasible or not. Any optimizations or improvements that do not increase size are an easy decision, all others will require some reduction elsewhere that does not negatively affect usability in any way.
I already have at least 10 milestones and will post them here soon (probably in the 3rd post - "projects"), but if you want a preview of some of the pet updates, just browse puppylinux.asia/members/T/444. I haven't uploaded them all yet, but there is a good sampling so far. One thing that you will notice is that I have some development versions of some of our core apps. I think that this is appropriate at this phase and will have significant long term benefits if the developers receive our bug reports (and fixes where possible)
Last edited by technosaurus on Thu 24 Sep 2009, 04:05, edited 1 time in total.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
pets are located here
puppy:linux to login
puppy:linux to login
Last edited by technosaurus on Thu 24 Sep 2009, 04:04, edited 1 time in total.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
projects
GTKDialog apps
init hacking
ffmpeg & xinelib
Pcompile
Woo-FF
Puppy Control Panel
ROX right clicks
GTKDialog apps
init hacking
ffmpeg & xinelib
Pcompile
Woo-FF
Puppy Control Panel
ROX right clicks
Last edited by technosaurus on Fri 25 Sep 2009, 05:47, edited 3 times in total.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
Milestones for consideration: (aka wishlist) - taking volunteers
On the fly sfs mounting: Choicepup style or symlink style
Update the core libraries so that newer software is usable - started
Update core applications (or replace if the case warrants it) - started
abiword, gnumeric, mtpaint(now themeable) and many more - started
Update petget and corresponding software to use xz compression - NOT started
Updates to gtkdialog apps
Re-introduce and update the Puppy Control Panel - needs minor update
Finish working on Woo-FF - started
Create GTKdialog version of the Remaster script - NOT started
Create GTKdialog version of the Universal installer - NOT started
... and many more
Boot to GUI using a default keyboard, mouse, timezone and video setting and start with the Puppy Control Panel and a message telling you what the setting is and why/how to change it
Look at having an Opera or QTwebkit based browser (or version) to make installing QT based apps much easier - Planning
Our theme changer seems to copy files - maybe it would be better to simply change one symlink?
Introduce the Puppy Plus pack(s) basically the most often downloaded pets & sfs in a single sfs file - Planning
Introduction of the DOCx_XXX.sfs and NLSx_XXX.sfs - started
Move Geany (possibly others) to the devx_sfs and use Nicoedit etc.. (~500kb savings)
Package Cleanup - cutting bloat, moving common files such as fonts, pixmaps etc to common folders and using symlinks so that other programs can benefit from them as well as updating to the newer 4.3 style specs files and database entries. - ??
Include a basic howto.html in the root of the iso so that new users can learn the basics before they boot the iso. - raffy
Windows and Mac Installers - ??
Run rdfind on final build to replace duplicate files with symlinks (~500kb savings)
Last but not least - fix bugs - ongoing
On the fly sfs mounting: Choicepup style or symlink style
Update the core libraries so that newer software is usable - started
Update core applications (or replace if the case warrants it) - started
abiword, gnumeric, mtpaint(now themeable) and many more - started
Update petget and corresponding software to use xz compression - NOT started
Updates to gtkdialog apps
Re-introduce and update the Puppy Control Panel - needs minor update
Finish working on Woo-FF - started
Create GTKdialog version of the Remaster script - NOT started
Create GTKdialog version of the Universal installer - NOT started
... and many more
Boot to GUI using a default keyboard, mouse, timezone and video setting and start with the Puppy Control Panel and a message telling you what the setting is and why/how to change it
Look at having an Opera or QTwebkit based browser (or version) to make installing QT based apps much easier - Planning
Our theme changer seems to copy files - maybe it would be better to simply change one symlink?
Introduce the Puppy Plus pack(s) basically the most often downloaded pets & sfs in a single sfs file - Planning
Introduction of the DOCx_XXX.sfs and NLSx_XXX.sfs - started
Move Geany (possibly others) to the devx_sfs and use Nicoedit etc.. (~500kb savings)
Package Cleanup - cutting bloat, moving common files such as fonts, pixmaps etc to common folders and using symlinks so that other programs can benefit from them as well as updating to the newer 4.3 style specs files and database entries. - ??
Include a basic howto.html in the root of the iso so that new users can learn the basics before they boot the iso. - raffy
Windows and Mac Installers - ??
Run rdfind on final build to replace duplicate files with symlinks (~500kb savings)
Last but not least - fix bugs - ongoing
Last edited by technosaurus on Thu 24 Sep 2009, 09:56, edited 1 time in total.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Using my (few days old) efforts to program in c++
created this simple 44CE development portal program
You should fill out the registration if you want to help with 4.4CE
so we can contact you
- but most contact will be done through this forum
and as usual registration is a suggestion not a compulsion for inclusion:)
However if the forum is down we still need to contact each other
There is also a link to the wiki, this thread, latest info etc
It also barks, when you need to express approval . . .
Later on we will be able to send testing info using the program (feedback)
Source code is provided of course (puppy44CE.cpp)
and so improvements from real coders welcome
created this simple 44CE development portal program
You should fill out the registration if you want to help with 4.4CE
so we can contact you
- but most contact will be done through this forum
and as usual registration is a suggestion not a compulsion for inclusion:)
However if the forum is down we still need to contact each other
There is also a link to the wiki, this thread, latest info etc
It also barks, when you need to express approval . . .
Later on we will be able to send testing info using the program (feedback)
Source code is provided of course (puppy44CE.cpp)
and so improvements from real coders welcome
- Attachments
-
- p44ce.zip
- (25.36 KiB) Downloaded 2042 times
Some whishes from me:
- Try to follow One Task => One Application
- Unclutter the menu
- get rid of absvolume
- newer ffmpeg
- Add much more keybindings for jwm
- don't compile with "--disable-nls"
- update some parts of devx (autocon, automake,...)
- Setup a default for $CFLAGS
- Add an alias or a wrapper-script for a default configure-pattern
- update isomaster to 1.36 (this might solve an issue with puppy-isos we had with former versions)
- update gphoto and create a gtkdialog-frontend for gphotofs to simply mount a digicam to the regular filesystem
- add ldconfig to the regular iso (now devx)
- Add 'set bell-style none' to /etc/inputrc (matter of taste - i hate this 'bing')
- Add
to /etc/inputrc. if you type a part of a command, you could browse the history with up/down only for the history-subset that matches your part.
Possible add apps:
- htop
- mc with pet-extension (by bruce b)
- ncdu (better than du)
- ddrescue (data recovery)
- mlocate (fast file search)
- asunder (nice cd-ripper)
- lazy (cli-cd-player with the ability to play the cd digital)
- conky (trgular one)
just some quick ideas - sure all egoistic
aragon
- Try to follow One Task => One Application
- Unclutter the menu
- get rid of absvolume
- newer ffmpeg
- Add much more keybindings for jwm
- don't compile with "--disable-nls"
- update some parts of devx (autocon, automake,...)
- Setup a default for $CFLAGS
- Add an alias or a wrapper-script for a default configure-pattern
- update isomaster to 1.36 (this might solve an issue with puppy-isos we had with former versions)
- update gphoto and create a gtkdialog-frontend for gphotofs to simply mount a digicam to the regular filesystem
- add ldconfig to the regular iso (now devx)
- Add 'set bell-style none' to /etc/inputrc (matter of taste - i hate this 'bing')
- Add
Code: Select all
"\e[B": history-search-forward
"\e[A": history-search-backward
Possible add apps:
- htop
- mc with pet-extension (by bruce b)
- ncdu (better than du)
- ddrescue (data recovery)
- mlocate (fast file search)
- asunder (nice cd-ripper)
- lazy (cli-cd-player with the ability to play the cd digital)
- conky (trgular one)
just some quick ideas - sure all egoistic
aragon
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Try this http://www.murga-linux.com/puppy/viewto ... h&id=21934aragon wrote:Some whishes from me:
- get rid of absvolume
aragon
compile on puppy 4.31 its a volume control like absvolume with a button to launch Zmixer, I hacked the source code to use zmixer.
ttuuxxx
Ps here's the brief writeup
http://www.murga-linux.com/puppy/viewto ... 354#343354
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
@ ttuuxxx - I am following a lot of your work with 2.X and saw that (I think with the horizontal sliders if I recall correctly). Hopefully we can work our parallel paths to Puppy's advantage. I'm glad to see you here.
@ Nathan0 - I may need to set something up for it to automatically retrieve its required dependency - If I remember it is rather large and serves no other purpose.
@ Aragon - lots of good suggestions.
I have been testing CFLAGS, CXXFLAGS etc... and plan to incorporate them into Pcompile (and remove --disable-nls from the defaults)
I would like to go with 1 app per task as well accept when two multifunction apps overlap.
Newer ffmpeg is desirable but it will affect many other things that have it as a dependency. Barry has fought this battle already, but I will give it a shot & if I am going to do that I will also look into gstreamer.
Keybindings should probably have a separate thread since many apps have nonstandard bindings - Nicoedit for example uses F5 for history rather than refresh.
I plan to compile the latest usable version of ALL of the apps - Where I will need help on this is ensuring that Puppy patches don't get missed (like programs that use bmp vs png etc...)
As for the other apps - give me the link & I will compile and package them for testing
any file that contains "config" will automatically get put on the devx by default using new2dir - does this apply for any other packages? if so should this behavior be modified?
I really liked the ROX right clicks as well.
I have set up some templates for building gtkdialog guis for command line programs. There are infinite possibilities there.
@ Nathan0 - I may need to set something up for it to automatically retrieve its required dependency - If I remember it is rather large and serves no other purpose.
@ Aragon - lots of good suggestions.
I have been testing CFLAGS, CXXFLAGS etc... and plan to incorporate them into Pcompile (and remove --disable-nls from the defaults)
I would like to go with 1 app per task as well accept when two multifunction apps overlap.
Newer ffmpeg is desirable but it will affect many other things that have it as a dependency. Barry has fought this battle already, but I will give it a shot & if I am going to do that I will also look into gstreamer.
Keybindings should probably have a separate thread since many apps have nonstandard bindings - Nicoedit for example uses F5 for history rather than refresh.
I plan to compile the latest usable version of ALL of the apps - Where I will need help on this is ensuring that Puppy patches don't get missed (like programs that use bmp vs png etc...)
As for the other apps - give me the link & I will compile and package them for testing
any file that contains "config" will automatically get put on the devx by default using new2dir - does this apply for any other packages? if so should this behavior be modified?
I really liked the ROX right clicks as well.
I have set up some templates for building gtkdialog guis for command line programs. There are infinite possibilities there.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
wonderful...technosaurus wrote: I have been testing CFLAGS, CXXFLAGS etc... and plan to incorporate them into Pcompile (and remove --disable-nls from the defaults)
ffmpeg is a challenge, but gstreamer is an adventure (but in my opinion more a horrorshow)Newer ffmpeg is desirable but it will affect many other things that have it as a dependency. Barry has fought this battle already, but I will give it a shot & if I am going to do that I will also look into gstreamer.
yes some apps are a little tricky with that but key-combinations like alt+shift+KEY are a little less problematic. if you like i could create a (wish)-list.Keybindings should probably have a separate thread since many apps have nonstandard bindings - Nicoedit for example uses F5 for history rather than refresh.
will post tomorrow.As for the other apps - give me the link & I will compile and package them for testing
sorry i don't understand ("f*** kraut" i know, but my english is getting better with this forum)any file that contains "config" will automatically get put on the devx by default using new2dir - does this apply for any other packages? if so should this behavior be modified?
yes but heavyI really liked the ROX right clicks as well.
you're having big plans, could become a nice little puppy!
aragon
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
I've compiled Gstreamer a few times and one of the best advantages of it is to recompile alsa with gstreamer support, once you have gstreamer compiled, Like I've mentioned before absvolume or any task bar volume control has never worked on my motherboards, but once I compiled Gstreamer and then recompiled alsa with gstreamer and yes it fully worked for once. Plus other liteweight audio players also use gstreamer and I even made a xfburn package with gstreamer support that can burn videos I guess, never tried, but the support is built in. Probably would be best to have gstreamer compiled first then work on all audio aspects, That has been a drawback on series 4 is a current alsa package, and with gstreamer that would be grandtechnosaurus wrote: I would like to go with 1 app per task as well accept when two multifunction apps overlap.
Newer ffmpeg is desirable but it will affect many other things that have it as a dependency. Barry has fought this battle already, but I will give it a shot & if I am going to do that I will also look into gstreamer.
.
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
Regarding PET-Be-Gone, I haven't installed 4.3 yet so I'm not sure how the package database format has changed and where it is now located. I intend to look at that sometime in the next couple weeks.
Something that would be nice (if 4.3 hasn't already done so) would be to let the user optionally keep the HW clock on UTC time rather than localtime. This would have no impact on size or speed, it's just a minor change of a couple scripts.
http://www.murga-linux.com/puppy/viewtopic.php?t=41680
Something that would be nice (if 4.3 hasn't already done so) would be to let the user optionally keep the HW clock on UTC time rather than localtime. This would have no impact on size or speed, it's just a minor change of a couple scripts.
http://www.murga-linux.com/puppy/viewtopic.php?t=41680
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
RE: pet-be gone and ldconfig -background info FYI when you compile a program, and use new2dir to remove the bloat, the script uses installwatch, sed, grep etc... to copy files to the appropriate directories main, DEV, DOC and NLS one of the strings the script looks for is "config" (assuming that the developer would setup the package before distribuition and it would not be neeeded) Also when a pet is created in this way, you should get a package_name.files that lists all of the files. These files could be used in Pet-be-gone. We could even keep them in a small repository to save space.
This brings up another point. It would be nice if .pet posts also had the CFLAGs, CXXFLAGs, LDFLAGs and ./configure settings used (where applicable) and package database entry... otherwise I will probably end up recompiling it. I will probably do the same thing if the packages aren't split into DEV, DOC and NLS as well. This is mainly a quality control issue and a quick pet for testing is still fine for submission, but if you spend hours tweaking the perfect combo of FLAGs and hand editing the makefiles or something please let me know. I just don't want to end up having a devx docx or nls sfs that is missing stuff, packages that are missing dependency lists or bloated/broken packages Publishing the flags and setting will allow others to reproduce the package if a new version comes out and you are busy. I will try to address most of these with Pcompile as it progresses, but if all of this sounds like a foreign language to you, don't be afraid to post a pet, suggestions or feedback.
This brings up another point. It would be nice if .pet posts also had the CFLAGs, CXXFLAGs, LDFLAGs and ./configure settings used (where applicable) and package database entry... otherwise I will probably end up recompiling it. I will probably do the same thing if the packages aren't split into DEV, DOC and NLS as well. This is mainly a quality control issue and a quick pet for testing is still fine for submission, but if you spend hours tweaking the perfect combo of FLAGs and hand editing the makefiles or something please let me know. I just don't want to end up having a devx docx or nls sfs that is missing stuff, packages that are missing dependency lists or bloated/broken packages Publishing the flags and setting will allow others to reproduce the package if a new version comes out and you are busy. I will try to address most of these with Pcompile as it progresses, but if all of this sounds like a foreign language to you, don't be afraid to post a pet, suggestions or feedback.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
- esmourguit
- Posts: 1410
- Joined: Fri 17 Nov 2006, 14:45
- Location: Entre l'ile aux oiseaux.et l'ile de sainte Lucie
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
That could be a good job for youesmourguit wrote:Bonjour à tous,
What about localizing scripts like xorgwizard, chooselocale etc.?
Cordialement
If you started with French, maybe others could follow your lead after and use your examples.
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
O common, not again. How much longer can Puppy be blind to the real world? Please have a look at how the bigger Linux distros are handling localization. There have been truly heroic Puppy-translators, like MU, esmourguit, magerlab, hacao and many others, but just how long can a human being continue that kind of endless work?ttuuxxx wrote:That could be a good job for youesmourguit wrote:Bonjour à tous,
What about localizing scripts like xorgwizard, chooselocale etc.?
Cordialement
If you started with French, maybe others could follow your lead after and use your examples.
ttuuxxx
What's needed, yes I said it before, is a standardized, unified, teamwork-enabling localization system.
To return to Technosaurus's topic, I was very pleased to see this as the first point on his wishlist:
Yes, dynamic sfs mounting, a dream come true. I do not understand what the "symlink style" means, but if it works as well as choicepup, I'm a happy end-userOn the fly sfs mounting: Choicepup style or symlink style
Thanks to all of you great guys!
[url=http://pupsearch.weebly.com/][img]http://pupsearch.weebly.com/uploads/7/4/6/4/7464374/125791.gif[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]