From MemberWiki

URL: http://www.openajax.org/member/wiki/Mobile_Minutes_2008-06-19

Attendees

• Paddy Byers, Aplix
• Guillermo Caudevilla, Vodafone
• David Pollington, Vodafone
• Jon Ferraiolo, IBM
• Adam Peller, IBM
• Ian Hay, Orange/FT
• Andrew Sledd, Ikivo
• Troed Sandberg, Sony Ericsson

Minutes

Minutes from last call accepted

Main purpose of the call is to discuss the new document outlining device APIs written by Jon http://www.openajax.org/member/wiki/OpenAjax_Device_APIs

Produce something solid and tangible based on open discussion.

Jon outlined the objective which everyone agreed with based on silence, the objective being to have a working demo by the end of the Summer in time for the next major conference events, tradeshows, in order to do this aim for one or two only to start with like Geo and Address book. Possible if we assume use of Mobilescript from Voda or WebVM from Aplix and add a shim layer.

(Scribe says: I cant make much sense of my notes on the actual discussion now)

During the walkthrough the discussion centred around several topics:

Loader - use an existing one or build own? bubble it up to the shim layer (making it much larger) or push it to the adapters? Hesitant to take on a loaded project at this stage

Paddy volunteered to write up and supply some examples for next call to discuss further

• User Agent - where does the sniffing take place to establish presence of OpenAjax
• Browsers - sticking to main 4 desktop (IE, Opera, Safari, Firefox) and not xHTML type
• OBJECT tag - number of methods and ideas explored
• Connhandles - perhaps overly complex for what is required at this point
• Providers should implement support per API
• Modular - don't load all APIs at each call, make modular, some discussion on asynchronous call, status and how to handle that

Shim layer - try to keep it as thin as possible, some discussion of associative arrays providing a lookup per API, decision made to revisit discussion on modularisation later

Provider provides a list of functions for each API

• shim does lookup
• then calls that function
• makes JS small & fast

Paddy - Provider is the adaptor and shim is the selector

?? asked if a device has two ways to get Geo for example how would the shim know which one to pick?

In the end it was decided to refine proposals by email over the next two weeks and revise at next meeting as the lengthy discussion raised a number of things that need to be resolved, the 2 main talking points identified were whether to be DYNAMIC / MODULAR or a LOADER / ConnHANDLES route and how the shim / API needs to be defined

Next meeting 3rd July at the usual time