On 11/19/14 13:14, Counihan, Tom wrote: > > >> -----Original Message----- >> From: Dev [mailto:[email protected]] On Behalf Of Thiago >> Macieira >> Sent: Wednesday, November 19, 2014 6:50 PM >> To: Baptiste Durand >> Cc: [email protected] >> Subject: Re: [Dev] Documentation on Tizen.org >> >> Hi Baptiste >> >> As far as I know, we don't have a planned dev guide, especially since >> developer.tizen.org is geared towards app developers and we don't have >> any for Tizen 3.0. > > Is there a risk that this could become a self-fulfilling prophecy here? > > For what it is worth, there is a small nucleus of IVI Tier1s in AGL looking > at HTML5 interface suitability for automotive. > Tizen IVI 3.0 is definitely a target ... not 2.x, so having a clean landing > zone for them to jump from would be beneficial to that ecosystem I suspect. > To that group there is certainly confusion as through this url lens below you > could be led to believe nothing beyond 2.3 exists - and we know how wrong > that is. > > > I note also that the Wearable's HTML5 interfaces appear not to align with the > Mobile Web interfaces - at least interface compatibility between both devices > is not apparent. > a) can someone confirm this? > b) if true, then does that imply other verticals could remove any self > imposed constraint from breaking Interface compatibility?
can you elaborate? they're supposed to match, except if they're optional. optional interface sets (usually backed by availability of hardware) can be queried through system info; other interfaces are supposed to degrade gracefully if they're not appropriate (that is, available but return appropriate error code). I know wearable has chosen to omit some sets, as has TV but they're supposed to follow that model. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
