]>
Commit | Line | Data |
---|---|---|
1 | % | |
2 | % automatically generated by HelpGen from | |
3 | % htmlparser.tex at 14/Mar/99 20:13:37 | |
4 | % | |
5 | ||
6 | \section{\class{wxHtmlParser}}\label{wxhtmlparser} | |
7 | ||
8 | This class handles the {\bf generic} parsing of HTML document: it scans | |
9 | the document and divide it into blocks of tags (where one block | |
10 | consists of begining and ending tag and of text between these | |
11 | two tags). | |
12 | ||
13 | It is independent from wxHtmlWindow and can be used as stand-alone parser | |
14 | (Julian Smart's idea of speech-only HTML viewer or wget-like utility - | |
15 | see InetGet sample for example). | |
16 | ||
17 | It uses system of tag handlers to parse the HTML document. Tag handlers | |
18 | are not staticaly shared by all instances but are created for each | |
19 | wxHtmlParser instance. The reason is that the handler may contain | |
20 | document-specific temporary data used during parsing (e.g. complicated | |
21 | structures like tables). | |
22 | ||
23 | Typically the user calls only the \helpref{Parse}{wxhtmlparserparse} method. | |
24 | ||
25 | \wxheading{Derived from} | |
26 | ||
27 | wxObject | |
28 | ||
29 | \wxheading{See also} | |
30 | ||
31 | \helpref{Cells Overview}{cells}, | |
32 | \helpref{Tag Handlers Overview}{handlers}, | |
33 | \helpref{wxHtmlTag}{wxhtmltag} | |
34 | ||
35 | \latexignore{\rtfignore{\wxheading{Members}}} | |
36 | ||
37 | \membersection{wxHtmlParser::wxHtmlParser}\label{wxhtmlparserwxhtmlparser} | |
38 | ||
39 | \func{}{wxHtmlParser}{\void} | |
40 | ||
41 | Constructor. | |
42 | ||
43 | \membersection{wxHtmlParser::AddTag}\label{wxhtmlparseraddtag} | |
44 | ||
45 | \func{void}{AddTag}{\param{const wxHtmlTag\& }{tag}} | |
46 | ||
47 | This may (and may not) be overwriten in derived class. | |
48 | ||
49 | This method is called each time new tag is about to be added. | |
50 | {\it tag} contains information about the tag. (See \helpref{wxHtmlTag}{wxhtmltag} | |
51 | for details.) | |
52 | ||
53 | Default (wxHtmlParser) behaviour is this: | |
54 | First it finds a handler capable of handling this tag and then it calls | |
55 | handler's HandleTag method. | |
56 | ||
57 | \membersection{wxHtmlParser::AddTagHandler}\label{wxhtmlparseraddtaghandler} | |
58 | ||
59 | \func{virtual void}{AddTagHandler}{\param{wxHtmlTagHandler }{*handler}} | |
60 | ||
61 | Adds handler to the internal list (\& hash table) of handlers. This | |
62 | method should not be called directly by user but rather by derived class' | |
63 | constructor. | |
64 | ||
65 | This adds the handler to this {\bf instance} of wxHtmlParser, not to | |
66 | all objects of this class! (Static front-end to AddTagHandler is provided | |
67 | by wxHtmlWinParser). | |
68 | ||
69 | All handlers are deleted on object deletion. | |
70 | ||
71 | \membersection{wxHtmlParser::AddText}\label{wxhtmlparseraddword} | |
72 | ||
73 | \func{virtual void}{AddWord}{\param{const char* }{txt}} | |
74 | ||
75 | Must be overwriten in derived class. | |
76 | ||
77 | This method is called by \helpref{DoParsing}{wxhtmlparserdoparsing} | |
78 | each time a part of text is parsed. {\it txt} is NOT only one word, it is | |
79 | substring of input. It is not formatted or preprocessed (so white spaces are | |
80 | unmodified). | |
81 | ||
82 | \membersection{wxHtmlParser::DoParsing}\label{wxhtmlparserdoparsing} | |
83 | ||
84 | \func{void}{DoParsing}{\param{int }{begin\_pos}, \param{int }{end\_pos}} | |
85 | ||
86 | \func{void}{DoParsing}{\void} | |
87 | ||
88 | Parses the m\_Source from begin\_pos to end\_pos-1. | |
89 | (in noparams version it parses whole m\_Source) | |
90 | ||
91 | \membersection{wxHtmlParser::DoneParser}\label{wxhtmlparserdoneparser} | |
92 | ||
93 | \func{virtual void}{DoneParser}{\void} | |
94 | ||
95 | This must be called after DoParsing(). | |
96 | ||
97 | \membersection{wxHtmlParser::GetFS}\label{wxhtmlparsergetfs} | |
98 | ||
99 | \constfunc{wxFileSystem*}{GetFS}{\void} | |
100 | ||
101 | Returns pointer to the file system. Because each tag handler has | |
102 | reference to it's parent parser it can easily request the file by | |
103 | calling | |
104 | ||
105 | \begin{verbatim} | |
106 | wxFSFile *f = m_Parser -> GetFS() -> OpenFile("image.jpg"); | |
107 | \end{verbatim} | |
108 | ||
109 | \membersection{wxHtmlParser::GetProduct}\label{wxhtmlparsergetproduct} | |
110 | ||
111 | \func{virtual wxObject*}{GetProduct}{\void} | |
112 | ||
113 | Returns product of parsing. Returned value is result of parsing | |
114 | of the document. The type of this result depends on internal | |
115 | representation in derived parser (but it must be derived from wxObject!). | |
116 | ||
117 | See wxHtmlWinParser for details. | |
118 | ||
119 | \membersection{wxHtmlParser::GetSource}\label{wxhtmlparsergetsource} | |
120 | ||
121 | \func{wxString*}{GetSource}{\void} | |
122 | ||
123 | Returns pointer to the source being parsed. | |
124 | ||
125 | \membersection{wxHtmlParser::GetTempData}\label{wxhtmlparsergettempdata} | |
126 | ||
127 | \func{virtual wxList*}{GetTempData}{\void} | |
128 | ||
129 | This method returns list of wxObjects that represents | |
130 | all data allocated by the parser. These can't be freed | |
131 | by the destructor because they must be valid as long as | |
132 | GetProduct's return value is valid - the caller must | |
133 | explicitly call | |
134 | ||
135 | \begin{verbatim} | |
136 | delete (MyParser -> GetTempData()); | |
137 | \end{verbatim} | |
138 | ||
139 | to free the memory (this method always sets the list to delete its contents). | |
140 | ||
141 | \wxheading{Example} | |
142 | ||
143 | Why is this neccessary? Imagine wxHtmlWinParser: when handling | |
144 | a FONT tag it creates some fonts. These fonts are then used by wxHtmlWindow | |
145 | to display the text. But the wxHtmWinParser object is needed only when parsing | |
146 | the document - it may be deleted then. But fonts CAN'T be deleted - they | |
147 | must exist as long as the window is displaying text. | |
148 | ||
149 | GetTempData() solves the problem. | |
150 | ||
151 | \membersection{wxHtmlParser::InitParser}\label{wxhtmlparserinitparser} | |
152 | ||
153 | \func{virtual void}{InitParser}{\param{const wxString\& }{source}} | |
154 | ||
155 | Setups the parser for parsing the {\it source} string. (Should be overriden | |
156 | in derived class) | |
157 | ||
158 | \membersection{wxHtmlParser::Parse}\label{wxhtmlparserparse} | |
159 | ||
160 | \func{wxObject*}{Parse}{\param{const wxString\& }{source}} | |
161 | ||
162 | Proceeds parsing of the document. This is end-user method. You can simply | |
163 | call it when you need to obtain parsed output (which is parser-specific) | |
164 | ||
165 | The method does these things: | |
166 | ||
167 | \begin{enumerate} | |
168 | \item calls \helpref{InitParser(source)}{wxhtmlparserinitparser} | |
169 | \item calls \helpref{DoParsing}{wxhtmlparserdoparsing} | |
170 | \item calls \helpref{GetProduct}{wxhtmlparsergetproduct} | |
171 | \item calls \helpref{DoneParser}{wxhtmlparserdoneparser} | |
172 | \item returns value returned by GetProduct | |
173 | \end{enumerate} | |
174 | ||
175 | You shouldn't use InitParser, DoParsing, GetProduct or DoneParser directly. | |
176 | ||
177 | \membersection{wxHtmlParser::SetFS}\label{wxhtmlparsersetfs} | |
178 | ||
179 | \func{void}{SetFS}{\param{wxFileSystem }{*fs}} | |
180 | ||
181 | Sets the virtual file system that will be used to request additional | |
182 | files. (For example {\tt <IMG>} tag handler requests wxFSFile with the | |
183 | image data.) | |
184 |