Date: Wed, 28 Sep 2011 14:48:44 -0700 > From: Rudolf Streif <[email protected]> > To: [email protected] > Subject: Re: [MeeGo-ivi] [MeeGo-IVI] What does Tizen means for > MeeGo-IVI? > Message-ID: > <CAEKp-aYbQBoozNWrt2EEUzZ0R1GAG9Nt4Tj2==g6ozbety-...@mail.gmail.com > > > Content-Type: text/plain; charset="iso-8859-1" > > MeeGo IVI's work has always been focused on the middleware on top of the > Linux stack provided by MeeGo Core to support the functionality required > for > vehicle applications such as connectivity to vehicle networks (CAN, MOST, > etc), audio management, etc. The user experience has been provided as an > example and is expected to be replaced for a customized one providing > differentiation. > > In that sense all the work that has been done for IVI in conjunction with > MeeGo still applies to Tizen. As the matter of fact, for MeeGo 1.3 the team > has greatly improved MeeGo IVI so that it can run on a wider variety of > hardware and to make it simpler to remove the demo UX and replace it with > something more functional. >
I fully agree with both above statements. Current IVI UX has just been implemented as a reference one, no questions at all... > > HTML5 is mainly an abstraction layer for application development. The > native > application approach chosen for MeeGo puts pretty strong constraints on how > APIs can evolve after products have been shipped. An API defines a contract > between the application and the underlying system and if one changes > without > the other then there is trouble ahead. An abstraction layer such as HTML5 > provides the necessary flexibility for evolution without breaking things. > It > also provides an abstraction from the underlying hardware and its > architecture. The idea is obviously not new and if you remember the early > days of Java this was exactly what Java was intended to do: provide an > abstraction layer for embedded software applications. > > :rjs > ...however, a part of meego core is also Qt, Qt Mobility and Qt WRT, see http://wiki.meego.com/In-vehicle/Roadmap/API https://meego.com/developers/meego-architecture/meego-architecture-layer-view and in IVI community apart of defining abstract apis for IVI, we were making extensions for Qt APIs mentioned. So from IMHO not continuing supporting these Qt APIs, but only starting with HTML5 would be a great step back the roots. cheers simon:) mit freundlichem Gruss / best regards / pozdrawiam / atentamente Simon P. Bolek ------------------------------------------------------ Dipl. Inf. Simon P. Bolek SAP Consultant Business Mobile and IVI Solutions Cell: +49 (177) 67 36 556 mailto: [email protected] http://www.arcom-ivi.de/ XING: https://www.xing.com/profile/SimonP_Bolek GULP: 84465
_______________________________________________ MeeGo-ivi mailing list [email protected] http://lists.meego.com/listinfo/meego-ivi
