Bruno Tavares wrote:
> <snip>
>> And we can also remove the bad hacked network interface, you can send
>> events directly to Freevo:
>> app->Freevo: Button 'DISPLAY' is pressed
>> or
>> app->Freevo: Event(OSD_MESSAGE, arg='hi')
>
> Erms.. not so sure about this.. do you really want to introduce the
> communication overhead for this kind of events?
> Mbus sounds great to communicate with external helper, but it seems a
> little bit inefficient to spread all kind of events to OSD or from
> critical helpers such as mplayer.
> But i don't know, some benchmarking should speak for itself.
Yes, it is a bad example. I was thinking about the bad hacked remote
gui for Freevo. But I guess we won't need that anymore. Or does anyone
use this? For the Event() stuff, yes, it also makes no sense because
the app doesn't know the context Freevo is it. It should only
demonstrate that apps can display a message. But better commands will
be
freevo.message("hi")
freevo.play("/path/to/file")
Dischi
--
The three R's of Microsoft support: Retry, Reboot, Reinstall.
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
