Woof at Github

Message

bigpup · #141 Post by **bigpup** » Sun 08 Dec 2013, 03:51

entered in error.
Re-posted.

dancytron · #142 Post by **dancytron** » Sun 08 Dec 2013, 06:38

I'd add pupsaveconfig

http://www.murga-linux.com/puppy/viewtopic.php?t=60678

pup save hot backup

http://www.murga-linux.com/puppy/viewtopic.php?t=49999

mavrothal · #143 Post by **mavrothal** » Sun 08 Dec 2013, 06:40

bigpup wrote:I am posting this here so I can check the links.

Links to core Puppy programs that have active topics in Puppy forum.
These may have newer versions at any time.
......
Is this useful?

dancytron wrote:I'd add...

It does help (a bit). But is practically impossible for 1 or 2 persons (with real life obligations) to do the development, release puppies, keep up with 30-40 treads and mailing lists and test new pets with the current puppy builds.

(BK was retired with out of the home kids and still could not manage...)

I believe the best way (for you or any pet developers) is to get a free github account and just "raise in issue" in woof-CE, issues page.

1) Make sure that the latest version of the said pet/sfs is not in any of the http://distro.ibiblio.org/puppylinux/pet_packages-* repos (not if it is just not showing in the PPM of the pupplet that you are using)
2) Go to the woof-CE, issues page and rase an issue. ie "update my.pet from v3 to v4"
3) Mark it as an "enhancement" and provide the link to the relevant post with the updated/new pet.
NOT the link of the thread but the actual download post (clicking on the little icon left to "Posted:" on the upper left of the post will give you the exact link).
4) Would be very helpful to have verified that the said pet works correctly with the latest woof-CE build as things are changing fast these days. If not it may take some time before is included (if ever).
5) Finally would be helpful to indicate if an older version of this pet currently in the repo is depreciated (and should be removed) or which repo would the pet be appropriate for if not already in a repo.

- Pets that have shell/gtkdialog code are appropriate for Puppy-noarch..
- Pets with binary code that depends only in libraries found in all Puppies/Linux are good for the Puppy-common.
- (Real) distro-specific pets that will not work on other pupplets (ie slacko vs dpup) because they use a specific lib version go to the distro pets. Please make sure that you do not put common/noarch-type pets here just because an existing dependency may not be installed by default in a given pupplet. Just add the dependency in the specs file and place it in common/noarch

6) (Not necessary but helpful) provide a patch for the respective "Puppy-packages-..." file in woof-CE/woof-distro/

Please do not suggest pets that may be specific to non-woof puppies/distros (ie Fatdog, Saluki, Macpup etc) unless you have thoroughly tested that work fine with woof-CE pupplets and do not conflict/brake anything else.

So, please get a github account, follow the above guidelines and help so your (preferred) pet is up to date in the repos. Help to actually build puppy CE.

Deacon · #144 Post by **Deacon** » Sun 08 Dec 2013, 08:20

mavrothal wrote:
So, please get a github account, follow the above guidelines and help so your (preferred) pet is up to date in the repos. Help to actually build puppy CE.

