Hi Thiago, and all Very happy to see you involved, Thiago (Yes I know you have been for quite a while now...)
> From: IVI [mailto:[email protected]] On Behalf Of Thiago Macieira > Sent: den 20 augusti 2014 17:22 > > On Wednesday 20 August 2014 16:00:53 Patrick Ohly wrote: > > On Wed, 2014-08-20 at 14:54 +0200, José Bollo wrote: > > > The OSP framework is deprecated and should not be used. In place, > > > the C framework (known as CAPI), on wich OSP was built, was promoted > > > to the rank of official native API. > > > > Are you sure that this has happened and if so, whether it applies to > > IVI or only some of the other profiles? > > As far as I know, this has not happened for any profile yet. Those are > intentions. > > And even for IVI, as far as I know there are currently no plans to add > official > support for native APIs. That's not to say that it may not be provided by somebody. Maybe a native framework appears running on another platform that is complete enough and attractive enough that porting to Tizen IVI makes sense... Let's see what the future holds, and let's talk about it! :-) GENIVI takes a comprehensive view on this as the organization often does, which could mean it takes time, but leads to a thorough understanding and architecture, I envision. That means describing how different application frameworks are built in general, and exemplifying with more than one concrete example (where Tizen is a prominent one). And then looking into what is common and different, so that collaboration and/or standardization can evolve from that understanding. From that result companies, alliances, and projects (I'm thinking widely here, such as GNOME desktop) can hopefully make informed decisions as well as find additional collaboration opportunities. Information from this work will be published, and as always any newly developed code under FOSS licenses. It will take a little time but "watch this space" ;-) > However, considering that most applications running on an IVI device are > pre-installed, official API matters little. The OEM can use whatever APIs > they want to use. This is relatively true but changing in the industry. Evaluating what the native APIs should be and finding at least some opportunities for sharing is still in our interest. Apparently it is worthwhile for Web APIs, right? Also, sorry to ramble on and this is not a sales pitch... but GENIVI's strong focus on interfaces and development of the Franca IDL, tooling and principles are part of a strategy. One of the things I have tried to promote out of that is that APIs are APIs... With minor exceptions perhaps, there need not be a difference between native and Web APIs for application development. You can achieve that by copying them manually, or as we envision generating different bindings out of only one common description (in Franca IDL). The challenge of course is both legacy and competition. You must stay true to other new standards that matter; any W3C defined APIs will of course be used if they exist. Similarly, with Qt as an example you need to decide which of the standard Qt libraries - multimedia, networking, file I/O, IPC,... - shall be the basis for your application API and which will be custom APIs. The statement from Tizen devs so far I think is that Qt standard APIs are too desktop oriented to make sense to port. I would suspect a Qt based framework would be somewhere in between - a few common Qt APIs, some evolved from mobile space (QtMobility etc...), and a third category will be IVI specific. All the best, - Gunnar > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > _______________________________________________ -- Gunnar Andersson Lead Architect, GENIVI Alliance Infotainment, Volvo Car Corporation _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
