Hi, Bernhard-
I think that's a very interesting point, and a strong use case. I don't know
that it should be in SVG, though. That being said, I *do* think that the
mechanism for doing so should be specified in SVG.
Since what you're talking about deals with direct access to hardware, I
think the WG will need to be very careful in how they handle it. While the
other 3 hardware addressable inputs (mouse, keyboard, clock) are pretty well
established on PCs, and are talked about in DOM3 (from which SVG inherits),
inputs on mobiles are all pretty non-standard, from what I understand. Also,
not all devices will have GPS.
I think some other WG should deal with these issues (nonstandard keyboards,
pointing devices, GPS units), and that the SVG WG should merely provide an
interface whereby such attributes can be accessed in a generic fashion. This
is akin to SVG's relationship with DOM (which, sadly, no longer has an
active WG).
One way that I can think of to address this somewhat cleanly and generically
(I think... I haven't thought much about it) is socket access to a
Distributed DOM, where a GPS device (or another client, such as a
whiteboard) would change some properties of an XML element, in its own
namespace, and the SVG could import that automagically and throw a mutation
event when it changes.
Perhaps the W3C should have a WG or Task Force that specifically addresses
the needs of mobile devices, similar to DOM, and which also integrates other
W3C Specs, such as VoiceXML.
Regards-
Doug
doug . schepers @ vectoreal.com
www.vectoreal.com ...for scalable solutions.
Bz wrote:
|
| Hi all
|
| If people talk about Tiny SVG they also talk about:
|
| o SVG for Mobil Phones und PDAs
| o Location based Services
| o Map Applications (Navigation Systems)
|
| There are already Mobile Phones with build in GPS Modules.
| There are also Bluetooth GPS devices with the ability to
| connect to mobile Phones.
|
| ------------------------
|
| Examples:
| http://shopping.lycos.de/7904de20165247046.html
| http://www.garmin.at/Produkte/navtalk/navtalk_allg.htm
| http://www.kelkoo.de/b/a/ss_gps_-pda.html
| ...
| ------------------------
|
| The thing I'm missing is:
| ---------------start-----------------------
| evt.gpsLong //similar to evt.clientX
| evt.gpsLat //similar to evt.clientY
|
| onGPSmove //similar to onMouseMove
|
| ---------------stop-----------------------
|
| The user should have the possibility to deny access to GPS
| Data (similar to deny Cookies)
|
| thanks for reading
|
| Bernhard Zwischenbrugger
| http://www.fh-stpoelten.ac.at
|