On Wed, May 19, 2010 at 6:21 AM, Thiago Macieira <[email protected]> wrote:
> Em Quarta-feira 19 Maio 2010, às 11:34:58, Cornelius Hald escreveu:
>>
>> 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.
I disagree here - I think we need some kind of compliance stamp
indicating that an application is MeeGo compliant - indicating that it
will run happily on all MeeGo devices.
And I would definitely expect that 'vendor specific' applications
would not qualify as a 'MeeGo compliant app.
I haven't seen any details on standards for MeeGo compliant apps yet,
but I'd assume that our friends at Nokia and Intel have plans around
this - hopefully we'll hear more as part of 'the Big Reveal'...
>
> 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")
Yeah, that makes sense - Maybe even show a visual indicator that you
are running in 'non-compliant mode' when you do this.
I'd like to see some kind of automated or semi-automated testing to
ensure MeeGo compliance for applications - Perhaps running a series of
tests in the simulator from the stock SDK could be part of that...
Warren
--
Warren Baird - Photographer and Digital Artist
http://www.synergisticimages.ca
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