Is it ok for an "I told you so" yet? (I really am going to end up unpopular here aren't I, I feel it)

EDIT: Ok the flashplayer thing, that's a real big thing with the young people and it seems to be a repo mismatch as it can never be found. See, I'm helpful.

mavrothal · #145 Post by **mavrothal** » Sun 08 Dec 2013, 08:56

Deacon wrote:
mavrothal wrote:
So, please get a github account, follow the above guidelines and help so your (preferred) pet is up to date in the repos. Help to actually build puppy CE.
Is it ok for an "I told you so" yet?

No is not, because I have no idea what are you referring to.

bigpup · #146 Post by **bigpup** » Sun 08 Dec 2013, 15:42

mavrothal,

How to keep the Woof-CE program repositories updated.

I understand, most of what you posted, about keeping program pets updated, in the repositories used to build a Puppy, with Woof- CE.

The list of Puppy forum links, to program topics.
All of these program pets are commonly used in every Puppy version. So all of them are actively in use, in most versions of Puppy.

Would be very helpful to have verified that the said pet works correctly with the latest woof-CE

That is basically what an alpha or beta version of a new Puppy version is.
Testing all the programs in it.
example:
Slacko testing (for 5.7)
Suppose to be made with the latest Woof-CE.

I agree with all of your statements.
Anyone that developed a program, that is commonly used in Puppy, should be doing these things.
Have fun making that happen.

I could see it working, very well, if the 35 or 40 program developers did what you stated.

No way could one person keep the Woof-CE repositories up to date.
Maybe a quick reference list, to the programs active forum topic, is the best answer to problem.

I, as only a user, would have trouble doing most of what you stated.
We all do this as a part time hobby!

pemasu · #147 Post by **pemasu** » Sun 08 Dec 2013, 16:01

Regarding woof compliant pets. The crucial thing is that if the pet uses pinstall.sh script, it needs to be woof compliant - for the desired effect to happen and for that woofing 3builddistro stage does not fail. 'exit' command at the end of the pinstall.sh script is disaster. It stops 3builddistro collective - cumulative - one and only pinstall.sh script to stop and the rest of the one and only cumulative pinstall.sh operations are not performed.

I usually notice this when woofing. Then I start to hunt that exit command.

Here is an example of one and only - woof 3builddistro created - pinstall.sh. It shows the ways to create woof compliant pinstall.sh. Main thing is to have './' ie current directory execution for woof compliance. Without that the pinstall.sh script is not processed inside rootfs-complete and the desired pinstall.sh effect is lost. Hmm... in good and bad. There are couple of ways how to create that current directory effect. Coders are clever. Cleverer than me.

Coders can say above in better words. I know the practical effect.

When woofing, during 3builddistro stage. You should see this message when the cumulative pinstall.sh has finished:

END OF pinstall.sh SCRIPT.
If you did not get 'End of pinstall.sh' message above, then
it aborted before completion. Press ENTER or CTRL-C

If you dont see it, one or more of those about 35 pinstall.sh scripts have been defective and you start to hunt that-those one-ones down by detective skills. How good Holmes you are ? It is great way to spend Sunday.

Here is example how to do pinstall.sh scripts - as cumulative one - as woof processes it. This one is from real life, and it should be ok. Inside that cumulative pinstall.sh is several examples to create woof compliant pinstall.sh script.

Ted Dog · #148 Post by **Ted Dog** » Sun 08 Dec 2013, 16:01

Another question is where is the T2 sources going to be located? Also where are the current versions hosted. If I recall the racy wary series are compiled from source.

mavrothal · #149 Post by **mavrothal** » Sun 08 Dec 2013, 17:17

bigpup wrote:
Would be very helpful to have verified that the said pet works correctly with the latest woof-CE
That is basically what an alpha or beta version of a new Puppy version is.
Testing all the programs in it.

Exactly. The programs already in the repository!
The new ones or updates of the existing ones?
So what I'm saying is, if you tested a newer version of say pmusic that works fine in the existing slacko 5.6.3 propose it in the issues list for inclusion in 5.6.4.

bigpup wrote:No way could one person keep the Woof-CE repositories up to date.

My point exactly! Imagine if that person has also to scout 40 threads for new pets or troubles related to them...

bigpup wrote:I, as only a user, would have trouble doing most of what you stated.
We all do this as a part time hobby!

Actually is exactly what you do now.
Log in a site and write some text with some links about pets that you tried and liked. Just a different site than this forum and a bit more structured so can be helpful to the persons that are doing the heavy lifting.
BTW, why did you remove your post with the pet links after getting to all the trouble to assemble it

Ted Dog wrote:Another question is where is the T2 sources going to be located?

This is up to the person that is doing the T2 builds. Currently this is BK and the sources are in bkhome.org/sources.

pemasu wrote:The crucial thing is that if the pet uses pinstall.sh script, it needs to be woof compliant

Valuable insight.
Do you have a list of misbehaving pets?

pemasu · #150 Post by **pemasu** » Sun 08 Dec 2013, 17:25

No. I dont have a list. But I know whose pets I inspect carefully.

I havent been that practical. But...I could try to remember to make a note, now on...

One pet I would like to see woof compliant is that rox right click pet maintained by don570. The pinstall.sh script in it has about 1000 rows, so...I havent started to do that.

mikeslr · #151 Post by **mikeslr** » Sun 08 Dec 2013, 17:41

Hi all,

Occasionally, when I think of it, I'll add to a web-browsing folder I called "packages" a link to a repo I've stumbled across. In no way is it complete. Absent, in particular, are all the links to pets posted in "Additional Software" with links other than to repos. Some of the links are to mirrors. Some may be broken, to repos no longer in existence which I haven't pruned from the list. And it may not be what you're looking for. But I've attached it. Hope it helps. Remove the false "zip" ending. Its a plain text file.

mikesLr

bigpup · #152 Post by **bigpup** » Sun 08 Dec 2013, 20:31

BTW, why did you remove your post with the pet links after getting to all the trouble to assemble it Confused Shocked

I did not remove it.

For some reason the text in that post stopped showing up after doing an edit.
I can bring it back up if I select the edit button.

Does anyone know what is happening here?

I must be hitting some kind of post length limit.

could have been this:

disappearing posts are usually the fault of a link - [url] - with a space in it at the end....

Anyway. That thing was getting kind of long.
Edit:
Deleted some of the entries and re-posted below.

bigpup · #153 Post by **bigpup** » Sun 08 Dec 2013, 20:33

bigpup · #154 Post by **bigpup** » Sun 08 Dec 2013, 20:38

No pets maintained

AbiWord
http://www.abisource.com/download

Asunder
http://littlesvr.ca/asunder/downloads.php

Geany
http://www.geany.org/Download/Releases

Gnome MPlayer
http://code.google.com/p/gnome-mplayer

Gnumeric
https://projects.gnome.org/gnumeric/downloads.shtml

Homebank
http://homebank.free.fr/downloads.php

osmo
http://sourceforge.net/projects/osmo-pim

Is this helpful?

bigpup · #155 Post by **bigpup** » Sun 08 Dec 2013, 21:01

I do not know about you guys.
But I am learning some stuff about supporting Woof-CE with usable programs.

bigpup · #156 Post by **bigpup** » Sun 08 Dec 2013, 21:20

pemasu wrote:No. I dont have a list. But I know whose pets I inspect carefully.
I havent been that practical. But...I could try to remember to make a note, now on...

One pet I would like to see woof compliant is that rox right click pet maintained by don570. The pinstall.sh script in it has about 1000 rows, so...I havent started to do that.

Just tried rox right click pet maintained by don570 in the test Woof-CE build of Slacko 5.7.
Worked for me OK.

At least my list made it easy to download and check the program.

Maybe we need a specific topic on programs to have available in the Woof-CE repository.

gcmartin · #157 Post by **gcmartin** » Fri 13 Dec 2013, 09:56

By now, many/most of this community, probably already has a smart device. These are characterized by a touch interface.

Microsoft rewrote Windows from the ground up to provide API and development guidance for its latest operating system (OS) releases. One of the primary ideas is about the behavior of the display's behavior when touched. In reality, when you step back and understand, they are really treating the touch as mouse button 1 (left-click) to launch action(s). While, also, honoring the industry standard of "long-pause", too. And there is other behavior subsequent also.

This community's distro developer, TaZoC, understood this behavior and chose, in his distro to do a simple change of mouse behavior on the desktop. In most every PUP, today, if you click mouse button 2, you will get a pop-up. He moved that pop-up function to mouse button 1 such that it allows ANYONE with a touch screen to navigate the PC by touching anywhere on an open area of the desktop. Also, the finger's touch has other behaviors that include how traditional mouse button1 behaves. Thus, a touch PC user, can manage much/most of desktop's activity with your finger.

So here's a thought that I ask distro developers of WOOF-CE to consider.

Would the overall community benefit from this simple change?
Since mouse button 1 does nothing for any user of most every PUP), Is there a known downside to making this change?

