Wiley.Developing.Software.for.Symbian.OS.2nd.Edition.Dec.2007 (779887), страница 77
Текст из файла (страница 77)
If this resource file does not exist,then the system uses a default icon and caption for the application.This section provides only a brief introduction to using localizableapplication information files to supply your application with icons andcaptions. You should refer to the SDK documentation for more detail, aswell as examples.The general sequence of events needed to define your applicationcaption and icons is as follows:• Create your icon images using an image editor.• Write the localizable application information resource file definingthe caption, number of icons, and other information.41012.8.1GUI APPLICATION PROGRAMMING•Update the MMP to build this resource file (output will be a binaryRSC file) and to write the bitmaps to a MBM (multi-bitmap) formatfile.
If you use scalable bitmaps, a MIF file is produced instead, butnot via the MMP file (this will be discussed a little more shortly).•Update your PKG file so that the installation will copy the application information RSC and icon bitmap (MBM or MIF file) to the\resource\apps directory of the smartphone.Creating the Icon BitmapsTo cope with the different situations in which application icons may bedisplayed, each application needs to be supplied with icon bitmaps intwo or more sizes.
The required number and sizes (in pixels) vary withthe UI platform.There is also now a Scalable Vector Graphics Tiny (SVG-T) standardthat allows you to create a scalable image and thus you need onlyone copy.Icon bitmaps can be created with any paint program. Each icon imagein Symbian OS consists of two BMP files, one defining the image itselfand the other defining a two-color mask for the bitmap. For every blackpixel in the mask bitmap, the corresponding pixel in the image bitmap isdisplayed – the rest are not displayed, thus giving a transparent effect forthose pixels.
So, for every icon size, you need both an image bitmap anda mask bitmap.All icon graphics get converted to MBM files, which is what Symbianuses. This can be done in the MMP file, or via separate tools. The detailsof creating and building bitmaps can be found in the SDK documentation.12.8.2 Creating the Localized Application Information ResourceHere is a sample localized application information resource file:#include <AppInfo.rh>RESOURCE LOCALISABLE_APP_INFO{caption_and_icon ={CAPTION_AND_ICON_INFO{caption = "My Application";number_of_icons = 3;icon_file = "\\Resource\\Apps\\MyAppIcon.mbm";}};}The LOCALISABLE APP INFO resource defines the application information.
The attribute caption is your application’s caption text.APPLICATION ICON AND CAPTION411Although I have it hardcoded here, you can use an RLS header file todefine the strings in different languages and reference the rls stringidentifier for the caption (see section 12.4.4). The attribute icon filespecifies the MBM file that contains your icons and number of iconsspecify how many icons are in the MBM file.12.8.3Building Information File and BitmapsTo build the localizable information file, enter the following in the MMP:START RESOURCE myapp_loc.rssTARGETPATH \resource\appsENDIf you are using BMP files for your images, you can build them viathe MMP file.
As mentioned previously, if you use scalable bitmap files(SVG-T format), you do not use the MMP to produce the MIF file (scalablebitmap equivalent to the MBM file). Instead, you specify with a separatemakefile that is also referenced in the bld.inf file. Reference the S60example programs for how this is done.
At the time of writing, UIQ doesnot support having the scalable images SVG-T files in your application.Using BMP files, however, works on both platforms.An example of building the icon bitmaps in your MMP is as follows:START BITMAP myapp.mbmTARGETPATH \resource\appsSOURCEPATH ..\imagesSOURCE c24 myapp_small.bmpSOURCE 8 myapp_small_mask.bmpSOURCE c24 myapp_large.bmpSOURCE 8 myapp_large_mask.bmpENDThis would generate a MBM file with two icons, one small and onelarge. The c24 indicates a 24-bit color image.
The bitmaps with the maskin are monochrome bitmaps used to define the image mask. You thenneed to update your package file to copy the localizable information RSCfile and the bitmap MBM file to \resource\apps on the smartphone.References[Babinv1]Steve Babin (2005)Developing Software for Symbian OS:An Introduction to Creating Smartphone Applicationsin C++Publisher: John Wiley & Sons LtdISBN: 0470018453[Campbell]Iain Campbell (2007)Symbian OS Communications Programming, SecondEditionPublisher: John Wiley & Sons LtdISBN: 0470512289[Harrison]Richard Harrison and Mark Shackman (2007)Symbian OS C++ for Mobile Phones, Vol. 3:Application Development for Symbian OS v9Publisher: John Wiley & Sons LtdISBN: 0470066415[Heath]Craig Heath (2006)Symbian OS Platform Security:Software Development Using the Symbian OS SecurityArchitecturePublisher: John Wiley & Sons LtdISBN: 0470018828414REFERENCES[Sales]Jane Sales (2005)Symbian OS Internals: Real-Time Kernel ProgrammingPublisher: John Wiley & Sons LtdISBN: 0470025247[Stichbury]Jo Stichbury and Mark Jacobs (2006)The Accredited Symbian Developer Primer:Fundamentals of Symbian OSPublisher: John Wiley & Sons LtdISBN: 0470058277[Stichburyv1]Jo Stichbury (2004)Symbian OS Explained:Effective C++ Programming for SmartphonesPublisher: John Wiley & Sons LtdISBN: 0470021306Online ReferencesSymbian Developer Network: http://developer.symbian.comOther online references and resources are available on the wiki page forthis book, which can be found on the Symbian Developer Network (http://developer.symbian.com/wiki).
Please leave a comment on the wiki pageif you find a broken link, and we will do our best to find a replacement.Index1G networks 42G networks 4–62.5G networks 4, 63G networks 6, 16–194G networks 4a (function arguments) prefixes,concepts 120ABIs see application binaryinterfacesabld 36–8, 56, 127–31, 142–4,145–9abld freeze 37–8, 128–31,142–9abstract classes, C++ concepts93–4, 98–100ActivateL 374–7active objectssee also asynchronous functionsactive scheduler 81–2,249–75blocks 269, 304–5CActive 82, 249–75cancellations 251–2, 253–4,260–1, 263–8class creation 251–4, 262–8complexity problems 269–71concepts 69, 249–75, 285–6,287–92, 300–1, 335–57construction 251–2, 262–8creation 251–4, 262–8CTimer 271–5, 321definition 249examples 262–8, 335–57high-level view 249–50issues 269–71network programming 335–57non-preemptive multitaskingmodel 250–1, 269–71outstanding requests 270–1priorities 260removal 262requestor implementation 253,262–8servers 303–4, 311–12,313–21sockets 335–57stray-signal exceptions 269–70thread uses 271–5tips 269–71uses 250–1, 271–5active schedulerconcepts 81–2, 249–75,313–21, 335–57customization 257–60definition 249–50, 254detailed workings 255–6error handling 258–60,269–70event-loop pseudo-code255–6examples 262–8, 313–21GUI applications 254–3, 269,342–3, 355–6high-level view 249–51installation 254–7, 313–21leave/trap mechanism 258–9,262–8, 269–70, 314–21starting 254–7, 313–21ActivePerl 518 25–6Add 214–15, 249–54, 257,269–70Add Field 397–401AddFirst 214AddItemL 397–401AddLast 214addressesIP (Internet Protocol) 325–6,331–4, 338–9, 349–53memory 71–2, 293–7MMU 71–2, 74–5, 294–7physical/virtual memoryaddresses 71–7, 294–7AddText 310–21AddViewL 52Adjust 294–6After 119, 251, 269, 271–5,287–8aknapp.h 40–4416aknappui.h 40–4akndoc.h 40–4alarms 90AlertWin 50–4, 402AllFiles 226, 229, 232, 243Alloc 181–5AllocL 181–3AllocLC 110–11, 181–3animation plug-inssee also graphicsconcepts 85–6APIs see application programminginterfacesapparc.lib 128–31AppDllUid 56, 369–77Append 167–8, 171, 175–7,179–80, 192–4, 210–13,340–57AppendFill 193–4AppendFormat 194AppendJustify 193–4AppendNum 193–4application binary interfaces (ABIs)133–5application engines, concepts90–1application frameworksee also graphical user interfaceframeworkconcepts 64–5, 83–5,359–411application processor, concepts80–1application programming interfaces(APIs) 63–4, 77–9, 86–9,104–14, 117, 143–4,161–215, 359–411base libraries 63–4BSD socket API 86–9, 323–4,328–34, 340–1capabilities 129, 131, 160,220–31data organization classes165–215platform security 90–1,217–46sockets 86–9, 323–4, 328–57TCP/IP 323–57types 77–9, 90–1, 104–14INDEXUser 94–5, 104–14, 115application protocols, concepts90–1application services/engines/protocols, concepts 64–5,90–1application views 38–56, 360–5,367–411application-specific cleanups,concepts 107–9applicationssee also executables; processes;softwareavailability 1, 12, 15–16captions 409–11classes 38–56, 365–411communications architecture86–9components 38–56, 365–411concepts 1–2, 12, 38–56,83–5, 149–60, 365–411downloads 1, 9–10, 149–50example applications 38–56,365–411GUI programming 38–56,359–411header files 39–56, 115–18,126–31, 141–4, 151–60,365–411icons 366–7, 409–11installation 23–5, 39–56,59–1, 149–60, 236–7,365–411package definition files 39–56,59–61, 150–60, 365–411platform security 90–1project build files 54–6,115–18, 119–49, 365–411registration files 48–9, 366–7,384–5resource files 44–56, 128–31,141–4, 365–7, 377–411signed applications 30, 60–1,91, 160, 218–46, 324SimpleEx 38–56, 262–8,353–6, 365–411source files 49–54, 128–31,141–4, 365–411TCP/IP applications 323–57third-party suppliers 1, 13–14types 1, 3–4, 12UIDs 38–56, 115–18, 119,128–31, 135–7, 152–60,237–8, 239, 367–411view architecture 409APP REGISTRATION INFO48–9, 384–5apprun.exe 118–19arguments, processes 279–81Arima U308 27ARM 24–6, 59–61, 71–2, 79,118–19, 124–5, 132–5,139–40see also CPUsARMV5...
132–5ARMV6 132–5ARRAY resource 359–60, 390–6arraysclasses 205–13concepts 166–8, 173–4, 198,205–13, 378–80, 390–6data-finding method 211descriptors 166–8, 173–4,198, 206–8dynamic arrays 209–13fixed arrays 205–6inserting/appending data210–11methods 210–13RArray 209–13sorting method 211–12templates 205–6, 209–13thin templates 205–8ASCII 281–2, 332assert macros, concepts 114–15ASSERT ALWAYS 114–15ASSERT DEBUG 114–15Assign 185–6ASSP 77–9asynchronous functionssee also active objects; Logoncancellations 251–2, 253–4,260–1, 263–8concepts 81–2, 247–75,285–6, 287–92, 300–1,311–12, 335–57definition 247examples 262–8, 335–57INDEXhigh-level view 249–51request semaphores 248–75,300–1servers 303–4, 311–12,313–21, 335–57sockets 335–57TRequestStatus 247–61,336–57AT&T 6audio 4, 8, 227automatic network connections,concepts 323–4AVKON CONFIRMATION QUERY404avkon.lib 56, 128–31avkon.rh 44–56, 382, 405avkon.rsg 44–56BackPtr 200–3BackSpace 310–21badef.rh 391–2badesca.h 207–8bafl.lib 207–8bandwidth, concepts 3–11BARM 146Base 294–6base classes, TDes...
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
