The problem with API's in OpenSource programming is they provide functionality across all hardware platforms to handle the minimum requirement set. It would be great to have API's that take into consideration of advanced CPU and GPU functionality for more advanced chipsets. The only questions is which chipsets? Have to pick and choose to make the best decision. Once those API's are in place, then subsets can be created from them to support other GPU and CPU architectures. This also great diversifies the development space and gets different types of developers together.
Cheers!! -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Attila Csipa Sent: Tuesday, June 22, 2010 1:54 PM To: [email protected] Subject: Re: [MeeGo-dev] multimedia architecture On Tuesday 22 June 2010 18:34:32 Thiago Macieira wrote: > > It is said that the MeeGo API is based on the Qt API, thus it sounds > > interesting to have a MeeGo architecture discussion (especially one that > > touches on features used directly by developers) without taking Qt into > > account on some level. > > Yes, there will be MeeGo APIs that are not cross-platform. MeeGo should > have APIs that serve its own needs and should not be limited by what other > platforms have. In fact, MeeGo should have APIs that other platforms *do > not* have. :-) Perfectly understood, it's just there is a fundamental difference in thinking about an API that is a superset of something (Qt in this case) or thinking about an API that is a union of libs that are loosely related at best. Regards, Attila _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
