Installation:

Make sure any GRP-files associated with the start menu are located at a path where Motosu will look for them. Motosu uses Thing groupfiles (*.GRP) to generate the start menu, and searches for INDEX.GRP in the following locations (in the order as listed below):
/$HOME/motosu/
/$HOME/
/$THINGDIR/
If not found in any of these, the workdir of Motosu will be searched as a last resort.
 
Where applicable, make sure the following environmental variables are set:
$HOME, $AVSERVER, $THINGDIR, $FONTSELECT, $FINDER, $SDMASTER.
 
A new environmental variable, $TAPIRSERVER (Tray and taskbar API Register) is established to point applications to Motosu if they wish to either change their appearance on the taskbar or create a tray object. To enable this functionality make sure to add the following to your setup:
$TAPIRSERVER="MOTOSU "
 
If XaAES is targetted you get a nice and slender appearance with the following app_options:
app_options = motosu, thinwork = true, xa_nomove = false, winframe_size = -1 (if not using textured background, you might like winframe_size = 0 better
 
Unzip the archive and run MOTOSU.PRG. When first launched, the program will try to write cache files for icons and (where applicable) background textures.
The cache files are written to subdirectories of /$HOME/motosu/cache/.
Motosu will save its configuration file to /$HOME/motosu/


Tray objects
============

It is still early days, so the only examples I have of the idea with tray objects are the following two:

1) TmpView		- A "dummy" tray object, only showing a static "made up" temperature reading

2) RAMses		- A view for free ST/TT-ram, showing results in the tray panel.

More to come, but hopefully this is enough to give a rough idea of what I am aiming for.


GokMasE  2020-2023

http://motosu.gokmase.com