Re: [tuxdroid-user] How tuxes "see" each other?

[David B. <da...@ja...>]

On Wed, 21 Mar 2007 15:58:24 +0100, Florent THIERY <ft...@gm...>  
wrote:

>> Basically, you could have a manager on your computer for all stuff that
>> occurs there, but the waker should be on the manager running on the  
>> slug.
>> We still need an access to that manaer from the computer for  
>> configuration
>> but after it should be able to run alone.
>
> So the gui would be used ONLY for application
> setup/activation/options? Upon "OK", it stores the parameters and the
> execution will be scheduled in the aggregator?

Yes, for the aggregator running on the slug, we need something like this.  
For the aggregator running on the computer, it doesn't really matter.

I thought of having the manager (or aggregator) very light and which  
handles the configuration and priorities/routing. Then a set of plugins  
could be installed, each plugin offering a functionality for tux. On a  
slug, you could have a waker plugin, a wheather plugin and an email plugin  
for example. Configuration could be done through a gui or simply  
configuration files. If you get an email, pressing on the head would read  
the emil, but if tux was waking you up, pressing on the head would stop  
the alarm. And pressing on the head when no event occured would tell the  
wheather forecast. That's the manager that should be able to route these  
events between the daemon and the plugins.

That's maybe not the good way to implement it but basically managing  
different functionalities is the problem we'll have to solve in the  
future. And having a computer running continuously is not something we  
usually accept so being able to run the daemon and the 'manager' on a  
small box is really necessary.