2011/7/25 Wonsuk Lee <wonsu...@gmail.com>: > 2011년 7월 17일 오후 2:52, Adam Barth <aba...@webkit.org>님의 말: >> This API seems roughly isomorphic to a JSON web service in the browser: >> >> navigation.calendar.findEvents(success, failure, options); >> >> => >> >> var xhr = new XMLHttpRequest(); >> xhr.open('POST', 'device://calendar/find-events'); >> xhr.onload = success; >> xhr.onerror = failure; >> send(JSON.stringify(options)); >> >> The URL-based approach has two major advantages: >> >> 1) URLs are a natural extension point for the platform, leading to a >> clean separation of concerns. For example, you wouldn't need to write >> any code in WebKit. All the supporting infrastructure can be provided >> by the embedder. >> >> 2) URLs allow more natural integration with web sites. As the API is >> structured today, the calendar must be provided by the user agent. >> If, instead, the API was based on URLs, the calendar service could be >> provided by a web services. For example, Google Calendar could >> provide an implementation of the API at >> https://calendar.google.com/find-events and control access to the API >> using CORS. >> >> My sense is that WebKit should not implement calendar or the other >> related device APIs at this time. Instead, we should address these >> use cases using the more extensible, web-friendly URL-based approach. > > I am a little bit confused. What does that mean ? > > Did you think a current version of device APIs(including calendar) are > not mature yet for the Webkit? > or > Web-friendly URL-based approach is better than javascript API for the Webkit ?
IMHO, the web-friendly URL-based approach is better for the web in general (as well as for WebKit specifically). The maturity of the JS APIs isn't really that important because they're headed in the wrong direction, from my point of view. Adam >> 2011/7/16 김동관 <donggwan....@samsung.com>: >>> I've registered bug to https://bugs.webkit.org/show_bug.cgi?id=64662. >>> >>> Donggwan >>> >>> ------- Original Message ------- >>> Sender : Simon Fraser<simon.fra...@apple.com> >>> Date : 2011-07-17 12:20 (GMT+09:00) >>> Title : Re: [webkit-dev] Adding ENABLE_CALENDAR to WebCore >>> >>> What's the bugzilla bug (or bugs)? >>> >>> Simon >>> >>> On Jul 16, 2011, at 8:11 PM, 김동관 wrote: >>> >>>> Hi webkit-dev! >>>> >>>> I wanted to let you know that I plan to add Calendar API support to WebKit. >>>> This API is a new feature that is published by W3C. >>>> The Device APIs Working Group of W3C has just released a Working Draft of >>>> its Calendar API: >>>> http://www.w3.org/TR/2011/WD-calendar-api-20110419/ >>>> >>>> I'm going to commit patch for Calendar API implementation very soon. >>>> >>>> This support will be behind the ENABLE_CALENDAR feature define. >>>> >>>> We'll be setting up a buildbot to track then ENABLE_CALENDAR build >>>> shortly. We expect >>>> this feature to be eventually enabled by all ports. >>>> Looking forward to your comments. >>>> >>>> Thank you. >>>> >>>> Donggwan _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev