[email protected] wrote: > On Thu, Nov 11, 2010 at 01:27:44PM -0800, Andy Ross wrote: >> The subject of how the "MeeGo API" is defined came up in the TSG >> yesterday, and against my better judgement I managed to inject myself >> into a discussion about standards. >> >> The way it's currently phrased, the MeeGo API is a very limited set of >> libraries (Qt, QtMobility and GLES, plus the web framework). >> Everything else is reserved for the "Platform API", which carries no >> promise of future availability. > > I have just recently read the developer pages on this very > subject, and I was surprised to find the distinction, that Meego Touch > Framework and the Web Runtime are in a "Platform API" with > warnings against using them. More clarification is indeed > needed, as far as I am concerned.
In the case of these two, it's a question of maturity. Since the current versions aren't fully mature, it can't be promised they won't change in the next version. There's nothing to prevent, and indeed it's the intent, to promote these to high-guarantee status once the right level of maturity is reached. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
