PPM2

[bigpup]

The changes are the items listed between V1.9.6 and v1.9.7

mavrothal lists the changes first and than the version those changes are in.

The norm is usually state the version and than list the changes in it.

mavrothal,

Thanks for the additional work on PPM2.
The tweaking you are now doing is just making it better and better!!!!!!

[mavrothal]

mavrothal lists the changes first and than the version those changes are in.

This is basically the git log.

Code: Select all

git log -10 --reverse --pretty=format:"%h - %s"

So when I think that are changes that allow/warrant a change in version number, I do one more change for the version number and that's the last entry in the git log.
I could have it not-reversed with the last change on top, but then you should read from bottom to top...

[mavrothal]

That's it! PPM2 is out
See first post.

Last chance for testing!
My local woof-CE repo already has these changes and by Monday I reckon will be in github too for the future Puppy woof builds.

[MochiMoppel]

Last chance for testing!

So then here is my last appeal to remove these unnecessary and obstructive changes in installpkg.sh.

Please remove these 2

Code: Select all

dialog --msgbox "$(gettext 'Sorry, bla bla ,Aborting.')" 0 0 

constructs. If for reasons beyond me you really, really find this a good idea (so far you adamantly ignored my requests for an explanation) then add a timeout.. This would allow scripts to move on and prevent - in worst case - freezing of the system (yes, happened to me. I'm not posting this for fun).

[mavrothal]

Last chance for testing!

So then here is my last appeal to remove these unnecessary and obstructive changes in installpkg.sh.

Please remove these 2

Code: Select all

dialog --msgbox "$(gettext 'Sorry, bla bla ,Aborting.')" 0 0 

constructs. If for reasons beyond me you really, really find this a good idea (so far you adamantly ignored my requests for an explanation) then add a timeout.. This would allow scripts to move on and prevent - in worst case - freezing of the system (yes, happened to me. I'm not posting this for fun).

The dialog messages are in complete analogy to the gtkdialog messages.
I could find no problem with them when in use, ie when using petget from console (no X), and I have a hard time seeing how a yes-no dialog or a message box dialog can freeze the system, but I may very well have missed something.
Please provide a use case where I can reproduce the "system freeze"
Please be as detailed as possible so I can understand and possibly fix the issue.
Thanks.

[Jasper]

From the second paragraph of the opening post

The major feature of the new PPM is that it can install or remove simultaneously many packages and their dependencies without any further user input. "With just 1 click".

I run in PupMode 77 and even if "simultaneusly" [rather than sequentially] is a true description - what I actually want [personally - because I have limited resources] is the option to be able to make an on-the-fly change to download to a directory of my choice and the convenience of the option to keep pets after installation.

MochiMoppel used these in his own ppm code and he was a strong advocate of such obviously beneficial features in PPM2, but it took many weeks and a needless request for confirmation before it was adopted here (though, even then, in a less than ideal manner).

Now MochiMoppel advocates more change - the obvious advice is to investigate his advice thoroughly - don't .........

[rcrsn51]

don't .........

Another obscure ellipsis. I have no idea what that statement means.

[mavrothal]

From the second paragraph of the opening post

The major feature of the new PPM is that it can install or remove simultaneously many packages and their dependencies without any further user input. "With just 1 click".

I run in PupMode 77 and even if "simultaneusly" [rather than sequentially] is a true description - what I actually want [personally - because I have limited resources] is the option to be able to make an on-the-fly change to download to a directory of my choice and the convenience of the option to keep pets after installation.

MochiMoppel used these in his own ppm code and he was a strong advocate of such obviously beneficial features in PPM2, but it took many weeks and a needless request for confirmation before it was adopted here (though, even then, in a less than ideal manner).

Now MochiMoppel advocates more change - the obvious advice is to investigate his advice thoroughly - don't .........

The beauty of Puppy and Open source in general, is that everyone is free to use whatever he/she sees fit for their needs.

Regarding the download folder implementation in PPM2 is based on my ppm_down_dir-9.pet of Dec 2 and I have said since mid December that after we stabilise the new UI and functions, it will be considered, as it did.

Regarding MochiMoppel's suggestion, I'm open to MM's and anyone's suggestion really. If you noticed I already asked for specific input and hopefully we'll get it. However, I'm sure that MM is old enough to speak for himself

[slavvo67]

Mav,

I appeal to you to consider Mochi's request. He is quite knowledgeable (as are you) and has been quite helpful on the board. Perhaps he found something that needs a little tweaking.

PS - I know he's old enough to defend himself or discuss intelligently. He may be just too busy to follow-up on this.

Thanks for the consideration and the great update to PPM.

Slavvo67

[mavrothal]

I know he's old enough to defend himself or discuss intelligently. He may be just too busy to follow-up on this.

I do not think that has anything to "defend"
He reported that some specific lines freezes the system. I can not see that and no-one else reported such an issue.
I would like to know the conditions where the said freeze is induced before changing/deleting the said lines.
In the current setup if a package is already installed and the user "forces" or "tricks" or somehow manages to get it to be reinstalled (and of course fails), will be reported as "failed to be installed".
Deleting these lines, the user will have no idea why the package failed to be installed.
There are ways around it, but before we try to work it out we must first know what the real problem is. No?
I said Sunday but an extra day is not a problem.

[666philb]

feature request.

I would like the search field to 'auto clear' on mouse over, like in the new pfind. would make it middle click friendly.

[mavrothal]

feature request.

I would like the search field to 'auto clear' on mouse over, like in the new pfind. would make it middle click friendly.

In pFind this is done only for the original text, "Search text", which in PPM2 does not exist. So middle click can be used fine.
To do it for any string would generate more problems than solution as if you try for example to correct your entry by moving the cursor with the mouse to another point would erase everything and you would have to retype it.
I guess this is the reason that Zig does not implement this for any string in pFind too.

[MochiMoppel]

I could find no problem with them ..<snip>... Please be as detailed as possible

Here we go again. You made the change and you must have had a reason for it, but you still don't explain why you did it. I don't know how often you want me to explain basic functionality of console programs, but before I do so - again - and in more detail I need to know the reason behind your change and why you think that the new solution is better than the old one. I'm still waiting for an answer.

[mavrothal]

I could find no problem with them ..<snip>... Please be as detailed as possible

Here we go again. You made the change and you must have had a reason for it, but you still don't explain why you did it. I don't know how often you want me to explain basic functionality of console programs, but before I do so - again - and in more detail I need to know the reason behind your change and why you think that the new solution is better than the old one. I'm still waiting for an answer.

Let me try once more!
I did not add these warnings.
When I modified petget to work from console again, some gtk/pup-dialog warnings were made to work also in console via dialog, because a simple echo message is easy to miss among other console output. There is no "old solution" because before petget was not working from console. What was there was a relic from the era that petget was an installation script serving as a rudimentary "package manager", and was never changed.
Warnings and info are important and consistent with puppy culture of informing the user about what is going on. I can understand that you may or may not like/prefer that this info is showing in this way during console use too, and we could discuss it at some point latter.
However, what is really important to find out before anything else, is if and under which conditions these dialogues freeze the system as you said.
So once more, please describe the setting where you get the system freeze. What do you try to do with PPM2 when this happens?
Thanks.

BTW is hard to understand why an "explanation" from me on the reasoning behind the use of the dialogues in console, is a prerequisite for the description of the freeze you said you had. If it really freezes the system, is a bug and regardless of any reasoning behind the dialogue use, should be fixed first. So please describe the "freeze" settings.

[666philb]

feature request.

I would like the search field to 'auto clear' on mouse over, like in the new pfind. would make it middle click friendly.

In pFind this is done only for the original text, "Search text", which in PPM2 does not exist. So middle click can be used fine.
To do it for any string would generate more problems than solution as if you try for example to correct your entry by moving the cursor with the mouse to another point would erase everything and you would have to retype it.
I guess this is the reason that Zig does not implement this for any string in pFind too.

what about a button to clear the field then?

[mavrothal]

feature request.

I would like the search field to 'auto clear' on mouse over, like in the new pfind. would make it middle click friendly.

In pFind this is done only for the original text, "Search text", which in PPM2 does not exist. So middle click can be used fine.
To do it for any string would generate more problems than solution as if you try for example to correct your entry by moving the cursor with the mouse to another point would erase everything and you would have to retype it.
I guess this is the reason that Zig does not implement this for any string in pFind too.

what about a button to clear the field then?

I would rather not.
I think that another button there would be unnecessarily confusing and I do not think I have seen this in any other app, gtkdialog or not. I think you can always delete first and drag-select after if you are to middle-click in the field.
Another option would be to delete the entry after the search is done, but maybe some people want to search again say after the first installation of "music player"
Anyway, if anyone provides a patch for one or the other, I would certainly consider it.
Pock Zigbert

[666philb]

it's not that confusing.... see the clearfields addon for firefox & palemoon https://addons.mozilla.org/en-us/firefo ... ar-fields/

it's just a very handy feature. at the moment i inevitably already have the middle click primed and end up pasting it after whatever's already in the search field and then deleting the unwanted item.

all those wasted clicks

[mavrothal]

it's not that confusing.... see the clearfields addon for firefox & palemoon https://addons.mozilla.org/en-us/firefo ... ar-fields/

I avoid addons
I'm not sure if gtkdialog can do that (gtkdialog-experts please suggest)
The patch below clears the field and shows as in the picture (which I find ugly'sh)

Code: Select all

--- a/usr/local/petget/pkg_chooser.sh	2015-03-09 12:47:51.703307914 +0200
+++ b/usr/local/petget/pkg_chooser.sh	2015-03-09 14:59:12.820006982 +0200
@@ -458,7 +429,7 @@
       
         <text space-expand="true" space-fill="true"><label>""</label></text>
 
-        <entry width-request="80" activates-default="true" is-focus="true" secondary-icon-stock="gtk-find">
+        <entry width-request="80" activates-default="true" is-focus="true" primary-icon-stock="gtk-close" secondary-icon-stock="gtk-find">
           <variable>ENTRY1</variable>
           <action signal="activate">/usr/local/petget/findnames.sh all</action>
           <action signal="activate">refresh:TREE1</action>
@@ -466,6 +437,7 @@
           <action signal="secondary-icon-release">/usr/local/petget/findnames.sh all</action>
           <action signal="secondary-icon-release">refresh:TREE1</action>
           <action signal="secondary-icon-release">/usr/local/petget/show_installed_version_diffs.sh & </action>
+          <action signal="primary-icon-release">clear:ENTRY1</action>
         </entry>
       
         <text space-expand="true" space-fill="true"><label>""</label></text>

[666philb]

perfect!

thankyou

[mavrothal]

PPM2 is now in the testing branch woof-CE.

The updated pet (v2 not v2.0) in the first post has what is actually in woof-CE now and hopefully soon, in a puppy near you.

PPM bugs, for PPM2 or the original, can still be reported here.