On Thursday, 6 de January de 2011 09:15:56 Sergio Schvezov wrote: > On Wed, 2011-01-05 at 17:09 -0800, Thiago Macieira wrote: > > On Wednesday, 5 de January de 2011 09:22:22 Pertti Kellomki wrote: > > > On 01/05/2011 12:58 AM, ext Arjan van de Ven wrote: > > > > > > Does this imply that the reference applications are not compliant? > > > Or do they include Mono in the packaging? > > > > And yes, reference applications don't need to be compliant. Anyone can > > ship a MeeGo device with non-compliant applications. In fact, there's > > nothing that stops non-compliant applications from being allowed on any > > kind of device. > > Can you define allowed?
The sense of the word in English. The opposite of "forbidden".
In other words: nothing forbids non-compliant applications. The specification
deals with what a compliant application and a compliant device must do, at
minimum. What they do in *addition* to the spec is not defined by the spec.
> > What matters is that compliant applications must be accepted and mu
> > t work.
>
> I would of thought that by being compliant, your application would work
> throughout all the verticals. Is that a true statement?
That's the idea.
But note that "work" in our sense here means "it loads and runs", not that it
displays properly or that the application is even suitable for the device.
--
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 MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
