|
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-21909CF6-B810-599A-A486-01BA1BF21F35" xml:lang="en"><title>Introduction</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
13 <p>The TextMTM is an example MTM project, which shows many aspects of dealing |
|
14 with the Messaging APIs. Developers can use it as a basis for experimenting |
|
15 with the MTM architecture, and for studying the MTM interfaces. </p> |
|
16 <p>Rather than implementing a real message transport protocol, the TextMTM |
|
17 simulates this by treating the local file system as a remote mail server. |
|
18 The TextMTM allows a user to create a service representing a folder in the |
|
19 file system. The service then contains entries for each folder and file under |
|
20 that folder, so functioning as a mirror of the folder contents. </p> |
|
21 <p>The UI MTM component allows users to get messages from the "remote" server, |
|
22 to edit the contents of a text message, and to copy messages back to a TextMTM |
|
23 service. Moving and deleting messages is also allowed. </p> |
|
24 <section id="GUID-147AEBF3-2F87-5AA1-AC42-32EEA1FF8315"><title>Download</title> <p>Click |
|
25 on the following link to download the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-419758e4-b663-48d3-bf21-d9c4bb00da23.zip" scope="external">TextMTM.zip </xref> </p> </section> |
|
26 <section id="GUID-32E4981D-BBEA-570F-9770-B5E9F5E15C4A"><title>TextMTM projects</title> <p>The |
|
27 TextMTM is made up of a number of components, and so the source has a number |
|
28 of projects. </p> <p>The following project is a utility project, used for |
|
29 deploying the MTM. </p> <table id="GUID-C760358C-B3D1-54DF-B11D-D029E3C1F3BA"> |
|
30 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
|
31 <tbody> |
|
32 <row> |
|
33 <entry><p> <b>Project</b> </p> </entry> |
|
34 <entry><p> <b>Description</b> </p> </entry> |
|
35 </row> |
|
36 <row> |
|
37 <entry><p> <filepath>txin</filepath> </p> </entry> |
|
38 <entry><p>Utility application for MTM installation </p> </entry> |
|
39 </row> |
|
40 </tbody> |
|
41 </tgroup> |
|
42 </table> <p>The following projects supply the source for the MTM. </p> <table id="GUID-9A6B5470-F988-5100-BD3F-7A2074DE2470"> |
|
43 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
|
44 <tbody> |
|
45 <row> |
|
46 <entry><p> <b>Project</b> </p> </entry> |
|
47 <entry><p> <b>Description</b> </p> </entry> |
|
48 </row> |
|
49 <row> |
|
50 <entry><p> <filepath>txtc</filepath> </p> </entry> |
|
51 <entry><p>Client-side MTM implementation. This defines the methods required |
|
52 for a <codeph>CBaseMtm</codeph> -derived class. It is instantiated by a client |
|
53 application to perform MTM-specific tasks. </p> </entry> |
|
54 </row> |
|
55 <row> |
|
56 <entry><p> <filepath>txti</filepath> </p> </entry> |
|
57 <entry><p>UI Data MTM implementation. This presents the messaging application |
|
58 with useful information, without the need for actually fully loading all the |
|
59 DLLs necessary to handle text messages. </p> </entry> |
|
60 </row> |
|
61 <row> |
|
62 <entry><p> <filepath>txts</filepath> </p> </entry> |
|
63 <entry><p>Server-side MTM implementation. This provides all the functionality |
|
64 to handle messages on the server side, and supports moving, copying, deleting, |
|
65 and creating of entries. </p> </entry> |
|
66 </row> |
|
67 <row> |
|
68 <entry><p> <filepath>txtu</filepath> </p> </entry> |
|
69 <entry><p>User Interface MTM implementation. This is loaded when the user |
|
70 decides to actually perform some MTM-specific task, such as editing a message. </p> </entry> |
|
71 </row> |
|
72 <row> |
|
73 <entry><p> <filepath>txut</filepath> </p> </entry> |
|
74 <entry><p>A small utilities DLL where code resides that has to be shared between |
|
75 the MTM implementations. </p> </entry> |
|
76 </row> |
|
77 </tbody> |
|
78 </tgroup> |
|
79 </table> </section> |
|
80 </conbody></concept> |