]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/filetype.tex
Compilation fixes
[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
32\wxheading{Required headers}
33
34#include <wx/mimetype.h>
35
36\wxheading{Derived from}
37
38No base class.
39
40\wxheading{See also}
41
42\helpref{wxMimeTypesManager}{wxmimetypesmanager}
43
44\latexignore{\rtfignore{\wxheading{Members}}}
45
46\membersection{MessageParameters class}{wxfiletypemessageparameters}
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
67class MailMessageParamaters : public wxFileType::MessageParameters
68{
69public:
70 MailMessageParamaters(const wxString& filename,
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,
88\helpref{GetOpenCommand}{wxfiletypegetopencommand} like this:
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}
102
103\end{verbatim}
104
105{\bf Windows:} As only the file name is used by the program associated with the
106given extension anyhow (but no other message parameters), there is no need to
107ever derive from MessageParameters class for a Windows-only program.
108
109\membersection{wxFileType::wxFileType}\label{wxfiletypewxfiletype}
110\func{}{wxFileType}{\void}
111
112The default constructor is private because you should never create objects of
113this type: they are only returned by
114\helpref{wxMimeTypesManager}{wxmimetypesmanager} methods.
115
116\membersection{wxFileType::\destruct{wxFileType}}\label{wxfiletypedtor}
117\func{}{\destruct{wxFileType}{\void}
118
119The destructor of this class is not virtual, so it should not be derived from.
120
121\membersection{wxFileType::GetMimeType}\label{wxfiletypegetmimetype}
122\func{bool}{GetMimeType}{\param{wxString *}{mimeType}}
123
124If the function returns TRUE, the string pointed to by {\it mimeType} is filled
125with full MIME type specification for this file type: for example, "text/plain".
126
127\membersection{wxFileType::GetExtensions}\label{wxfiletypegetextensions}
128\func{bool}{GetExtensions}{\param{wxArrayString \&}{extensions}}
129
130If the function returns TRUE, the array {\it extensions} is filled
131with all extensions associated with this file type: for example, it may
132contain the following two elements for the MIME type "text/html" (notice the
133absence of the leading dot): "html" and "htm".
134
135{\bf Windows:} This function is currently not implemented: there is no
136(efficient) way to retrieve associated extensions from the given MIME type on
137this platform, so it will only return TRUE if the wxFileType object was created
138by \helpref{GetFileTypeFromExtension}{wxmimetypesmanagergetfiletypefromextension}
139function in the first place.
140
141\membersection{wxFileType::GetIcon}\label{wxfiletypegeticon}
142\func{bool}{GetIcon}{\param{wxIcon *}{icon}}
143
144If the function returns TRUE, the icon associated with this file type will be
145created and assigned to the {\it icon} parameter.
146
147{\bf Unix:} This function always returns FALSE under Unix.
148
149\membersection{wxFileType::GetDescription}\label{wxfiletypegetdescription}
150\func{bool}{GetDescription}{\param{wxString *}{desc}}
151
152If the function returns TRUE, the string pointed to by {\it desc} is filled
153with a brief description for this file type: for example, "text document" for
154the "text/plain" MIME type.
155
156\membersection{wxFileType::GetOpenCommand}\label{wxfiletypegetopencommand}
157\func{bool}{GetOpenCommand}{\param{wxString *}{command},\param{MessageParameters \&}{params}}
158
159If the function returns TRUE, the string pointed to by {\it command} is filled
160with the command which must be executed (see \helpref{wxExecute}{wxexecute}) in
161order to open the file of the given type. The name of the file is
162retrieved from \helpref{MessageParameters}{wxfiletypemessageparameters} class.
163
164\membersection{wxFileType::GetPrintCommand}\label{wxfiletypegetprintcommand}
165\func{bool}{GetPrintCommand}{\param{wxString *}{command},\param{MessageParameters \&}{params}}
166
167If the function returns TRUE, the string pointed to by {\it command} is filled
168with the command which must be executed (see \helpref{wxExecute}{wxexecute}) in
169order to print the file of the given type. The name of the file is
170retrieved from \helpref{MessageParameters}{wxfiletypemessageparameters} class.
171
172\membersection{wxFileType::ExpandCommand}\label{wxfiletypeexpandcommand}
173\func{static wxString}{ExpandCommand}{\param{const wxString \&}{command},\param{MessageParameters \&}{params}}
174
175This function is primarly intended for GetOpenCommand and GetPrintCommand
176usage but may be also used by the application directly if, for example, you want
177to use some non default command to open the file.
178
179The function replaces all occurences of
180\twocolwidtha{7cm}
181\begin{twocollist}\itemsep=0pt
182\twocolitem{format specificator}{with}
183\twocolitem{\%s}{the full file name}
184\twocolitem{\%t}{the MIME type}
185\twocolitem{\%\{param\}}{the value of the parameter {\it param}}
186\end{twocollist}
187using the MessageParameters object you pass to it.
188
189If there is no '\%s' in the command string (and the string is not empty), it is
190assumed that the command reads the data on stdin and so the effect is the same
191as "< \%s" were appended to the string.
192
193Unlike all other functions of this class, there is no error return for this
194function.