![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
The TextMTM can be built, deployed on the WINS emulator or native platform, and its functionality experimented with through the ER5 Email application.
To do this requires a number of steps:
.sis
filestxdat
and then the txin
program to register the TextMTM with the Message ServerThe following sections contain more details on each of these.
Building the TextMTM is a little more complex than some other examples, as it is made up of a number of projects, some of which include headers from other projects, or link to the utilities DLL txut
. Additionally, built resource files for the txti
and txtu
projects need to move to their target folders \system\data
before the related MTM components can be used.
For these reasons, you are recommended to use initially the provided ebld
script to perform the build. This ensures that the special requirements mentioned above are met. To build all components, go to \epoc32ex\txbuild
and run the command:
For example, ebld all wins deb
, for the debug Emulator.
If you are interested in the details, see the ebld
script and the following information. After this initial build, all the special steps will have been performed, and you can re-build individual components through an IDE or ebld
.
The projects have batch files that perform special build steps. The ebld
script invokes these batch files at appropriate times in the build process.
The batch files are of the following types:
export.bat
: copies header files that may be required for inclusion by other projects into the \epoc32\include
directory. This allows these headers to be included with a simple #include <header> macro, rather than specifying a full path. You can explicitly invoke all the export batch files using the command ebld export all
.
prebld.bat
: called before the compile and link phase. The only instance is in the txti
project, which invokes bmconv
to build an .mbm
file containing various icons.
postbld.bat:
called after the compile and link phase. The txti
and txtu
projects have such a file to move built resource files to the \system\data
target folder.
Section Contents
For the MARM platform, the built files must be transferred to the target machine. .sis
files for this purpose for use with EPOC Connect are generated when ebld
is invoked for a native platform target.
You can run an individual .sis
file to transfer an individual component. Alternatively, you can combine the .sis
files for all projects, and transfer them together. To do this, go to txbuild
and enter the command:
Then run the generated txtmtm.sis
file.
You should have run Email at least once before registering the TextMTM, as this creates some necessary folders.
Before the TextMTM can be used with Email or other message client application, it must be registered with the Message Server. Two simple console programs are provided to do this.
txdat
: run this to create a registry data file textmtm.dat
in \System\Mtm
.
txin
: run this to inform the Message Server of the TextMTM registration data.
Both programs simply print OK on success.
Start the Email application in the normal way. You will find that it has automatically detected the presence of the new MTM and added suitable commands to the user interface. For details of the available functionality, see the other documentation on individual TextMTM components, but to get started, try the following:
Create a new TextMTM service using Tools\Add new account\Text. You will be asked to choose a directory to be mapped to the TextMTM service.
Create a new Text message using Message\Create new Text. The new message is placed in the Draft folder. As the TextMTM does not currently include a user interface for message editing and viewing, this is simulated by flashing an Editing information message.
Select a Text message in a local folder. Check that a special Export to file command appears in the Tools menu and use it.
Cut, copy, and paste messages between local folders and the service.
Add and remove files manually from the directory mapped to the TextMTM service using the System screen. In Email, select the service and see that a special Tools\Refresh service command appears. Use this and check that the service now accurately reflects the state of the directory.
Note: in debug builds a panic occurs if you delete from Email a service that has children. This does not occur in release versions of Email and can be ignored.
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |