Em Quarta-feira 19 Maio 2010, às 11:34:58, Cornelius Hald escreveu: > Example: > We have the reference Meego Handset UX and Nokia decides to customize > it. They exchange the theme, graphics etc., which shouldn´t be a > problem. But they also add the NokiaFancyButton API. This button is > based on Qt and provides some über cool animations and stuff. Are they > allowed to do so? > > If yes, each application, that makes use of NokiaFancyButton API will no > longer be compatible with other Meego Handset products. So how will > compatibility be ensured?
Adding new libraries is ok. I expect that to happen all the time.
What developers need to understand is that those libraries are not part of the
MeeGo API. If they choose to use them, they will be subjecting themselves to
whatever binary guarantees and release schedules those libraries provide, as
well as being deployed only on certain devices.
I don't think this is a compliance issue. It's a communication issue.
And I think the SDK should not include by default those extension APIs. But it
should be possible to add them later, *consciously*. ("I know what I'm doing,
please install this library")
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
