On Sat, May 7, 2011 at 2:23 PM, Counihan, Tom <[email protected]> wrote:
[...] >> >> Does that mean the IVI compliance specification is independent of the >> overall MeeGo compliance specification? > > Mark gives a great insight into the compliance structure here: > http://conference2010.meego.com/session/app-compatibility-and-meego-compliance-program > It's worth a view as it addresses many of the questions. Thanks. I'll read that. > In essence, IVI will have an additional spec, but an IVI compliant system is > a combination of the 'core' compliance, plus the additional IVI spec. So each vertical's compliance "profile" is a compliment to the overall MeeGo Compliance, if I understand things correctly? >> >> Lastly, I'd like to know the specifics about OpenGL, particularly >> OpenGL ES. Is OpenGL ES going to be part of compliance in MeeGo IVI? > > http://dev.linuxfoundation.org/~mats/MeeGo-Compliance-Spec-1.0.99.9.pdf > states: That document has a version number very similar to the MeeGo version numbers. Does that mean they track each other? Or is that just a coincidence? If they follow each other, are there relevant documents for MeeGo 1.2? Does the spec change significantly from one version to the other? > Implementations must support MeeGo API. The MeeGo API consists of the > following: > * Qt 4.7 [Qt47] > * Qt Mobility 1.0 [QtMob] > * OpenGL ES 2.0 [OGLES] (ARM) or OpenGL [OGL] (Atom) > > So, ES is part of Core, ergo it is automatically part of IVI compliance. So this means that one can specify in the compliance profile for the IVI vertical OpenGL ES? Regards, Jeremiah _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
