There was something else that I wanted HelpSurfer to be able to do: execute local executables.
This is not a web browser, it is a local help viewer, so I can justify doing things that would be unacceptable in a browser.
Although it is not legitimate html, HelpSurfer 0.3 supports hyperlinks to
<a href="exec:leafpad /usr/share/doc/home.htm">EXECUTE LEAFPAD</a>
I have a requirement for this feature.
Announced on the Puppy Forum, with source and PET links:
No comments With Quirky, at first bootup, QuickSetup displays, followed by 'welcome1stboot'. The latter is a window with some introductory information, such as about the desktop icons and tray applets, and links to further help.
In woof-CE, that welcome1stboot is a web page, in Quirky it is a binary executable (written in BaCon).
For Easy, I have created /usr/share/doc/easy/welcome.htm, and this now replaces welcome1stboot.
As easy has the lovely new HelpSurfer html viewer enhanced by SFR, this is used to view welcome.htm
Technical note: welcome.htm is launched from /usr/sbin/delayedrun, which in turn is launched from /root/.xinitrc when X starts up.
I used Google Translate to create welcome_de.htm, etc.. After the user has chosen a language in QuickSetup, delayedrun will look for a matching welcome_*.htm and if exists will launch it.
No comments Forum member tallboy posted about this, for Firefox:
SeaMonkey does the same thing, updates the session information every 15 seconds. This is only useful in case of a crash. Setting it to 15 seconds causes Flash memory to be pounded.
tallboy posted a link, with a fix. It can also be done by editing /root/.mozilla/*/seamonkey/prefs.js, this line will set it to 30 minutes update:
I reckon that I will modify my SM PET with this.
1 Comment The icon bar along the top of ROX-Filer file manager has a "Home" icon. Click that, and it takes you to /root.
In Quirky and Easy, I want to differentiate between the /root and the user's preferred working home. When I click the "Home" icon, I want to go to that alternative path.
This question has been asked a few times on the Puppy Forum, for example here:
I have created a patch for the source code, 09-rox-filer-easy-home.patch. hard-coded for the home path in Easy Linux.
The source that I am using for Quirky and Easy is:
And these patches have to be applied:
09-rox-filer-easy-home.patch really should be generalized to suit any desired home, so it will work in any pup, as my todo note here:
...if anyone wants to do that, go for it!
After patching, compile:
# ./ROX-Filer/AppRun --compile
Which will create 'ROX-Filer' executable, copy that to /usr/local/apps/ROX-Filer/, or where ever ROX is in your pup, then restart X.
2Comments I have received a request, how to compile SeaMonkey 2.48.
This is a useful read:
Get the 'hotfix.patch' from here:
This is what I did:
# patch -p1 < ../hotfix.patch
# EXTRA_FLAGS=" -fno-delete-null-pointer-checks -fno-lifetime-dse -fno-schedule-insns2"
# export CFLAGS+=$EXTRA_FLAGS
# export CXXFLAGS+=$EXTRA_FLAGS
# unset EXTRA_FLAGS
This is my mozconfig file. Note that I used system pixman, however pixman spits out error messages, non-fatal, but you might want to consider using SM's internal pixman library: "--disable-system-pixman"
I did not use system nspr and nss, as in Quirky 8.3 (based on Ububtu 16.04.2 DEBs) they are too old.
Here is 'mozconfig':
Just put 'mozconfig' into top-level of source code, then off you go:
# make -f client.mk
Before installing, if you already have /usr/lib/seamonkey-2.48 and seamonkey-devel-2.48, /usr/share/idl/seamonkey-2.48, and /usr/include/seamonkey-2.48, rename them to something else. then:
# make -f client.mk install
Make sure that /usr/lib/seamonkey is a symlink to seamonkey-2.48, and check that /usr/bin/seamonkey is a symlink to /usr/lib/seamonkey/seamonkey or /usr/lib/seamonkey-2.48/seamonkey
Then run "seamonkey".
Or, if you want to make a pet, use 'cp -a' to copy out all of those target directories, before running seamonkey (when seamonkey runs, it actually writes into /usr/lib/seamonkey-2.48, or at least it used to, so grab the pristine files before first run of seamonkey).
Tidy up: if creating a PET, good to use an existing PET, such as mine, as a template. Note, delete the dictionary files, as all pups have hunspell, and delete the 'modern' theme -- again, look in my PETs.
Get my PET from here:
If you have Quirky and maybe a very recent pup, it will have 'pet2dir' utility, so just do this to expand the PET to a folder:
# pet2dir seamonkey-2.48-xerus64.pet
If your pup does not have this utility, then do it this way, which will give an error message, but works:
# tar -xf seamonkey-2.48-xerus64.pet
Pages: ...       ...