<br><br><div><span class="gmail_quote">On 11/30/06, <b class="gmail_sendername">Tim Newsom</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> the problem with doing it this way, is you'd need some way to notify<br>> each application of all the sensors available at runtime, or you<br>> re-compile each availability sensitive app for every combination of
<br>> sensors (having that many versions of software is sure to turn off<br>> Sean's dad) there's definately more to think about on this one<br><br>Are you thinking of not only notifying each application on the number of
<br>sensors.. (That would be easy enough in the api) but also to let them<br>have access to the setup/configure api for each one?<br><br>Enumerating over each sensor that is active would be fairly easy using<br>the plugin mechanism previously described... If every plugin had the
<br>same output ranges... Say 0 to 255 or whatever and using the probability<br>scenario he talked about the application would only need to know one<br>interface, I.e. Availability. As I understand the proposal, and I<br>
might be wrong, it would end up a heirarchy. Lower level plugins could<br>be accessed at any level but the common usage would be to build<br>behaviors going up from the sensors and applications would interface<br>with that... Is that right?
<br><br>With that in mind, each plugin would register with some service which<br>handles the interface to applications. Each behavior created would do<br>the same and gain access to the sensors available. Then a control panel
<br>could be created to enable/disable some but not all plugins at the will<br>of the user, though that would modify the behaviors, they would then act<br>on the information currently available.<br><br>Seems like a fairly interesting concept. Do I understand the concepts
<br>or am I missing something?<br><br>--Tim<br></blockquote></div>yeah, I'm still trying to understand Richard's concept. It sounds really efficient, therefore cool, but I'm missing stuff<br><br clear="all"><br>-- <br>--Jeff
<br>What DO you call whitewater when you live in the desert?