What is it?

Motosu is a taskbar, with some extended functionality added.

Background

Before anything else, let me get this out of the way: I am a big fan of Taskbar by Jo Even Skarstein and I will not deny that is has inspired more than one aspect of how Motosu is put together.
When Taskbar arrived, it was a game changer in how I used my Atari. Slightly due to the start menu with its features but even more so in how I could suddenly access and control
the applications running. The way that I could interact with applications had suddenly turned a thousand times more intuitive than having to resort to the cumbersome application list in the desk menu.

So why writing another taskbar? Well I was working on some unrelated code that involved logging temperature readings from wireless sensors and started thinking that it would be 
pretty nifty to be able to display the results somewhere. I then started toying with coding ideas on how to keep track of running processes as a proof of concept - and over time it all just
snowballed into a project of its own.

In order to define some kind of place/object where I could display sensor data and similar, I came up with the concept of "tray items". Much like the notification area in the taskbar of Windows, 
the area to the left of the system clock is now reserved for applications that wish to display certain information within a dedicated container labelled Tray item. This new area of display consists
of an icon + two display areas. The display areas can be used to draw a level meter, display text or both. 


What do I need to run it?

I am basically creating a system utility tailor made to suit my own needs, hence the look and feel as well as the system requirements will naturally reflect my setup and how I use my Atari.
Rather than aiming for maximum compatibility with every system combination imaginable, I decided in a fairly early stage of development that I want to use a different approach.
The idea is to take advantage of any OS/AES function that makes it easier to get the desired results - distinctly targetting and encouraging the extended functionality of the AES's that kept evolving beyond the scope of Atari themselves. 
Motosu relies heavily on a number of MiNT kernel function to keep track of things and thus has been written with MiNT in mind from day one. For client interaction, shared memory is also a requirement.

When it comes to Geneva I have sadly decided that it is missing too many of the crucial functions to be easily supported. As for MagiC, I would expect it to potentially have fewer incompatibilities since it shares quite a few of the more
advanced functions with MiNT. However, already from the start I decided that I would much rather spend more time developing the application further than regularly checking for compatibility with MagiC. 

As far as the AES is concerned, the situation is similar - while I could produce a detailed list of functions that 
needs to be present, you are realistically facing the choice between XaAES and N.AES.



Motosu is being developed mainly on a Falcon/CT60@100mhz with 14+512mB but I am making efforts not to resort to unefficient solutions in my code.




What do you need?

	* TOS compatible machine 

	* FreeMiNT + AES (Motosu is developed on XaAES)

	* AV-server (Thing is recommended)

	* 

Supported additions
	
	* NVDI5.03 + Lp's image modules


	* Shutdown app

	* Finder app



