Mobile Phone Programming

Transcription

1 agenda Symbian OS Introduction Why Symbian? Overview Symbian Development considerations UI Platforms Series 60/80/90, UIQ etc. agenda Development for S60 Available IDE s Getting the SDK and using the Carbide.c++ IDE Getting Help Symbian Fundamentals 1

2 why symbian? Why are we here? Symbian OS runs on ~75% of all smartphones Nokia expects the smartphone market to exceed 250 million units in million cumulative Symbian OS phone shipments since the formation of Symbian (as of Q2 2006). Symbian C++ gives Maximum flexibility Speed why symbian? why symbian? Licence owners 2

3 overview Runs on battery powered devices has low power consumption Designed for devices with limited memory Open Operating System 3rd party developers can write applications Reliable and stable Applications can run for years without being closed or losing user data Object Orientated from the ground up Provides a C++ API Micro kernel architecture development considerations Native language Symbian C++ Writing of Epoc32 ER1 begins: September 1994 Psion Series 5 PDA ships containing the first release of the Symbian OS in a product: June 1997 ISO/IEC publication of the C++ standard: September 1998 Thus Symbian does not support standard C++ features. development considerations Designed for devices with limited resources E.g. Battery, CPU, Memory. Example device: Nokia N bit CPU 220 MHz (ARM). C: Flash/RAM ~30MB free after boot (this is quite good). Z: ROM stores the OS and built in middleware and applications. Symbian OS v8.1a S60 2nd Edition, Feature Pack 3 3

4 development considerations Older models even fewer resources Source: development considerations Limited resources results in: Active Object Framework, Descriptors etc. Different screen sizes. Numeric keyboard, pen based input, other.. Device specific capabilities. The manufacture adjust the UI layer to match the capabilities of their device. platforms Series 60/80/90 (forum.nokia.com or s60.com) Nokia, Simens, Sendo, Panasonic, Samsung, LG, Lenovo UIQ (uiq.com) Sony Ericsson, BenQ, Motorola, Arima What s the difference: The base system is the same. Main difference is the UI layer. 4

5 platforms We can use a common code base. Source: development for S60 S60 and Symbian evolution Today Overview development for S60 Moving to third edition. Code recompilation. Platform security. Certificates and data caging. More access. Binary break Some migration needed Compatibility 5

6 platform security API Access grouping based on capabilities Note, All SIS files must be signed before installation on the device available IDE s Carbide New generation of development tools. Released beginning of Carbide.c++ is a family of Eclipse-based development tools supporting Symbian OS development on Series 60, Series 80 and UIQ. Carbide.vs is a plug-in that allows Visual Studio users to develop C++ code for Symbian OS platforms including Series 60 and Series 80. available IDE s Other alternatives CodeWarrior for Symbian OS Borland C++ Builder Mobile Edition Using command line tools. Note: Platforms No official support for anything but Windows. Linux and Mac development is possible. 6

7 getting around the SDK Dir: C:\Symbian\OS version\ui version Epoc32 - cross compiler, emulator, include files, etc. Examples - SDK examples Series60Doc - SDK documentation Series60Ex - Series 60 specific examples Series60Tools Tools Drive mappings (z: and c:) Z: \Epoc32\release\winscw\udeb\z C: \Epoc32\winscw\c Lets quickly browse the directories using Carbide.c++ Express Demo Find the steps at: development/programming/symbian_c/ next up Overview of the Symbian OS fundamentals Basic types and Naming conventions Exception handling & memory management Descriptors ( data container e.g. strings) Active Objects Client / server framework Adding to the steep learning curve. 7

8 types and names Naming conventions Helps preserve maintainability, consistency and readability. Approx. 13 rules Basic types Are simple typedefs, e.g. typedef signed int TInt; memory & exception management Reliability and robustness must generally be very high in mobile applications. Effective memory management is also vital due to Devices may be online several weeks (even years) Limited memory Memory leaks must not occur! New concepts: Leave and Traps CleanupStack descriptors Descriptors encapsulate strings and binary data They provide functions to access and manipulate the data They replace NULL terminated strings System APIs nearly always use descriptors instead of: NULL terminated strings Byte arrays Byte pointers 8

9 active objects Non pre-emptive multi-tasking is used: Applications are usually single threaded Within a thread, each event is handled before the next one can be scheduled Events are scheduled by the Active Scheduler Events are handled by Active Objects Multi-threaded applications are possible but are discouraged More difficult to develop Higher run-time cost (context-switching) client / server framework Servers handle access to system resources on behalf of multiple clients (e.g. file server, window server) Servers are located in: their own process or their own thread in a process with other server threads Servers are accessed from applications and other threads by a Client API client / server framework 9

10 getting started Testing you code quickly using console applications! additional resources Great books: Loan a book from us. Remember the IRC channels Freenode #symbian EFNet #symbian.dev additional resources Tutorials, code examples and forum at Tutorials, code examples and forum at forum.nokia.com Wiki at forum.nokia.com/wiki White papers and Symbian OS documentation at Newsgroups regarding a wide range of Symbian related topics: nttp://developer.symbian.com 10

11 want to make a project Recommended C++ experience Use us Step by the office and discuss the project. 11