12 <concept xml:lang="en" id="GUID-28227926-2D5A-500C-B2BC-0EE6CC077DBE"><title>About application resources</title><prolog><metadata><keywords/></metadata></prolog><conbody><section><title>Overview</title> <p>Much of the information that defines the appearance, behaviour and functionality of a Symbian platform application is stored externally to the main body of the program, in a <keyword>resource file</keyword>. This is unlike some other programming environments, in which a single executable contains all the code and information used by the application. Resource files can have the advantages that information is loaded only when needed, which can reduce RAM requirements, they can be compressed, and they can be localised without needing to recompile the main program. </p> <p>Resource files are developed as text files written in a Symbian platform-specific resource language. These source files are then compiled into a binary file format that can be loaded and read by programs. The source files can be compiled on their own using the command-line resource builder tool (<filepath>epocrc</filepath>), or as part of the standard project building process either from the command-line or from within an IDE. </p> </section> <section><title>Purposes of resource files</title> <p>Resource files are used for the following purposes: </p> <ul><li id="GUID-82CD9E65-0F3E-53E5-98D3-DF6039383F05"><p>to define the application user interface. The C++ application programming framework requires that some aspects of an application’s layout and behaviour, such as the menu bars and dialogs, are defined in a resource file </p> </li> <li id="GUID-35A884F3-384D-576F-927C-1F6F6F340176"><p>to define application properties that are used by the application launcher or system shell. </p> <p>Until v9.0, (<filepath>.aif</filepath>) files are used to define the application's icon and caption, and various properties, for instance whether the application is exposed to users or hidden, whether the application can be embedded, and the priority at which the application should be associated with MIME data types. Aif files are built from a type of resource file. </p> <p>From v9.0, aif files are replaced by <xref href="GUID-3AFA877F-41DE-5343-8BC2-C0FB894A062C.dita">application registration information</xref>. The caption and icon are defined either in a special resource file called a localisable icon/caption definition file, or, if more convenient, in the application's UI resource file. The application's properties and some other information is defined in another type of resource file called a registration file. </p> </li> <li id="GUID-3FEA9285-6F25-538D-B925-30EFF89DE072"><p>Literal strings and other constant data: for example, dialog text and error messages. The resource tool chain provides support for localisation of these. </p> </li> </ul> </section> <section><title>File types reference</title> <p>The resource compilation process uses a number of file types: </p> <table id="GUID-B15BD665-259D-5E38-AF3B-4C0B3111D752"><tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/><tbody><row><entry><p> <filepath>rss</filepath> </p> </entry> <entry><p>resource source file </p> </entry> </row> <row><entry><p> <filepath>rls</filepath> </p> </entry> <entry><p>defines localisable strings, for inclusion in the resource source file </p> </entry> </row> <row><entry><p> <filepath>h</filepath> </p> </entry> <entry><p>header file, for inclusion in C++ file </p> </entry> </row> <row><entry><p> <filepath>rh</filepath> </p> </entry> <entry><p>resource header, for inclusion in the resource source file </p> </entry> </row> <row><entry><p> <filepath>hrh</filepath> </p> </entry> <entry><p>common C++ or resource header, for inclusion in either type of source file </p> </entry> </row> <row><entry><p> <filepath>rsg</filepath> </p> </entry> <entry><p>resource header file output from the resource compiler </p> </entry> </row> <row><entry><p> <filepath>rsc</filepath> </p> </entry> <entry><p>compiled resource file from the resource compiler </p> </entry> </row> </tbody> </tgroup> </table> </section> </conbody></concept> |
|