|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-D7600D93-CFB8-565D-8200-7082B2CF1791" xml:lang="en"><title>User |
|
13 Interface Data MTM</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <p>UI MTM libraries can be quite large, and often there are functions that |
|
15 Messaging applications need to access often and rapidly. To improve memory |
|
16 efficiency, these functions are split off into another DLL, called the UI |
|
17 Data MTM that can be easily kept in memory without the extra overhead of the |
|
18 UI MTM. </p> |
|
19 <section><title>UI Data MTM base class</title> <p>The base class for a UI |
|
20 Data MTM is <xref href="GUID-899C6D87-5712-34A7-902C-EA452894700C.dita"><apiname>CBaseMtmUiData</apiname></xref>. The implementation of UI Data |
|
21 MTMs is relatively simple, as they contain little more than functions to return |
|
22 the required icons and extra menu items. </p> <p>UI Data MTMs offer the following |
|
23 capabilities: </p> <ul> |
|
24 <li id="GUID-EF22528E-D4EA-57B4-84FC-BD8E44D742DA"><p> <b>Provide MTM-specific |
|
25 icons for Message Server entries</b> </p> <p>Provide bitmap icons for messages, |
|
26 folders, and services for display in the various folder views. For each icon, |
|
27 an array of bitmaps should be available, giving the icon in a number of sizes. </p> </li> |
|
28 <li id="GUID-2830B9E2-B9D1-50AF-B6E9-43D187BE053A"><p> <b>Provide user interface |
|
29 text</b> </p> <p>Provide command captions for MTM-specific functions that |
|
30 the Messaging client application can dynamically add to menus and dialog controls. |
|
31 A function ID is associated with each caption to identify the MTM-specific |
|
32 function that should be invoked when the command is chosen. This data is encapsulated |
|
33 in a resource of the <codeph>MTUD_FUNCTION</codeph> type. </p> </li> |
|
34 <li id="GUID-24B76538-A4BB-5996-9187-EC03393C35A9"><p> <b>Verification of |
|
35 MTM functions</b> </p> <p>Validate the specified functions that are available |
|
36 on a particular entry, so that a Messaging client application can process. </p> <p>It |
|
37 is intended that client applications use the <xref href="GUID-F5466277-25C7-31BD-8129-A0FF3D84FC03.dita"><apiname>OperationSupportedL()</apiname></xref> function |
|
38 to dynamically set the user interface features that are available depending |
|
39 on the entry currently selected within the application. For example, menu |
|
40 items that do not apply to particular entries could be greyed out. </p> </li> |
|
41 </ul> <p>The <xref href="GUID-899C6D87-5712-34A7-902C-EA452894700C.dita"><apiname>CBaseMtmUiData</apiname></xref> class provides the virtual |
|
42 functions for overriding in derived classes.</p> </section> |
|
43 </conbody><related-links> |
|
44 <link href="GUID-59217FA7-3078-53CA-88B3-78D6FB788271.dita"><linktext>MTM |
|
45 overview</linktext></link> |
|
46 <link href="GUID-BAD138D5-2914-5C6E-9FA4-F7A3CCB85E6D.dita"><linktext>MTM |
|
47 Capabilities</linktext></link> |
|
48 <link href="GUID-1E2DB50A-D8D7-595D-8448-77F057655E82.dita"><linktext>Writing a |
|
49 UI Data MTM </linktext></link> |
|
50 </related-links></concept> |