W3C home > Mailing lists > Public > public-coremob-camera@w3.org > January 2013

Re: Update

From: <tomomi.imura@nokia.com>
Date: Thu, 3 Jan 2013 00:39:00 +0000
To: <ij@w3.org>, <tobie@fb.com>
CC: <public-coremob-camera@w3.org>
Message-ID: <782CC27336BBDB42A1CAA641AF7CEAB5014B3AC8@008-AM1MPN2-082.mgdnok.nokia.com>
Hi everybody!

Happy new year!

On 1/2/13 1:06 PM, "ext Ian Jacobs" <ij@w3.org> wrote:

>
>On 2 Jan 2013, at 8:42 AM, Tobie Langel wrote:
>
>> Hi all,
>> 
>> Just a quick note (I'm still on PTO) that I'm increasingly concerned we
>> might not find a single mobile browser that meets the various
>>requirements
>> we need to make a fully functional app. E.g.:
>> 
>> - Mobile browsers that support HTML Media Capture: Chrome, Android.
>> - Mobile browsers that support storing blobs in IndexedDB: Firefox.
>> 
>> Although this somewhat makes sense as it is what we're trying to show
>>and
>> improve with Coremob, it might be a serious concern for the MWC app.
>> 
>> We're investigating workarounds right now and we'll have an update
>>shortly.
>
>Hi Tobie,
>
>Thanks for the update. I wish you luck in finding a solution!
>
>One backup for the MWC app would be simply to show the photo gallery on
>different devices. That's obviously less interesting than the full
>camera+gallery combo.
>
>Do you think you'll know the answer to your question in the next 10 days?


Currently, I am working on the workaround for Chrome Mobile for Android.
This browser is still stuck at ver 18, which uses deprecated/buggy
indexedDB, so it is almost like I need to write a whole functions only for
the Chrome.

iDB issue on Chrome 18:
- vender prefix 
- onupgradeneeded event
- using constant READ_WRITE instead of 'readwrite' string for
IDBTransaction

- autoIncrement for DB key (a real problem- I am relying on
auto-incremated id to track photos stored in DB)
 Probably more

I try to get around with most issue, without dumbing down Firefox and
newer Chrome.
My code is in process of getting messy now.

About blob/iDB issue, I can probably just store data urls (strings)
instead of blob objects.
Chrome (in general, even new versions like Canary) does not support blob
in iDB, but data url strings work just fine when I tested.
So hopefully, I can figure out to make this work on Chrome mobile too.

For the browsers which don't support indexedDB at all, e.g. iOS Safari, I
probably have to use alternative dumb-down version of the app.
Or PhoneGap.

IE10 does support iDB (and storing blob too) however, the File Reader is
disabled. (apparently, implemented in IE10 but disabled for WP8).
So I am thinking about using PhoneGap. Also I am thinking about asking
Microsoft guys how to enable the feature. (Possible? Does IE has such
feature like Chrome??? Probably not.)
Because I work for Nokia, the priority of creating PhoneGap app is WP8 >
iOS, if I don't have time.


Anyway, I will let you know the status on Chrome 18 on Android by the end
of this week.




>
>Ian
>
>> 
>> Some of the options imply bypassing IDB altogether for the MWC app, or
>> going with a PhoneGap wrapped app native app instead, but both have
>>their
>> own issues and imply more work.
>> 
>> Best,
>> 
>> --tobie
>> 
>> 
>> 
>
>--
>Ian Jacobs (ij@w3.org)    http://www.w3.org/People/Jacobs/
>Tel:                                      +1 718 260 9447
>
>


Thanks!
Tomomi


/* 
 *  Tomomi Imura
 *  HTML5 Evangelist
 *  Developer Relations
 * 
 *  tomomi.imura@nokia.com
 *  +1.408.368.6848

 */
Received on Thursday, 3 January 2013 00:39:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 January 2013 00:39:36 GMT