Fatdog64 Contributed Packages and SFS

[ETP]

@ The Fatdog Team,

Thanks for Fatdog64-810 Final [17 Jan 2020]

Whilst testing it booted via "Super GRUB2 Disk" [SG2D] I made a couple of videos & created some packages.

The 2 videos can be found here:

https://photos.app.goo.gl/dbpcP44LkMDJgePp9

The packages are a streamed TV Panel & a version of my (TTS) multilingual startup welcome alert/ Internet alarm package.

They can be found here:

https://drive.google.com/drive/folders/ ... 4P7193UYVL

The TV Panel requires the installation of mpv using Gslapt.

Two AU channels are included.

If outside the UK, just ignore the 4 BBC channels on the top row unless you have a UK based VPN that will give you at least 10Mbps.

You should be able to access SKY UK at the bottom left & the rest of the icons.

The AU ABC channel is old fashioned & takes several second to launch. SKY AU works fine here in the UK.

You will find the TV panel on the desktop menu together with it's boot toggle switch.

Download all items then right click each in turn and select "Install Package"

The translate-shell package is required by the multilingual startup_welcome_alert package.

Having installed those 2 packages you will need to reboot twice to activate the spoken greeting.

Some MPV Tips:

# To quit the TV press keyboard letter q
# To resume later at the same position when viewing a film or video, use instead keyboard letter Q (Upper case)
# To toggle between windowed & full-screen mode press keyboard letter f (Or a fast double left click of the rodent)
# Use numbers 0 (up) and 9 (down) across the top of the keyboard to adjust volume.
# To take a screenshot press keyboard letter s
# Toggle visibility of subtitles (when available) with keyboard letter v
# To pause or resume play use keyboard letter p or the space bar.

Plus in the version of mpv in Fatdog [shift + i] will toggle on screen stream stats.

[ETP]

An easy practical implementation for Fatdog-810 Final [17 Jan 2020]

@ The Fatdog Team,

I posted here http://murga-linux.com/puppy/viewtopic. ... 82#1050582

about a DLNA Pet & Repository image for Bionicpup64 8.0. I see no reason why Fatdog should be

left out in the cold so am attaching a modified package of that pet suitable for Fatdog.

The same repository image referenced in that post must be used with this package together with the

instructions for download, placement and writing the extracted image to a USB2 stick.

The compressed repository image [70MB] & it's md5sum can be found here:

https://drive.google.com/drive/folders/ ... sp=sharing

N/B Use Gslapt to install minidlna as in the shot below and in Fatdog64 Service Manager do NOT

tick the minidlna service item.

Enjoy

[ETP]

Please see previous post

Six additional test videos together with their associated icons
for the repository stick are available from the following share:

https://my.pcloud.com/publink/show?code ... PPOS6oYU6X

EDIT 02/03/20:
Now 11 additional test videos in share.

[step]

Zoom client for Linux repackaged as an SFS for Fatdog64 >>here.

[step]

The pointerpointer tool for Zoom.

[step]

A couple of options for Abiword in Fatdog64-810:
http://murga-linux.com/puppy/viewtopic.php?p=1023684#1023684
http://murga-linux.com/puppy/viewtopic.php?t=118549

[dr. Dan]

Greetings all,
I've wanted to get more information from the battery icon in the tray for a long time, so I started adding to the fatdog-battery-applet.sh script to make it more to my liking. I don't know that much about shell scripting, but I know more now than before. The script attached below seems to work fairly well. I've tried it on Dell, Gateway/Acer, HP, and Toshiba laptops. I'd appreciate any additional brand-based evaluation.

The script wants configuration files lowbatt, criticalbatt and shutdown in ~/.config/battery_level/, and refers to an as-yet-nonexistant fatdog-power-settings.sh which I envision as being able to set a variety of battery and power usage parameters. Since it doesn't yet exist, sit ignores it.

The code could be more elegant, and I plan to improve it, or incorporate any suggestions I receive, over time. For example, I'll eventually want to simplify the tooltip section, perhaps use a single configuration file, and improve the battery health presentation.

If it is successful and practical, it could be packaged with preset parameters in the appropriate locations, but I haven't figured that bit out yet.

Any feedback is appreciated.

Dan

[step]

Dan, you have a good plan in mind. I can give you some feedback and hopefully someone else will add more.
In the interest of keeping this long thread right on its topic please consider opening a new thread focused on discussing the battery script.

I would change your modifications between the lines that start with ACTION= and BATTERY_SVG= as follows

Code: Select all

 LOWBATT=15 CRITICALBATT=5 SHUTDOWN=2
 LOWBATT_ACTION='batt-low.sh low'
 CRITICALBATT_ACTION='batt-low.sh critical'  # dr. Dan
 CLICK_ACTION="Xdialog --left --title \"Battery Info\" --msgbox \"\$(cat $POWER_PATH/*/uevent | sed 's/=/:    /')\" 0 0"
 RIGHT_CLICK_ACTION="fatdog-power-settings.sh" # configuration GUI
 [ -e /etc/battery.conf ] && . /etc/battery.conf # configuration
 [ -e $FATDOG_STATE_DIR/battery.conf ] && . $FATDOG_STATE_DIR/battery.conf # user overrides --dr. Dan
 

This is a "standard" way to add user overrides to the system configuration.
1) Provide in-script defaults. That's LOWBATT=15 ...
2) Read system configuration. . /etc/battery.conf
3) Read user overrides to the system configuration. . $FATDOG_STATE_DIR/battery.conf
I replaced ~/.config/battery_level/ with $FATDOG_STATE_DIR/ because $FATDOG_STATE_DIR is guaranteed to exist and it's where fatdog-bla-bla.sh (system) scripts normally expect to find user configuration files. This is preferred Fatdog64 usage, not policy. You can use ~/.config/some_dir even in this case, if you prefer. And you should for non-Fatdog64-system scripts. In that case I would write this stanza:

Code: Select all

 USER_CONFIG=${XDG_CONFIG_HOME:-$HOME/.config}/battery_level
 mkdir -p "${USER_CONFIG%/*}"
 

which ensures Desktop.org (XDG) compliance and creates the path if needed. On well-configured systems, you can simplify to

Code: Select all

 USER_CONFIG=$HOME/.config/battery_level/battery.conf
 mkdir -p "${USER_CONFIG%/*}"
 

I noticed several lines that follow this pattern:

Code: Select all

 variable=$(cat /path/to/file | head -n 1 2>/dev/null)
 

This can almost always be improved to another pattern:

Code: Select all

 unset variable  # or set it to a default value
 [ -s /path/to/file ] && read variable < /path/to/file
 

This code runs entirely inside the shell without starting external programs. It's faster and less error-prone.

[dr. Dan]

Thank you step, I'll look into all of that. If you compare this to the original, you'll see how dependent I have been of the original. The technical details will help in other efforts as well.

Dan

[step]

Thank you step, I'll look into all of that. If you compare this to the original, you'll see how dependent I have been of the original.

That's a good thing. After all, the original script is battle-tested, something to leverage.

[don570]

designed for recording a radio broadcast...
rewritten to kill arecord properly

download
23k
baconrecorder-5.0-x86_64.txz


https://drive.google.com/open?id=1-SGyO ... 4jLqbgR92r
--------------------------------------------

[jake29]

Here is the latest Nvidia Proprietary Driver (440.82), compatible with Kernel 4.19.92. Seems to work fine for me.

Filename: nvidia-440.82-810.sfs
File Size: 167mb
Download: google drive