W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2011

RE: Question about HTML Media Capture specification

From: Josh Soref <jsoref@rim.com>
Date: Mon, 27 Jun 2011 14:46:01 -0400
To: Kyle Huey <me@kylehuey.com>, Vivek Khurana <hiddenharmony@gmail.com>
CC: "js45.yang@samsung.com" <js45.yang@samsung.com>, "Ilkka.Oksanen@nokia.com" <Ilkka.Oksanen@nokia.com>, "dom@w3.org" <dom@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>, 정상욱 <sangwook@samsung.com>, 이원석 <wonsuk11.lee@samsung.com>, 김규영 <gyuyoung.kim@samsung.com>
Message-ID: <6A252AE18765C3468EF06946F24F0B571FFC122EC9@XCH102CNC.rim.net>
Kyle wrote:
> This is not what Josh is proposing ....

Indeed

I should probably have included a pipe between my icon and the browse text.

A more complicated button plus a description to make Vivek happy:
 [ 📷 Take Picture    |v]
  Use front Camera   |
  Use mini Camera    | 
  Use phone Camera   | 
  Select from Gallery|
     Browse...       |

Where clicking on the 'v' would show a menu listing Browse... and other things. The exact text should be discussed with Linguists and UI designers, and is merely to show that there are other possibilities instead of having an intermediate dialog.

I was thinking more along the lines of things like the combined Back/Forward buttons in combination with Microsoft's option of showing only some text.

Microsoft does have some controls which do things like that, but the only ones I can find are tall as opposed to wide, e.g. a "Macros" button in Word where the icon does one thing and clicking the text opens a menu.

Note that the bottom line here is that these are all implementation details. QoI is how vendors compete on feature for their audience/market. -- wrt markets, I recently found 1 person who was able to understand a UI which I had considered incredibly stupid and which no one else I had met understood. It turned out that for a certain market, the UI elements made sense (well, mostly, even she didn't approve / understand / accept some of them).

> Vivek wrote:
>> To allow launching different interfaces from file input type, we
>> should allow changing the value of the 'Browse' text. This way
>> developer can call the camera capture or audio recorder file input
>> button to 'Record' or anything which corresponds to the interface
>> being triggered.

This has internationalization issues, just because a web site designer speaks Finnish or Russian doesn't mean I shouldn't be able to see buttons in English when using an English based browser.

Kyle wrote:
> A whitelisted set of strings shipped with the UA might be ok,
> but this is very much an implementation detail.


Note that the text varies from browser to browser,...
http://swatelier.info/at/screen/formFile2.png

and by language:
http://audi.tw/Blog/webDesign/images/input.type=file.gif



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Monday, 27 June 2011 18:46:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:21 GMT