Hi peebee,
Thanks for testing the new PupMenu.
I installed LxPupSc-17.08.1T-k64.iso (manual frugal install) and then installed the PupMenu-6.0.pet, allowing the pinstall script to run. After testing, I created another frugal install of LxPupSc and installed the PupMenu-6.0.pet without running the pinstall script.
In both installations, the Icon Viewer button of PupMenuEdit works fine for me (see attached image). Of course, when you first open the File tab of PupMenuEdit, the icon viewer is inactive until you click on a menu item, at which time the icon of that item should be displayed in the viewer. If this does not work for you, maybe I can test further.
I'm also getting items put into the pcmanfm bookmarks that I'm not expecting... see screenie.
See /usr/local/PupMenu/PM-Edit, lines 544-552. My reason for adding these common icon directories to /root/.gtk-bookmarks was to expedite the search for appropriate icons when using the Icon selector button of the Edit tab in PupMenuEdit. However, if you prefer, commenting lines 544-552 should prevent this behavior.
And I have a suggestion - PupMenu currently puts multiple items into the Utility menu - I think I'd prefer just one item in the Desktop menu as I think you can get to all the other components using PupMenu as the "master" - am I right in this assumption? I can make this change locally in my build without disturbing your .pet .....
Yes, I think would be correct.
I notice that there is quite a big pinstall.sh in the .pet that doesn't get run in a woof-ce install - are there any implications to watch out for?
Yes, the 'Recent Files' button of PupMenu calls a script which utilizes a basic Perl function that requires the Escape.pm extension. Unfortunately, the standard cut-down Perl of Puppy does not include Escape.pm, so it must be added.
It seems the location of built-in Perl extensions varies in different Pups. The pinstall script of PupMenu will check the current location of perl extensions for the host Puppy, then install Escape.pm and create the companion URI folder. For example, in LxPupSc the pertinent built-in perl extensions reside in /usr/share/perl5. So, in this scenario, the Escape.pm extension is copied to /usr/share/perl5, and Escape.pm is symlinked to /usr/share/perl5/URI (ln -sf /usr/share/perl5/Escape.pm /usr/share/perl5/URI). On the other hand, in debian/ubuntu based pups the pertinent built-in perl extensions are in the /usr/lib/perl/5.* directory. See the pinstall script, lines 19-22 for recent pups based on slackware, or lines 15-18 for debian/ubuntu pups.
I included the above code in the pinstall script for conventional installations of the PupMenu pet, but not for Woof installations where it might have consequences unknown to me.
Thanks peebee for considering PupMenu for LxPup.
[color=blue][b][url=http://www.smokey01.com/radky/PupMates.html]PupMates[/url][/b][/color]