]> git.saurik.com Git - wxWidgets.git/blame_incremental - docs/latex/wx/filetype.tex
typo
[wxWidgets.git] / docs / latex / wx / filetype.tex
... / ...
CommitLineData
1\section{\class{wxFileType}}\label{wxfiletype}
2
3This class holds information about a given {\it file type}. File type is the same as
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
10unknown so the return value of all the accessors {\bf must} be checked: {\tt false}
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.
16But it is your responsibility to delete the returned pointer when you're done
17with it!
18
19% TODO describe MIME types better than this...
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
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
32\wxheading{Derived from}
33
34None
35
36\wxheading{Include files}
37
38<wx/mimetype.h>
39
40\wxheading{Library}
41
42\helpref{wxBase}{librarieslist}
43
44\wxheading{See also}
45
46\helpref{wxMimeTypesManager}{wxmimetypesmanager}
47
48\latexignore{\rtfignore{\wxheading{Members}}}
49
50\membersection{MessageParameters class}\label{wxfiletypemessageparameters}
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
63requires the caller to provide the file name (always used by the program to be
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
71class MailMessageParameters : public wxFileType::MessageParameters
72{
73public:
74 MailMessageParameters(const wxString& filename,
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,
92\rtfsp\helpref{GetOpenCommand}{wxfiletypegetopencommand} like this:
93
94\begin{verbatim}
95wxString command;
96if ( filetype->GetOpenCommand(&command,
97 MailMessageParameters("foo.txt", "text/plain")) )
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}
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}
113
114\func{}{wxFileType}{\void}
115
116The default constructor is private because you should never create objects of
117this type: they are only returned by \helpref{wxMimeTypesManager}{wxmimetypesmanager} methods.
118
119\membersection{wxFileType::\destruct{wxFileType}}\label{wxfiletypedtor}
120
121\func{}{\destruct{wxFileType}}{\void}
122
123The destructor of this class is not virtual, so it should not be derived from.
124
125\membersection{wxFileType::GetMimeType}\label{wxfiletypegetmimetype}
126
127\func{bool}{GetMimeType}{\param{wxString*}{ mimeType}}
128
129If the function returns {\tt true}, the string pointed to by {\it mimeType} is filled
130with full MIME type specification for this file type: for example, "text/plain".
131
132\membersection{wxFileType::GetMimeTypes}\label{wxfiletypegetmimetypes}
133
134\func{bool}{GetMimeType}{\param{wxArrayString\&}{ mimeTypes}}
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
142\membersection{wxFileType::GetExtensions}\label{wxfiletypegetextensions}
143
144\func{bool}{GetExtensions}{\param{wxArrayString\&}{ extensions}}
145
146If the function returns {\tt true}, the array {\it extensions} is filled
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
153this platform, so it will only return {\tt true} if the wxFileType object was created
154by \helpref{GetFileTypeFromExtension}{wxmimetypesmanagergetfiletypefromextension}
155function in the first place.
156
157\membersection{wxFileType::GetIcon}\label{wxfiletypegeticon}
158
159\func{bool}{GetIcon}{\param{wxIconLocation *}{ iconLoc}}
160
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}.
169
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.
173
174\membersection{wxFileType::GetDescription}\label{wxfiletypegetdescription}
175
176\func{bool}{GetDescription}{\param{wxString*}{ desc}}
177
178If the function returns {\tt true}, the string pointed to by {\it desc} is filled
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}
183
184\func{bool}{GetOpenCommand}{\param{wxString*}{ command}, \param{MessageParameters\&}{ params}}
185
186\func{wxString}{GetOpenCommand}{\param{const wxString\&}{ filename}}
187
188With the first version of this method, if the {\tt true} is returned, the
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
197indicate that an error occurred (typically meaning that there is no standard way
198to open this kind of files).
199
200\membersection{wxFileType::GetPrintCommand}\label{wxfiletypegetprintcommand}
201
202\func{bool}{GetPrintCommand}{\param{wxString*}{ command},\param{MessageParameters\&}{ params}}
203
204If the function returns {\tt true}, the string pointed to by {\it command} is filled
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}
210
211\func{static wxString}{ExpandCommand}{\param{const wxString\&}{ command}, \param{MessageParameters\&}{ params}}
212
213This function is primarily intended for GetOpenCommand and GetPrintCommand
214usage but may be also used by the application directly if, for example, you want
215to use some non-default command to open the file.
216
217The function replaces all occurrences of
218
219\twocolwidtha{7cm}
220\begin{twocollist}\itemsep=0pt
221\twocolitem{format specification}{with}
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}
226
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.
235