The decision whether to integrate directly with an application engine, switch views to an external application, or both (for example, edit an agenda entry and then switch to the Calendar application to view the entry) can be a difficult one. If you want to edit or change data, then using the application engines might be the correct decision, while if you only want to display the information, switching views to an external application might be wiser. By employing external views and using the application engines, with much-reduced effort and resources you will be able to present the user with a familiar, clear interface and effectively share data with other applications in a safe manner.

Many publicly available application engine APIs are contained within the SDK documentation. Details of other APIs can sometimes be found by searching the SDK header files in the \epoc32\include directory in the root of your SDK. Examples presented here include the log engine, agenda model, phonebook engine and many others. As the platform develops over time, you can expect much more functionality to become available ”the examples presented in this chapter represent the general principles of using such Symbian and Series 60 APIs. Hopefully this experience will prepare you for using new APIs as they emerge.

Developing Series 60 Applications. A Guide for Symbian OS C++ Developers
Developing Series 60 Applications: A Guide for Symbian OS C++ Developers: A Guide for Symbian OS C++ Developers
ISBN: 0321227220
EAN: 2147483647
Year: 2003
Pages: 139 © 2008-2017.
If you may any questions please contact us: