Uikon and Avkon Series 60 add a user interface layer (AVKON) above Uikon under the bottom of Symbian OS V7.0s. Uikon is the Symbian core user interface, and Avkon is a user interface of the S60 platform. Avkon provides a set of UI components and a software frame designed for Series 60 devices. Uikon is a user interface and control framework supported by all Symbian OS devices. Avkon is the 60 Series Extensions and Changes for other parts of the UIKON and Symbian OS Application Framework in Series 60 SDK (in Folders: / Series60ex). Software Examples are available to develop in Avkon. When I saw these code, I was thinking, how to use VC to open, no DSW, DSP first look at the help to find. Solution to an example, HellpWorld uses the ABLD to build HelloWorld.dsp and HelloWorld.dsw project files in the command line. We first enter the Series60Ex / HelloWorld directory. In Symbian, a Project is usually organized according to Inc, SRC, Group, and the project file is placed in the group directory. Use the command line mode to enter the directory, then execute: BLDMAKE BLDFILES This command generates an abld.bat batch file in the group directory, and generates series60ex / helloWorld / Group under Series60 / EPOC32 / Build, and is in the most Generate the .make file in the underlying directory. Then, running the generated abld.bat abld makefile VC6 can generate a VC engineering file For MetrowerKs CodeWarrior, you can use a normal way to create a project file in the IDE, or directly import the .mmp file directly into the IDE. The import process will establish the files required for the HellWarriRD.mcp. Similarly, the Borland C Builder mobile version of the IDE can perform similar import transactions similar to the MetrowerKs IDE, but it is imported into the BLD.inf file instead of .mmp file. For example, Borland C BuilderX will establish a project file called HelloWorld.cbx. 60 Series Application Framework MVC is 60 Platform User Interface Design General Design Mode S AVKON's Basic User Interface Component Notes No visual interface design, interface controls and text must be defined in the resource file. Of course, you can also create controls or modify controls in your code. A small handheld device such as a smart phone, once a resource overflow error, is important for the system that returns to the previous stable state without losing any important data. This makes it very important to completely capture and handle each run error for the system and application. Due to errors in resource overflow, it is called exceptions as all running period errors. In standard Catch-throw mechanisms, these exceptions are processed using the try-catch-throw mechanism, but because it causes the negative impact of code length, Symbian OS provides its own mechanism called Trap Harnes. The other reason for Symbian develops their own exception handler is to develop Symbian OS, the try - catch - throw mechanism is not part of the C standard. The concept of trap-harness is to encapsulate a TRAP macro that may cause an exception. This macro can be used to capture multiple functions and these functions can be nested. In case an exception, the execution of an exception can be terminated through the USER :: Leave function, which is equivalent to the THROW in the standard C exception handling.
This is called a Leave (away), which will return the program to the end-end TRAP macro, where the corresponding recovery action can be executed. Symbian OS also provides a tool to clear exceptions. A CleanupStack is used to reference only an automatic variable reference, and if a Leave occurs, it needs to be released. The Trap macro will destroy the memory allocated in the Cleanupstack. Multitasking and Memory Management Symbian C API achieves very effective multitasking and memory management. Memory-based operation, such as the context switching of the application is limited to the smallest. Symbian OS is primarily based on event drivers rather than multi-threaded mechanisms. Multithreading can be achieved but should be avoided because each thread system overhead potentially adds a few thousand bytes. Instead, a basic event driver does not require any applications.
Context switch and only dozens of bytes of system overhead. Already give special attention to the health and reliability design of Symbian OS.
