[whatwg] Device Element

Nikita Eelen neelen at amvonet.com
Wed Dec 29 12:22:34 PST 2010

I agree with Seth and the others that promote the spec idea. If a
detailed spec is needed although I too do not have much experience in
writing them I would definitely give some of my time along with Seth
to writing one. The thing with html5 is how long the spec is going to
be in spec status and even then wide implementation is still quite a
bit of time away.

 If this is not going to be implemented you will have to either use
flash, or native code, or activeX whoever knows if that XUL comment is
true but if it is then it's the same problem of no standard. Heck svg
just this year started becoming standard with new browsers.
Considering google has native client does that mean in the future all
I have a choice over is flash + native client (google and all
desktops) or native code (all others) and based on the platform design
code natively? Sounds like the current times problem to me.

Anyone else coding a web application with camera/microphone access for
android, iOS, Winphone 7, blackberry, Mac and PC? Each with their own
flaws to do the same darn thing :(. It would be a lot easier if this
was the same don't you think?

Hope someone else out there maybe with experience can usher some
guidance and let me and Seth know how we can help with this spec?

Kind regards,

On Wednesday, December 29, 2010, Charles McCathieNevile
<chaals at opera.com> wrote:
> On Wed, 29 Dec 2010 01:44:09 +0100, Seth Brown <learc83 at gmail.com> wrote:
> First I'd like to point out that accessing hardware is already
> possible through ActiveX, and I think I've heard of some people doing
> it with XUL. I would like to standardize these hardware interactions.
> I don't think it should be done without strict security measures,
> Indeed. This matters...
> Also it should be possible to allow an administrator to set policies
> to block the browser from accessing usb/RS232.
> So does this...
> At some point it is going to be necessary for the web apps to interact
> with hardware.... I hate the concept of platform specific apps and I
> think that once HTML5 if fully implemented apps will start to
> disappear. The only real hurdle left is hardware interaction, but it
> will happen at some point. Why don't we make sure it gets done right?
> Indeed. This is the point of initiatives like Opera platform, OMTP's BONDI, and WAC [1].
> I'm going to start working on a concrete proposal. I've never written
> one before, so any advice would be appreciated -- should I just look
> through other completed specs and format it accordingly?
> That helps in making the content easy to find and understand for people who are used to reading specs. I suggest you look at W3C's DAP group [2] for an idea of what people are doing - and at WAC for an idea of stuff that is being shipped already.
> [1] http://www.jil.org/web/jil or http://en.wikipedia.org/wiki/Wholesale_Application_Community
> [2] http://www.w3.org/2009/dap/
> cheers
> Chaals
> --
> Charles McCathieNevile  Opera Software, Standards Group
>     je parle français -- hablo español -- jeg lærer norsk
> http://my.opera.com/chaals       Try Opera: http://www.opera.com

Nikita Eelen
Network Manager

6 4 0 West State Street
Alliance, Ohio 4 4 6 0 1

Office: (800) 448-9126 ext. 101
Cell: 330-257-9319
email: neelen at amvonet.com

More information about the whatwg mailing list