On 6/22/2010 7:24 AM, Teemu Tuominen wrote:
Hi,
This discussion went straight into details, but it made me wonder what
is the correct steering from the top -- about directly accessing below
Meego APIs. I think within Meego context, man shouldn't bypass Meego
API. But, it would be nice to hear it from someone sitting on top of
meego-architecture.
ok so this is a little more complex than we'd like due to reality ;-)
"Normal" applications are expected to just use the Qt Multimedia APIs to
play media, and not talk to gstreamer directly.
However, at the same time we realize that specialist type of
applications may want to have more finegrained and detailed control than
the Qt Multimedia API allows (which is somewhat of an abstraction after
all), so we have
to allow direct access to gstreamer as well, to not make really
interesting applications impossible.
But again, normal apps should use the Qt Multimedia APIs....... only if
you do something completely out of the ordinary should one need to go
deeper,
and at that point you accept that you go to a more "raw" interface.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
