ext Ryan Abel wrote:
Well, except for the part where Nokia ends up marketing it as "MeeGo". Oh, and
Harmattan's, apparently, MeeGo, too, and it definitely has closed stuff at the platform
level.
Yeah . . . not confusing at all. ;)
No at all: it's about standardization. The device must support a certain
set of features and provide well defined APIs.
So if a device is MeeGo compliant, it will be advertised as such.
What's confusing about it?
If you write an application which relies on MeeGo features only and can
be run across multiple MeeGo compliant devices, what matters to you that
in one of them there might be a closed component which doesn't belong to
the MeeGo stack?
igor
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
