Dirk Meyer wrote: > Mathias Weber wrote: >> Dirk Meyer wrote: >>> Mathias Weber wrote: >>>> What i'm not sure yet is where should i put it. I don't think it would >>>> fit into popcorn, since it only play tv broadcasts. But still I think it >>>> could be usefull for some other users than freevo, so we could put it >>>> under kaa and just write a new plugin for freevo. >>> kaa.base (or similar): basic ir send module >>> freevo.ui.tv.plugins: plugin using it for TV control >> I think the ir send module would fit into this, but what I have in mind >> is something more general. I would to have a module that not only >> supports ir for controlling an external device. It should be a generic >> control for external devices that support ir, rs232, bluetooth, ... > > kaa.base has an input section with lirc and keyboard. But hey only > share one directory, the interface is a bit different. So this could > also work for an output directory with different output driver. > > About bluetooth. I only know about bluez. There was a bad hacked > bluetooth plugin in kaa.base once and now it is in WIP. The reason for > this is that bluez is GPL and I don't want to make kaa.base GPL (it is > LGPL now) just because of that. Maybe kaa.bluez is a solution here. >
I think bluez is not the problem. The python bindings are GPL so they would give the GPL dependencie. But you are right. LGPL would be better for kaa.base. >>> I would like to have such a module, I need an IR sender first. My >>> problem is that with AC3 pass-thru you can't control the volume with >>> the Linux mixer. So I need an ir-send-mixer.py that would transform >>> freevo volume request into ir codes. >>> >> This is an other thing I would like to have as well. Because of this i >> would like to have a generic solution since I need for the switch >> between the freevo box and the tv also to switch the audio receiver to >> the right channel. >> >> Here some code what I have in mind. >> >> >> class DeviceController: >> def send_command(self, command): >> def load_config(self, config): >> >> >> This looks like something very simple. The commands would be strings. >> The configuration where to find its device, device specific >> configuration and the list of commands would be stored in the config. >> That could be loaded from a separate file or something different (I >> don't know yet). >> May be we would like some kind of factory for the specific types so we >> only need to now that we want to load a DeviceController with a given >> config. The factory would decide from the config file witch kind of >> DeviceController implementation it would need. >> In addition we could use the factory to send a command to all device not >> only one, could be used for the switch between tv and freevo box where i >> need to switch the audio receiver as well. >> >> What do you think? > > First we need the stuff in kaa. After that we see what kind of > interface we have and can think of the freevo part. Bluetooth for > example is much more powerfull than ir, I generic module won't work > without cutting some bluetooth functions. > > BTW: what kind of bluetooth output do you have in mind? > I don't think that we could give a full abstraction layer for bluetooth, for this is pybluez. What i have in mind is more an abstraction layer to control an external device trough what ever channel there is. I see it more like the popcorn interface for the different players as an interface for different external devices. That we only would have to send commands to a specific device on the freevo side, so we wouldn't have to care about IR, RS232, bluetooth,... Mathias ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
