]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/filetype.tex
*** empty log message ***
[wxWidgets.git] / docs / latex / wx / filetype.tex
CommitLineData
b13d92d1
VZ
1\section{\class{wxFileType}}\label{wxfiletype}
2
3This class holds information about a given "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: 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's your responsability to delete the returned pointer when you're done
17with it!
18
19% TODO describe MIME types better than this...
20A brief remainder about what the MIME types are (see the RFC 1341 for more
21information): basicly, it is just a pair category/type (for example,
22"text/plain") where the category is a basic indication of what a file is
23(examples 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
b13d92d1
VZ
32\wxheading{Derived from}
33
34No base class.
35
954b8ae6
JS
36\wxheading{Include files}
37
38<wx/mimetype.h>
39
b13d92d1
VZ
40\wxheading{See also}
41
42\helpref{wxMimeTypesManager}{wxmimetypesmanager}
43
44\latexignore{\rtfignore{\wxheading{Members}}}
45
6be663cf 46\membersection{MessageParameters class}\label{wxfiletypemessageparameters}
b13d92d1
VZ
47
48One of the most common usages of MIME is to encode an e-mail message. The MIME
49type of the encoded message is an example of a {\it message parameter}. These
50parameters are found in the message headers ("Content-XXX"). At the very least,
51they must specify the MIME type and the version of MIME used, but almost always
52they provide additional information about the message such as the original file
53name or the charset (for the text documents).
54
55These parameters may be useful to the program used to open, edit, view or print
56the message, so, for example, an e-mail client program will have to pass them to
57this program. Because wxFileType itself can not know about these parameters,
58it uses MessageParameters class to query them. The default implementation only
59requiers the caller to provide the file name (always used by the program to be
60called - it must know which file to open) and the MIME type and supposes that
61there are no other parameters. If you wish to supply additional parameters, you
62must derive your own class from MessageParameters and override GetParamValue()
63function, for example:
64
65\begin{verbatim}
66// provide the message parameters for the MIME type manager
2432b92d 67class MailMessageParameters : public wxFileType::MessageParameters
b13d92d1
VZ
68{
69public:
2432b92d 70 MailMessageParameters(const wxString& filename,
b13d92d1
VZ
71 const wxString& mimetype)
72 : wxFileType::MessageParameters(filename, mimetype)
73 {
74 }
75
76 virtual wxString GetParamValue(const wxString& name) const
77 {
78 // parameter names are not case-sensitive
79 if ( name.CmpNoCase("charset") == 0 )
80 return "US-ASCII";
81 else
82 return wxFileType::MessageParameters::GetParamValue(name);
83 }
84};
85\end{verbatim}
86
87Now you only need to create an object of this class and pass it to, for example,
2432b92d 88\rtfsp\helpref{GetOpenCommand}{wxfiletypegetopencommand} like this:
b13d92d1
VZ
89
90\begin{verbatim}
91wxString command;
92if ( filetype->GetOpenCommand(&command,
93 MailMessageParamaters("foo.txt", "text/plain")) )
94{
95 // the full command for opening the text documents is in 'command'
96 // (it might be "notepad foo.txt" under Windows or "cat foo.txt" under Unix)
97}
98else
99{
100 // we don't know how to handle such files...
101}
b13d92d1
VZ
102\end{verbatim}
103
104{\bf Windows:} As only the file name is used by the program associated with the
105given extension anyhow (but no other message parameters), there is no need to
106ever derive from MessageParameters class for a Windows-only program.
107
108\membersection{wxFileType::wxFileType}\label{wxfiletypewxfiletype}
2432b92d 109
b13d92d1
VZ
110\func{}{wxFileType}{\void}
111
112The default constructor is private because you should never create objects of
2432b92d 113this type: they are only returned by \helpref{wxMimeTypesManager}{wxmimetypesmanager} methods.
b13d92d1
VZ
114
115\membersection{wxFileType::\destruct{wxFileType}}\label{wxfiletypedtor}
2432b92d
JS
116
117\func{}{\destruct{wxFileType}}{\void}
b13d92d1
VZ
118
119The destructor of this class is not virtual, so it should not be derived from.
120
121\membersection{wxFileType::GetMimeType}\label{wxfiletypegetmimetype}
2432b92d
JS
122
123\func{bool}{GetMimeType}{\param{wxString*}{ mimeType}}
b13d92d1
VZ
124
125If the function returns TRUE, the string pointed to by {\it mimeType} is filled
126with full MIME type specification for this file type: for example, "text/plain".
127
128\membersection{wxFileType::GetExtensions}\label{wxfiletypegetextensions}
2432b92d
JS
129
130\func{bool}{GetExtensions}{\param{wxArrayString\&}{ extensions}}
b13d92d1
VZ
131
132If the function returns TRUE, the array {\it extensions} is filled
133with all extensions associated with this file type: for example, it may
134contain the following two elements for the MIME type "text/html" (notice the
135absence of the leading dot): "html" and "htm".
136
137{\bf Windows:} This function is currently not implemented: there is no
138(efficient) way to retrieve associated extensions from the given MIME type on
139this platform, so it will only return TRUE if the wxFileType object was created
140by \helpref{GetFileTypeFromExtension}{wxmimetypesmanagergetfiletypefromextension}
141function in the first place.
142
143\membersection{wxFileType::GetIcon}\label{wxfiletypegeticon}
2432b92d
JS
144
145\func{bool}{GetIcon}{\param{wxIcon*}{ icon}}
b13d92d1
VZ
146
147If the function returns TRUE, the icon associated with this file type will be
148created and assigned to the {\it icon} parameter.
149
150{\bf Unix:} This function always returns FALSE under Unix.
151
152\membersection{wxFileType::GetDescription}\label{wxfiletypegetdescription}
2432b92d
JS
153
154\func{bool}{GetDescription}{\param{wxString*}{ desc}}
b13d92d1
VZ
155
156If the function returns TRUE, the string pointed to by {\it desc} is filled
157with a brief description for this file type: for example, "text document" for
158the "text/plain" MIME type.
159
160\membersection{wxFileType::GetOpenCommand}\label{wxfiletypegetopencommand}
2432b92d
JS
161
162\func{bool}{GetOpenCommand}{\param{wxString*}{ command}, \param{MessageParameters\&}{ params}}
b13d92d1
VZ
163
164If the function returns TRUE, the string pointed to by {\it command} is filled
165with the command which must be executed (see \helpref{wxExecute}{wxexecute}) in
166order to open the file of the given type. The name of the file is
167retrieved from \helpref{MessageParameters}{wxfiletypemessageparameters} class.
168
169\membersection{wxFileType::GetPrintCommand}\label{wxfiletypegetprintcommand}
2432b92d
JS
170
171\func{bool}{GetPrintCommand}{\param{wxString*}{ command},\param{MessageParameters\&}{ params}}
b13d92d1
VZ
172
173If the function returns TRUE, the string pointed to by {\it command} is filled
174with the command which must be executed (see \helpref{wxExecute}{wxexecute}) in
175order to print the file of the given type. The name of the file is
176retrieved from \helpref{MessageParameters}{wxfiletypemessageparameters} class.
177
178\membersection{wxFileType::ExpandCommand}\label{wxfiletypeexpandcommand}
2432b92d
JS
179
180\func{static wxString}{ExpandCommand}{\param{const wxString\&}{ command}, \param{MessageParameters\&}{ params}}
b13d92d1
VZ
181
182This function is primarly intended for GetOpenCommand and GetPrintCommand
183usage but may be also used by the application directly if, for example, you want
184to use some non default command to open the file.
185
186The function replaces all occurences of
2432b92d 187
b13d92d1
VZ
188\twocolwidtha{7cm}
189\begin{twocollist}\itemsep=0pt
190\twocolitem{format specificator}{with}
191\twocolitem{\%s}{the full file name}
192\twocolitem{\%t}{the MIME type}
193\twocolitem{\%\{param\}}{the value of the parameter {\it param}}
194\end{twocollist}
2432b92d 195
b13d92d1
VZ
196using the MessageParameters object you pass to it.
197
198If there is no '\%s' in the command string (and the string is not empty), it is
199assumed that the command reads the data on stdin and so the effect is the same
200as "< \%s" were appended to the string.
201
202Unlike all other functions of this class, there is no error return for this
203function.
2432b92d 204