Change history and release notes

This page describes important changes and known issues in this release.

Change history

Changes since the 1.0 release of the library:
  • Rebranded Forum Nokia terminology to Nokia Developer as per the guidelines.

Changes since the 0.9.1 release of the library:
Changes since the 0.8 release of the library:
  • API changes and compatibility breaks.

  • DSA Migration Guide.

  • The Redraw Drawing page in the Window Server section has been updated to explain some particular issues for applications that perform high frequency rendering on S^3.

  • The Tools and Utilities section has been removed. The content previously included in this section will be delivered with other Tools documentation in the Symbian^3 Tools Guide.

  • The CAF for DRM content is added to the OS Security Guide.

  • The Message Authentication Code (MAC) algorithm-related contents have been added to the OS Security Guide.

  • The TechView snapshots in the Graphics Guide are replaced with the S60 Emulator snapshots.

Release notes

The Developer Library for Symbian^3 is still in development. Please note the following important known issues and limitations with this release:
  1. In this release of the library, the C++ reference, organized according to the Symbian System Model, has the following limitations:
    • There are a number of empty pages in the table of contents.

    • Pages do not include information on libraries and required capabilities

    The recommended way to find classes and methods in the API reference is to use the search: type in the name of the class or method and click Go. You can also limit your search scope to include only topics in parts of the library by clicking Search scope.
  2. The API specifications are organized according to the Symbian system model, with each API spec located in the layer and package the API belongs to.

    Not all packages have API specifications.

    The recommended way to find API specifications is to use the search with the name of the API as the search term.
  3. Some links, particularly to API specifications and to the API reference, are broken.

  4. The contents in this library are not pre-indexed and so the first search will take a few minutes.