]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/htmlcell.tex
added support for binary data to wxConfig (slightly modified patch 1736788)
[wxWidgets.git] / docs / latex / wx / htmlcell.tex
CommitLineData
bd330a69 1\subsection{Cells and Containers}\label{cells}
704a4b75
VS
2
3This article describes mechanism used by
22d6efa8
JS
4\helpref{wxHtmlWinParser}{wxhtmlwinparser} and
5\helpref{wxHtmlWindow}{wxhtmlwindow} to parse and display HTML documents.
704a4b75
VS
6
7\wxheading{Cells}
8
9You can divide any text (or HTML) into small fragments. Let's call these
10fragments {\bf cells}. Cell is for example one word, horizontal line, image
11or any other part of document. Each cell has width and height (except special
22d6efa8 12"magic" cells with zero dimensions - e.g. colour changers or font changers).
704a4b75
VS
13
14See \helpref{wxHtmlCell}{wxhtmlcell}.
15
16\wxheading{Containers}
17
18Container is kind of cell that may contain sub-cells. Its size depends
19on number and sizes of its sub-cells (and also depends on width of window).
20
21See \helpref{wxHtmlContainerCell}{wxhtmlcontainercell},
22\helpref{wxHtmlCell::Layout}{wxhtmlcelllayout}.
23
4215a438 24This image shows the cells and containers:
605d715d 25\helponly{\image{}{contbox.bmp}}
4215a438 26
704a4b75
VS
27\wxheading{Using Containers in Tag Handler}
28
22d6efa8 29\helpref{wxHtmlWinParser}{wxhtmlwinparser} provides a user-friendly way
f6bcfd97 30of managing containers. It is based on the idea of opening and closing containers.
704a4b75
VS
31
32Use \helpref{OpenContainer}{wxhtmlwinparseropencontainer} to open new
22d6efa8
JS
33a container {\it within an already opened container}. This new container is a
34{\it sub-container} of the old one. (If you want to create a new container with
35the same depth level you can call {\tt CloseContainer(); OpenContainer();}.)
704a4b75 36
2edb0bde 37Use \helpref{CloseContainer}{wxhtmlwinparserclosecontainer} to close the
22d6efa8 38container. This doesn't create a new container with same depth level but
704a4b75
VS
39it returns "control" to the parent container.
40
41See explanation:
605d715d 42\helponly{\image{}{cont.bmp}}
4215a438
VZ
43
44There clearly must be same number of calls to OpenContainer as to
45CloseContainer.
704a4b75
VS
46
47\wxheading{Example}
48
22d6efa8
JS
49This code creates a new paragraph (container at same depth level)
50with "Hello, world!":
704a4b75
VS
51
52\begin{verbatim}
53m_WParser -> CloseContainer();
54c = m_WParser -> OpenContainer();
55
4215a438
VZ
56m_WParser -> AddText("Hello, ");
57m_WParser -> AddText("world!");
704a4b75
VS
58
59m_WParser -> CloseContainer();
60m_WParser -> OpenContainer();
61\end{verbatim}
62
63and here is image of the situation:
605d715d 64\helponly{\image{}{hello.bmp}}
704a4b75 65
4215a438
VZ
66You can see that there was an opened container before the code was executed.
67We closed it, created our own container, then closed our container and opened
704a4b75 68new container. The result was that we had {\it same depth level} after
22d6efa8 69executing. This is general rule that should be followed by tag handlers:
704a4b75
VS
70leave depth level of containers unmodified (in other words, number of
71OpenContainer and CloseContainer calls should be same within \helpref{HandleTag}{wxhtmltaghandlerhandletag}'s body).
72
4215a438
VZ
73Notice that it would be usually better to use
74\helpref{wxHtmlContainerCell::InsertCell}{wxhtmlcontainercellinsertcell} instead
75of adding text to the parser directly.