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.
Meego midware APIs like gstreamer that are (1.) declared to common Meego
Core for all architectures, but in same time (2.) as part of adaptation
layer.
I have a feeling that these should be clearly two separate things, but
are they ?
The way I would like to see it -- the strictly defined thing should be
the naming of APIs within Meego API level. Then, to be compliant with
that from middleware point of view, bunch of backend frameworks has to
be provided with more or less specific solutions suitable for each
targeted device. Time wasn't right to provide such level with Maemo or
Moblin -- and still wondering would Meego do that either.
In the other hand, its nice to have a common core. And gstreamer for
example, is doing its part (in providing qt multimedia backend) quite
flawlessly for bunch of architectures. This certainly accelerates the
adaptation work, but..
- is the common core idea made because of its benefits in adaption work ?
or
- are the component's declared as part of Meego compliance specification ?
For example, I would like to see Meego API (the apps portability thing)
to spread to architectures basing on strict OMX AL way someday. To see
such happening, the compliance specifications should not mention much
about middleware -- and stay strict with Meego API in both ways.
The common core efforts made so far are somewhat miss leading and makes
deves wonder whether it is still going to be ok to access middware API's
in wild fashion like before.
regards,
-Teemu
Narendranath Ghosh wrote:
I want to see the whole architeture starting from HW (with
accelerator) to kernel to codes to gstreamer to user application
including QT.
also want to know how USB webcam fits into it.
On Tue, Jun 22, 2010 at 12:22 PM, Zhou, Ting Z <[email protected]> wrote:
Hi, Naren
Maybe this link below can answer some of your questions
http://labs.trolltech.com/blogs/2009/09/09/multimedia-in-qt-whats-the-story/
the qt-x11 package has dependency on gstreamer.
As a programmer, we can directly call qt-mobility media or phonon APIs to write
the media applications without touching gstreamer api.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Narendranath Ghosh
Sent: Tuesday, June 22, 2010 4:54 PM
To: Development for the MeeGo Project
Subject: Re: [MeeGo-dev] multimedia architecture
thanks,
What I understand is all the multimedia calls should via GStreamer.
So, how QT is doing it? Doest it have a link with GStreamer?
I want to know how QT or the programming framework is connected with
the multimedia framework.
Regards,
-Naren
On Tue, Jun 22, 2010 at 11:47 AM, Xu Cheng <[email protected]> wrote:
Hi, Naren
i has been building a programming by GStreamer.
QT has links with GStreamer?
The first , you should download and install GStreamer packages in
workstation ( MeeGo provide packages of GStreamer ). The second, you could
programming most of code by Qt and using GStreamer building media player
modules.
I mean if I want to play some sound or video using QT programming?
Any component for Audio routing?
Qt have a multimedia modular class library which name is Phonon. It's
similar with GStreamer.
if I want to write my own application , do I have to use GStreamer
directly?
is there any detailed document?
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/index.html
In this manual, you could learn GStreamer concept and found some example.
--
Xu Cheng
+86-13517271560
-----------------------------------------------------------------
Wuhan Dail Science & Technology Co., Ltd
www.virtualdell.com
TEL: +86-27-83360199
FAX: +86-27-83775399
Ronghuayicun No.13, Qiaokou District
Wuhan, Hubei Province, P.R.C
PC: 430023
-----------------------------------------------------------------
_______________________________________________
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
_______________________________________________
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
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
