Daim api functions

Functions
dm_int	DM_Initialize (CONST char *appname, CONST char **argv, int argc)
	Initialize the daim library.
void	DM_Finalize ()
	Release all ressources used by the Daim library.
void *	DM_Sethandler (void *data, void *handler, int handler_type)
void *	DM_GetInstance ()
	Return interface to the run-time instance of the library.
const char_t *	DM_GetMimeType (const char_t *filename)
	Return the mime type associated to the file filename.
dm_long_ptr	DM_GetModule (const char_t *urn, const char_t *modulename, dm_uint _version)
	Return a resident module associated to the specific urn.
void	DM_ReleaseModule (const char_t *urn, const char_t *modulename)
	Remove a module from the resident list. This does not mean that the module is unloaded from the memory due to the fact that instances could be still referenced.

---

Function Documentation

void *void DM_Finalize (   )

Release all ressources used by the Daim library. This function should be called after each DM_Initialize() call. No Daim functions should be called afterward.

void * DM_Initialize (  CONST char *  appname, CONST char **  argv, int  argc )

Initialize the daim library. This function initialize the Daim library and must be called before using any Daim functions. Parameters: appname  is as string identify the application. If NULL, a default name will be assigned. This name is used to create temporary files (such as the log file). argv  is an array of string specifying options passed to the library. see below for a list of options argc  the number of arguments in argv, if argv is NULL terminated then argc can be set to -1. List of options passed to DM_Initialize: '--daim-root <path>' where path is the path to the Daim runtime environment (Usually the installation directory). '--daim-lib <path>[,<path>]' : Application specific directory. This is usually the directory where a specific daim application is installed. '--daim-user <path>' : This is the location where Daim application store data and must be accessible for writing. If not specified, use the system default application data directory. '--nocreatedir' do not create the user repository directories. Because these directories are required by specific tasks, this option should be avoided. '--nolog' do not generate log. Log file is usually created in the user directory. '--profil <name>' indicates which profil to use. '--tracemem' Trace memory usage (console only). The search order for modules and configuration files is : User dir -> Application dir -> Runtime dir

void * DM_Sethandler (  void *  data, void *  _handler, int  _handler_type )

Set specifics handlers for intercepting internal messages.

---