Who am I?
Works for Forum Nokia where his task is to represent Nokia in Symbian Signed and Java Verified.
Calendar
Recently...
Categories
- Browsing [12]
- Business Opportunities/Services [0]
- CDMA [0]
- Connectivity [1]
- Enterprise [0]
- Entertainment [0]
- Event [0]
- Flash [0]
- Games [0]
- General [0]
- Java [2]
- Location Based Services [0]
- Messaging [0]
- Open C [0]
- Python [0]
- S60 [1]
- Series 40 [0]
- Series 80 [0]
- Symbian C++ [12]
- Testing [6]
- User Experience [1]
Risto Helin's Forum Nokia Blog
Opportunities in the 3rd edition
Rippe | 13 October, 2006 12:29
Had bumped into quite many interesting requests lately. Assumptions that a capability is needed, even though it is not needed. I felt that it is good to raise them up here, in case someone happens to read this blog.
The user can grant
LocalServices
ReadUserData
WriteUserData
NetworkServices
UserEnvironment
to an application at installation time. It's up to the user to trust the application or not, but the capabilities can be granted. This way you could for example send messages without the application from asking the user every time you send the message.
The 3rd Party ETel API seems to have a bleak history. Fortunately there is some light at the end of the code, just to take an example:
The IMEI code can be obtained asynchronously using 3rd Party ETel API as follows:
TRequestStatus iStatus;
CTelephony::TPhoneIdV1 iPhoneId;
...
CTelephony telephony = CTelephony::NewL();
CTelephony::TPhoneIdV1Pckg phoneInfo(iPhoneId);
telephony->GetPhoneId(iStatus, phoneInfo));
...
TPtrC theIMEI(iPhoneId.iSerialNumber);
No capabilities are needed to achieve this.
The same API (if I remember correctly) can also be used to establish a connection without the user needing to select the access point.
Here comes the question. What do you think are the best ways of letting everyone know about these opportunities? A document? Discussion group? FAQ list?
The user can grant
LocalServices
ReadUserData
WriteUserData
NetworkServices
UserEnvironment
to an application at installation time. It's up to the user to trust the application or not, but the capabilities can be granted. This way you could for example send messages without the application from asking the user every time you send the message.
The 3rd Party ETel API seems to have a bleak history. Fortunately there is some light at the end of the code, just to take an example:
The IMEI code can be obtained asynchronously using 3rd Party ETel API as follows:
TRequestStatus iStatus;
CTelephony::TPhoneIdV1 iPhoneId;
...
CTelephony telephony = CTelephony::NewL();
CTelephony::TPhoneIdV1Pckg phoneInfo(iPhoneId);
telephony->GetPhoneId(iStatus, phoneInfo));
...
TPtrC theIMEI(iPhoneId.iSerialNumber);
No capabilities are needed to achieve this.
The same API (if I remember correctly) can also be used to establish a connection without the user needing to select the access point.
Here comes the question. What do you think are the best ways of letting everyone know about these opportunities? A document? Discussion group? FAQ list?
Symbian C++ |
Next | 
Previous |
Comments (2) | 
Trackbacks (0)
Comments
Re: Opportunities in the 3rd edition
biskero | 14/10/2006, 03:00
CiaoI think a discussion group will help, with some common examples that developers can refer to.
Thanks
Alessandro
Re: Opportunities in the 3rd edition
loginssuck | 13/10/2006, 22:52