B.K. Johnson wrote:@LazY Puppy
To make things persistent for a use in a T.O.P.L.E.S.S. LazY Puppy 5 there is currently only one possibility: editing the main sfs!
What is the name of the main sfs you speak of? I am making 2 puppies T.O.P.L.E.S.S.
There is only one main sfs for a Puppy - usually it starts with
puppy_. To make things persistent in both Puppies you'll need to edit them both: puppy_tahr_6.0.5.sfs and puppy_tahr64_6.0.5.sfs.
Menu=>Setup=>Puppy Package Manager
Type cursor_themes in the Search window. cursor_themes-1-1 appears, ready for download/install. Once installed, Menu=>Desktop=>Pcur and select the cursor you want. I use whitelarge.
Ok, thanks.
Name and location of 'main config' file, please.
What is the name of the main config file? Where is it located?
Those Files that I'm calling
main config and/or
sub config are
explained in this post. The post has two divisions (marked in
blue color) which has a partially underlined sub-title showing either
main config or
sub config.
The divisions content includes exact
(as much exact as I was able to do) description of how the names of these main and sub config files are defined (of course one needs to know what $DISTRO_FILE_PREFIX (e.g. tahr) and $DISTRO_VERSION (e.g. 6.0.5) will be set up to on a running Puppy.
May I ask you to offer some descriptions in EN that will be better than those descriptions I'm fighting with?
So, with the pet in InstallMe, what happens on boot? The pet is installed only for the current session!
Correct. It will install automatically. No need to confirm installation at all. Though there will be a message.
I want to use Seamonkey, I want to set up a menu item so I can launch Composer only. I want to use emelfm2 and tweak it so I can work efficiently. What's the recommended approach? Should the originals be converted to SFS. After being launched and configured to my needs, are they permanent or lost on the next reboot?
How to make things permanent/persistent is
explained in this post (probably too vague, not detailed enough).
I'm calling this:
Save settings back to T.O.P.L.E.S.S. System SFS Modules.
Ok, so the Seamonkey approach seems to be a good example to explain it using more details.
I assume there is Seamonkey existing as a .pet file.
Preparing the .pet package
(probably it's not necessary for some .pet packages, though I recommend it as it is a MUST at sometimes):
Copy the .pet file to a ext partition, right-click the .pet and choose Extract (or probably Extract .pet package (I'm in DE)). Go to the extracted .pet's location /usr/share/applications and load its .desktop file into a text editor. Check entry Categories= to make sure it will enter a Puppy Linux menu category. Check also entry Icon= to make sure its content (name of icon) will fit to either an icon already inside the system (like /usr/share/pixmaps, /usr/share/icons/hicolor/48x48/apps or /usr/local/lib/X11/pixmaps) or even to an icon at these locations inside of the extracted .pet package. If there is neither one choose a icon from somewhere, rename it or rename content of entry Icon= in .desktop file and put it (best: /usr/share/pixmaps AND /usr/share/icons/hicolor/48x48/apps) at these locations inside of the extracted .pet package. Where ever it's placed: don't symlink it back to the /usr/share/pixmaps directories.
If all done, right-click the .pet's extracted directory and choose
Create .pet package.
1. do right-click the new created .pet package and choose:
Convert to SFS P.L.U.S.
- a GUI may appear, if so
- - select the menu entry/entries (.desktop file/s, multiple selection possible) within the left list
- - no need to change settings
- - click Apply
- - just close the next dialogue
- the SFS will appear in /root (or probably at .pet's location?)
2. move that SFS to directory
Modules at boot partition
- this is the SFS Pool location from where the SFS P.L.U.S. RunScripts do load SFS Modules
3. open the Defaults Changer/Chooser
(near bottom of menu Default Apps)
- switch to the Tab for Internet etc.
- empty the entry for the default browser
- open /root/.my-sfs-scripts
- open the Seamonkey xxx.Scripts directory
- drag and drop the RunScript to the entry for the defaultbrowser
- update the default applications (click on Update)
- close the Defaults Changer GUI
4. go to menu SFS P.L.U.S.
- choose
Rebuild RunScripts SFS Module
- choose
Rebuild Default Apps SFS Module
That's it.
After doing a reboot you can execute Seamonkey from its menu entry or just by the browser (or internet?) icon at the desktop.
May I ask you again to offer some descriptions in EN that will be better than those descriptions I'm fighting with?
Now, something different, as
there seems to be also some confusion about my term RoxApp Directory for the T.O.P.L.E.S.S.
Really, nobody but me understands the term T.O.P.L.E.S.S. RoxApp Directory?
(Just hoping that's simply not true)
The Rox Application Directory (RoxApp Directory)
(A self contained application)
Re-packaging a program as an application directory
The simplest case is something like tgif where you just have an executable and a help file.
The steps would then be:
Create a directory called 'TGIF'
Move the executable inside as 'AppRun'
Put a PNG format icon inside as '.DirIcon'
Create a subdirectory called 'Help' and put the docs inside that
Optionally, create an AppInfo.xml file as explained in the filer's manual (this can be used to show a tooltip for the application, etc).
Yes, I know: when right-clicking such RoxApp Directory and choosing Properties it says Type = Application. Though, this is NOT an (usual) Application like binaries and/or scripts as this will show up just as a simple directory in every else file manager. Only the Rox desktop -which is partially used in Puppy- knows, that this directory is a Application Directory.
However, just to make sure: the
T.O.P.L.E.S.S. RoxApp Directory is different to directory
RoxApps (which is NOT a RoxApp Directory and which will be present also after converting to
T.O.P.L.E.S.S.).
Hope this is helpful...