]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/filetype.tex
Added EVT_MOVE_START, EVT_MOVE_END (wxMSW only for now)
[wxWidgets.git] / docs / latex / wx / filetype.tex
CommitLineData
b13d92d1
VZ
1\section{\class{wxFileType}}\label{wxfiletype}
2
36edded9 3This class holds information about a given {\it file type}. File type is the same as
b13d92d1
VZ
4MIME type under Unix, but under Windows it corresponds more to an extension than
5to MIME type (in fact, several extensions may correspond to a file type). This
6object may be created in several different ways: the program might know the file
7extension and wish to find out the corresponding MIME type or, conversely, it
8might want to find the right extension for the file to which it writes the
9contents of given MIME type. Depending on how it was created some fields may be
cc81d32f 10unknown so the return value of all the accessors {\bf must} be checked: {\tt false}
b13d92d1
VZ
11will be returned if the corresponding information couldn't be found.
12
13The objects of this class are never created by the application code but are
14returned by \helpref{wxMimeTypesManager::GetFileTypeFromMimeType}{wxmimetypesmanagergetfiletypefrommimetype} and
15\helpref{wxMimeTypesManager::GetFileTypeFromExtension}{wxmimetypesmanagergetfiletypefromextension} methods.
f6bcfd97 16But it is your responsibility to delete the returned pointer when you're done
b13d92d1
VZ
17with it!
18
19% TODO describe MIME types better than this...
36edded9
JS
20A brief reminder about what the MIME types are (see the RFC 1341 for more
21information): basically, it is just a pair category/type (for example,
22"text/plain") where the category is a basic indication of what a file is.
23Examples of categories are "application", "image", "text", "binary", and
b13d92d1
VZ
24type is a precise definition of the document format: "plain" in the example
25above means just ASCII text without any formatting, while "text/html" is the
26HTML document source.
27
28A MIME type may have one or more associated extensions: "text/plain" will
29typically correspond to the extension ".txt", but may as well be associated with
30".ini" or ".conf".
31
b13d92d1
VZ
32\wxheading{Derived from}
33
36edded9 34None
b13d92d1 35
954b8ae6
JS
36\wxheading{Include files}
37
38<wx/mimetype.h>
39
a7af285d
VZ
40\wxheading{Library}
41
42\helpref{wxBase}{librarieslist}
43
b13d92d1
VZ
44\wxheading{See also}
45
46\helpref{wxMimeTypesManager}{wxmimetypesmanager}
47
48\latexignore{\rtfignore{\wxheading{Members}}}
49
6be663cf 50\membersection{MessageParameters class}\label{wxfiletypemessageparameters}
b13d92d1
VZ
51
52One of the most common usages of MIME is to encode an e-mail message. The MIME
53type of the encoded message is an example of a {\it message parameter}. These
54parameters are found in the message headers ("Content-XXX"). At the very least,
55they must specify the MIME type and the version of MIME used, but almost always
56they provide additional information about the message such as the original file
57name or the charset (for the text documents).
58
59These parameters may be useful to the program used to open, edit, view or print
60the message, so, for example, an e-mail client program will have to pass them to
61this program. Because wxFileType itself can not know about these parameters,
62it uses MessageParameters class to query them. The default implementation only
2edb0bde 63requires the caller to provide the file name (always used by the program to be
b13d92d1
VZ
64called - it must know which file to open) and the MIME type and supposes that
65there are no other parameters. If you wish to supply additional parameters, you
66must derive your own class from MessageParameters and override GetParamValue()
67function, for example:
68
69\begin{verbatim}
70// provide the message parameters for the MIME type manager
2432b92d 71class MailMessageParameters : public wxFileType::MessageParameters
b13d92d1
VZ
72{
73public:
2432b92d 74 MailMessageParameters(const wxString& filename,
b13d92d1
VZ
75 const wxString& mimetype)
76 : wxFileType::MessageParameters(filename, mimetype)
77 {
78 }
79
80 virtual wxString GetParamValue(const wxString& name) const
81 {
82 // parameter names are not case-sensitive
83 if ( name.CmpNoCase("charset") == 0 )
84 return "US-ASCII";
85 else
86 return wxFileType::MessageParameters::GetParamValue(name);
87 }
88};
89\end{verbatim}
90
91Now you only need to create an object of this class and pass it to, for example,
2432b92d 92\rtfsp\helpref{GetOpenCommand}{wxfiletypegetopencommand} like this:
b13d92d1
VZ
93
94\begin{verbatim}
95wxString command;
96if ( filetype->GetOpenCommand(&command,
08890e27 97 MailMessageParameters("foo.txt", "text/plain")) )
b13d92d1
VZ
98{
99 // the full command for opening the text documents is in 'command'
100 // (it might be "notepad foo.txt" under Windows or "cat foo.txt" under Unix)
101}
102else
103{
104 // we don't know how to handle such files...
105}
b13d92d1
VZ
106\end{verbatim}
107
108{\bf Windows:} As only the file name is used by the program associated with the
109given extension anyhow (but no other message parameters), there is no need to
110ever derive from MessageParameters class for a Windows-only program.
111
112\membersection{wxFileType::wxFileType}\label{wxfiletypewxfiletype}
2432b92d 113
b13d92d1
VZ
114\func{}{wxFileType}{\void}
115
116The default constructor is private because you should never create objects of
2432b92d 117this type: they are only returned by \helpref{wxMimeTypesManager}{wxmimetypesmanager} methods.
b13d92d1
VZ
118
119\membersection{wxFileType::\destruct{wxFileType}}\label{wxfiletypedtor}
2432b92d
JS
120
121\func{}{\destruct{wxFileType}}{\void}
b13d92d1
VZ
122
123The destructor of this class is not virtual, so it should not be derived from.
124
125\membersection{wxFileType::GetMimeType}\label{wxfiletypegetmimetype}
2432b92d
JS
126
127\func{bool}{GetMimeType}{\param{wxString*}{ mimeType}}
b13d92d1 128
cc81d32f 129If the function returns {\tt true}, the string pointed to by {\it mimeType} is filled
b13d92d1
VZ
130with full MIME type specification for this file type: for example, "text/plain".
131
4d2976ad
VS
132\membersection{wxFileType::GetMimeTypes}\label{wxfiletypegetmimetypes}
133
d17f05af 134\func{bool}{GetMimeType}{\param{wxArrayString\&}{ mimeTypes}}
4d2976ad
VS
135
136Same as \helpref{GetMimeType}{wxfiletypegetmimetype} but returns array of MIME
137types. This array will contain only one item in most cases but sometimes,
138notably under Unix with KDE, may contain more MIME types. This happens when
139one file extension is mapped to different MIME types by KDE, mailcap and
140mime.types.
141
b13d92d1 142\membersection{wxFileType::GetExtensions}\label{wxfiletypegetextensions}
2432b92d
JS
143
144\func{bool}{GetExtensions}{\param{wxArrayString\&}{ extensions}}
b13d92d1 145
cc81d32f 146If the function returns {\tt true}, the array {\it extensions} is filled
b13d92d1
VZ
147with all extensions associated with this file type: for example, it may
148contain the following two elements for the MIME type "text/html" (notice the
149absence of the leading dot): "html" and "htm".
150
151{\bf Windows:} This function is currently not implemented: there is no
152(efficient) way to retrieve associated extensions from the given MIME type on
cc81d32f 153this platform, so it will only return {\tt true} if the wxFileType object was created
b13d92d1
VZ
154by \helpref{GetFileTypeFromExtension}{wxmimetypesmanagergetfiletypefromextension}
155function in the first place.
156
157\membersection{wxFileType::GetIcon}\label{wxfiletypegeticon}
2432b92d 158
da0766ab 159\func{bool}{GetIcon}{\param{wxIconLocation *}{ iconLoc}}
b13d92d1 160
da0766ab
VZ
161If the function returns {\tt true}, the {\tt iconLoc} is filled with the
162location of the icon for this MIME type. A \helpref{wxIcon}{wxicon} may be
163created from {\it iconLoc} later.
164
165{\bf Windows:} The function returns the icon shown by Explorer for the files of
166the specified type.
167
168{\bf Mac:} This function is not implemented and always returns {\tt false}.
b13d92d1 169
cdf339c9
VS
170{\bf Unix:} MIME manager gathers information about icons from GNOME
171and KDE settings and thus GetIcon's success depends on availability
172of these desktop environments.
b13d92d1
VZ
173
174\membersection{wxFileType::GetDescription}\label{wxfiletypegetdescription}
2432b92d
JS
175
176\func{bool}{GetDescription}{\param{wxString*}{ desc}}
b13d92d1 177
cc81d32f 178If the function returns {\tt true}, the string pointed to by {\it desc} is filled
b13d92d1
VZ
179with a brief description for this file type: for example, "text document" for
180the "text/plain" MIME type.
181
182\membersection{wxFileType::GetOpenCommand}\label{wxfiletypegetopencommand}
2432b92d
JS
183
184\func{bool}{GetOpenCommand}{\param{wxString*}{ command}, \param{MessageParameters\&}{ params}}
b13d92d1 185
0532a258
VZ
186\func{wxString}{GetOpenCommand}{\param{const wxString\&}{ filename}}
187
cc81d32f 188With the first version of this method, if the {\tt true} is returned, the
0532a258
VZ
189string pointed to by {\it command} is filled with the command which must be
190executed (see \helpref{wxExecute}{wxexecute}) in order to open the file of the
191given type. In this case, the name of the file as well as any other parameters
192is retrieved from \helpref{MessageParameters}{wxfiletypemessageparameters}
193class.
194
195In the second case, only the filename is specified and the command to be used
196to open this kind of file is returned directly. An empty string is returned to
43e8916f 197indicate that an error occurred (typically meaning that there is no standard way
0532a258 198to open this kind of files).
b13d92d1
VZ
199
200\membersection{wxFileType::GetPrintCommand}\label{wxfiletypegetprintcommand}
2432b92d
JS
201
202\func{bool}{GetPrintCommand}{\param{wxString*}{ command},\param{MessageParameters\&}{ params}}
b13d92d1 203
cc81d32f 204If the function returns {\tt true}, the string pointed to by {\it command} is filled
b13d92d1
VZ
205with the command which must be executed (see \helpref{wxExecute}{wxexecute}) in
206order to print the file of the given type. The name of the file is
207retrieved from \helpref{MessageParameters}{wxfiletypemessageparameters} class.
208
209\membersection{wxFileType::ExpandCommand}\label{wxfiletypeexpandcommand}
2432b92d
JS
210
211\func{static wxString}{ExpandCommand}{\param{const wxString\&}{ command}, \param{MessageParameters\&}{ params}}
b13d92d1 212
2edb0bde 213This function is primarily intended for GetOpenCommand and GetPrintCommand
b13d92d1 214usage but may be also used by the application directly if, for example, you want
154b6b0f 215to use some non-default command to open the file.
b13d92d1 216
7335902d 217The function replaces all occurrences of
2432b92d 218
b13d92d1
VZ
219\twocolwidtha{7cm}
220\begin{twocollist}\itemsep=0pt
2edb0bde 221\twocolitem{format specification}{with}
b13d92d1
VZ
222\twocolitem{\%s}{the full file name}
223\twocolitem{\%t}{the MIME type}
224\twocolitem{\%\{param\}}{the value of the parameter {\it param}}
225\end{twocollist}
2432b92d 226
b13d92d1
VZ
227using the MessageParameters object you pass to it.
228
229If there is no '\%s' in the command string (and the string is not empty), it is
230assumed that the command reads the data on stdin and so the effect is the same
231as "< \%s" were appended to the string.
232
233Unlike all other functions of this class, there is no error return for this
234function.
2432b92d 235