MMF issue in the 3rd Edition SDK

Hi,

I am using the RMMFController and CMMFDevSound classes to play audio. This
works fine on the S60 FP2 SDK and has been successfully tested on the Nokia
6630.

The issue is that the 3rd Edition SDK doesn't seem to have the
MMFControllerFramework.lib and MMFDevSound.lib which are required by these
classes respectively, so this code can't be ported over to it.

My questions are as follows:
1) Does this mean that one has to only use the Client API for playing audio
or is there anyway to get access to these libs?

2) If not, then what is the procedure for creating and testing MMF plugins
in the 3rd Edition?

3) Also, the TMMFFileParams and TMMFDescriptorParams class required to add
file source and descriptor sources to the controller seem not to be
available in this SDK. So, if at all there is a way to use RMMFController,
then what is the procedure for adding these sources to it?

Thanks in advance,
Sameet.

The header files are public from a Symbian perspective, but it is up to 
Nokia to define what header files they include in  their SDK product.
You need to talk to forum Nokia to find out information about what is 
included in Nokia products.

Symbian partners (members of the platinum partner program) can access the 
required headers from the Binary Access Kit, or from the DevKit.You may be 
able to copy the headers from the previous SDK, however reliance on copied 
headers is risky, given that the API may change in future.

Regards
H


"Sameet" <sameet@nospamarise.net> wrote in message 
news:gXIpr8iLGHA.1036@extapps30...
> Hi,
>
> I am using the RMMFController and CMMFDevSound classes to play audio. This
> works fine on the S60 FP2 SDK and has been successfully tested on the 
> Nokia
> 6630.
>
> The issue is that the 3rd Edition SDK doesn't seem to have the
> MMFControllerFramework.lib and MMFDevSound.lib which are required by these
> classes respectively, so this code can't be ported over to it.
>
> My questions are as follows:
> 1) Does this mean that one has to only use the Client API for playing 
> audio
> or is there anyway to get access to these libs?
>
> 2) If not, then what is the procedure for creating and testing MMF plugins
> in the 3rd Edition?
>
> 3) Also, the TMMFFileParams and TMMFDescriptorParams class required to add
> file source and descriptor sources to the controller seem not to be
> available in this SDK. So, if at all there is a way to use RMMFController,
> then what is the procedure for adding these sources to it?
>
> Thanks in advance,
> Sameet.
>
> 

G'day Hamish!

If the header files are public ((@publishedAll)) from a Symbian 
perspective then they are by definition NOT restricted to partners only 
(@publishedPartner). In which case they should be made available by 
Symbian irrespective of what is on Forum Nokia SDKs. (If Nokia remove or 
modify such APIs it is as you say for them to document what is supported 
on Series 60 phones. But they cannot "unpublish" Symbian OS APIs.)

The further issue of whether APIs are supported going forward or not 
(@released) is clarified by the release cycle tags in the header files, 
e.g. whether they are marked as prototype or deprecated or not. AFAIK 
this does not apply to either of the CMMFDevSound or RMMFController APIs.

 From 
http://www.symbian.com/developer/techlib/papers/symbian_tagging_policy/Symbian_T
agging_Policy_&_Guidelines_v1.0.pdf
the tagging system was supposedly introduced to remove precisely the 
above kinds of ambiguity.

Conclusion: the APIs mentioned should be published for all developers in 
their current version!

G'day Colin

Back for more eh :-) I know the theory, but at this point publishing the 
headers is a low priority - they are available in the UIQ SDKs and the beta 
SDK.

It may be that Nokia are planning on breaking BC on this API and removing 
the headers is a precursor to that. It may also be that they will not allow 
any controller to be signed unless originating through their channels. If so 
providing the headers would simply waste developer time.

I'm therefore working on getting Nokia to:
a) give some transparency on the decision they have made
b) define the mechanism by which developers can access the files 
"officially" if neccessary.

Its taking some time.

Cheerio
H


"Colin Turfus" <colin.turfus@lombardrisk.com> wrote in message 
news:5EuPG4TRGHA.1044@extapps30...
> G'day Hamish!
>
> If the header files are public ((@publishedAll)) from a Symbian 
> perspective then they are by definition NOT restricted to partners only 
> (@publishedPartner). In which case they should be made available by 
> Symbian irrespective of what is on Forum Nokia SDKs. (If Nokia remove or 
> modify such APIs it is as you say for them to document what is supported 
> on Series 60 phones. But they cannot "unpublish" Symbian OS
APIs.)
>
> The further issue of whether APIs are supported going forward or not 
> (@released) is clarified by the release cycle tags in the header files, 
> e.g. whether they are marked as prototype or deprecated or not. AFAIK this

> does not apply to either of the CMMFDevSound or RMMFController APIs.
>
> From 
>
http://www.symbian.com/developer/techlib/papers/symbian_tagging_policy/Symbian_T
agging_Policy_&_Guidelines_v1.0.pdf
> the tagging system was supposedly introduced to remove precisely the above

> kinds of ambiguity.
>
> Conclusion: the APIs mentioned should be published for all developers in 
> their current version!
>
> Colin T