Please understand that this ONLY APPLIES TO MOUSE CLICKS ON OPEN AREAS OF THE DESKTOP. It does NOT apply or affect any other such as right-click utilities already in use in PUPs.

This does NOT address all of Touch use in Linux. But, it certainly gives a portion such that it advances usability in system's navigation. And a manipulaton at this level means all PUPs would benefit.

Here to help

01micko · #158 Post by **01micko** » Fri 13 Dec 2013, 13:15

gcmartin wrote:Microsoft rewrote Windows from the ground up to provide API and development guidance for its latest operating system (OS) releases. (bla, bla)

Bullshit.

gcmartin wrote:This community's distro developer, TaZoC, understood this behavior and chose, in his distro to do a simple change of mouse behavior on the desktop. In most every PUP, today, if you click mouse button 2, you will get a pop-up. He moved that pop-up function to mouse button 1 such that it allows ANYONE with a touch screen to navigate the PC by touching anywhere on an open area of the desktop. Also, the finger's touch has other behaviors that include how traditional mouse button1 behaves. Thus, a touch PC user, can manage much/most of desktop's activity with your finger.

So here's a thought that I ask distro developers of WOOF-CE to consider.
Would the overall community benefit from this simple change?
Since mouse button 1 does nothing for any user of most every PUP), Is there a known downside to making this change?

Ok.. where is the patch?

pemasu · #159 Post by **pemasu** » Fri 13 Dec 2013, 17:58

Microsoft rewrote Windows from the ground up to provide API and development guidance for its latest operating system (OS) releases. One of the primary ideas is about the behavior of the display's behavior when touched.

The incredibly poor usability of windows 8 touchpad friendliness was one of the reasons I removed it from my laptop....My 20 years old daughter ( win os 8 ) laptop user called me and asked where is Skype in her laptop !
She couldnt find it because of missing menu and incredibly useless touchpad friendly system to launch apps....read: it absolutely sucks !
I suggested her to use 'search' app...and she found it. So...if you know you have some app...use search...and it find the app and you can lauch it....and that is usability ?
Win 8 was really hard and crude economical driven forced push to gain share in tablet markets and it forced win 8 also as os in laptops.....where it does not belong...and nobody wanted it.
Market forces for tablets...and lousy one...nothing else.

Ted Dog · #160 Post by **Ted Dog** » Fri 13 Dec 2013, 20:13

win8 is bad win8.1 is worse.. now it takes 3 changes to get to a desktop the start button is a overlay and near worthless.
Videos are suspect if not MS typed. long pause before playing. And if you play a OTA HD TV capture in .ts format it writes the activity to protected files. requires you to attach to NST servers for actual time stamp sync of your activity.

Win8 hid non windows setup hardrive parts. On win8.1 it will display used linux parts as unformatted and prompts each time for reformation. One accidentally pressed mouse click and linux is now been assimilated in the borg collective of Win8.1

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Woof at Github

T2 Build sources

Urls to some package repos

Move desktop mouse controls from button 2 to button 1

Re: Move desktop mouse controls from button 2 to button 1