Hardware awareness

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

Hardware awareness
by Martin on Wednesday 15/Aug/2007, @23:23

I watched the video. A major portion of the magic here seems to come from awareness of connected devices. Could parts of that be merged into Solid?

Interestingly, a lot of the hardware information is provided by the user; which room is a particular light located in? Which port of the digital TV receiver is connected to which input of a particular TV set?

Related Links

·   Articles on Applications
·   Also by Martin
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Hardware awareness
by kwilliam on Thursday 16/Aug/2007, @08:39

Ooh! Ohh! Yes, can that become part of the Solid hardware framework? How hard would that be? It would be sweet if I could use cron jobs to control my house appliances!

[ Reply To This | View ]

Re: Hardware awareness
by Aaron J. Seigo on Thursday 16/Aug/2007, @09:14

they actually use a lot of the same tech that solid does, namely hal/dbus for many (though not all) of the hardware events. the "what to do with the device" after that is a large part of the value add. i'm not sure it's solid's place to set up application specific configuration files based on those events.

in any case, we will be exploring how to share more code in this area as hardware awareness is obviously an important part of both the media center and the desktop.

[ Reply To This | View ]

Re: Hardware awareness
by Martin on Thursday 16/Aug/2007, @12:19

There is a space between "what does this device look like according to HAL" and "what to do with this device". That is the user-supplied "meta data", of which I gave two examples, and this seems to be precisely where the magic happens.

If the Solid layer could incorporate the additional information that a particular light has "location: living room" and "role: decoration", then any application using Solid could with a little effort achieve the same level of magic as does LinuxMCE. So if the descriptional parts of whatever DigitalTVBox, IRSensor etc. classes are in LinuxMCE today could be merged into Solid that would be a great unification, possibly?

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I switch between vi and xemacs quite a lot. I'm happy with both." -- Simon Hausmann
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.