- From: Max Froumentin via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 18 Jan 2010 13:26:17 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/system-info
In directory hutz:/tmp/cvs-serv536
Modified Files:
Overview.html
Log Message:
change API root, following decisions recorded in ISSUE-44
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/system-info/Overview.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- Overview.html 18 Jan 2010 13:07:06 -0000 1.56
+++ Overview.html 18 Jan 2010 13:26:15 -0000 1.57
@@ -200,13 +200,23 @@
<p>This interface contains the functions that enable access to
the properties defined in the following sections. It is
- typically exposed on the <code>navigator.device</code> object,
- as defined in [[!CORE-DEVICE]].</p>
+ exposed on the <code>navigator.device</code> object, as
+ defined in [[!CORE-DEVICE]].</p>
-<p class="issue">The actual object of which the API will be hanging off is still under discussion (e.g. directly from <code>navigator</code> vs from <code>navigator.device</code>); see <a href="http://www.w3.org/2009/dap/track/issues/44">ISSUE-44: What do APIs hang off of?</a>?</p>
+ <p class='issue'>The actual object of which the API will be
+ hanging off is still under discussion
+ (e.g. <code>navigator.service</code> vs from
+ <code>navigator.device</code>); see <a
+ href="http://www.w3.org/2009/dap/track/issues/67">ISSUE-67</a></p>
+
+
+ <div class='idl' title='Service implements ServiceSystemInfo'></div>
+
+ <dl title="[NoInterfaceObject] interface ServiceSystemInfo" class="idl">
+ <dt>readonly attribute SystemInfo system</dt>
+ <dd>The root node from which the contacts functionality can be accessed.</dd>
+ </dl>
- <p class="issue">window.systeminfo.* instead? Pending WG decision. See <a href="http://www.w3.org/mid/355A518BC0575547B2A3D6773AAF8EEF73A1A0@ftrdmel1">thread</a></p>
-
<dl title='[NoInterfaceObject] interface SystemInfo' class='idl'>
<dt>PendingOp get(DOMString propertyId, SuccessCB successCallback, optional ErrorCB? errorCallback, optional Options options)</dt>
<dd>
@@ -427,7 +437,7 @@
<h4>ECMAScript Example</h4>
<pre class="sh_javascript example">// Alert the user when the power level is below 20%
-navigator.system.watch("Power",success,null,{lowThreshold:0.2});
+navigator.service.system.watch("Power",success,null,{lowThreshold:0.2});
function success(power) {
alert("Low battery level: "+power.level);
@@ -642,12 +652,12 @@
<h4>ECMAScript Example</h4>
<pre class="sh_javascript example">// If the temperature gets near the top, set all cooling devices to 1500 RPM
-navigator.system.watch("Thermal",
+navigator.service.system.watch("Thermal",
function() {
alert("Cooling system at more than 90% capacity. Engaging Fans");
- navigator.system.get("Cooling",function(cooling) {
+ navigator.service.system.get("Cooling",function(cooling) {
for (var i in cooling.devices)
- navigator.system.set("CoolingDevice",cooling.devices[i], {speed: 1500},null,null);
+ navigator.service.system.set("CoolingDevice",cooling.devices[i], {speed: 1500},null,null);
})
},
null,
@@ -717,14 +727,14 @@
<pre class="sh_javascript example">// Find if the system has a WiFi connection, if so monitor its signal
// First, find the first WiFi interface on the system
-navigator.system.get("Network",success,null);
+navigator.service.system.get("Network",success,null);
function success(connection) {
var nets = connection.availableConnections;
for (var i=0;i<nets.length;i++) {
if (nets[i].type===nets[i].TYPE_IEEE802_11) {
// we found a wifi connection, watch it
- navigator.system.watch("Connection",wifiWatchCB,null,{id: nets[i].id});
+ navigator.service.system.watch("Connection",wifiWatchCB,null,{id: nets[i].id});
}
}
}
Received on Monday, 18 January 2010 13:26:18 UTC