add some more content to the overview section

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@12456 f5534014-38df-0310-8fa8-9805f1628bb7

diff --git a/docbook/edg_src/EDG_chapter_works.xml b/docbook/edg_src/EDG_chapter_works.xml
index 45faeb5fd98254868086e8a050d0227605598baf..f01673f553a0ca87a93a243ff3a0cc0510a7156e 100644 (file)
--- a/docbook/edg_src/EDG_chapter_works.xml
+++ b/docbook/edg_src/EDG_chapter_works.xml
@@ -21,7 +21,87 @@
          </title>\r
          <graphic entityref="EtherealFunctionBlocks" format="PNG"/>\r
        </figure>\r
-       XXX - describe the blocks in detail\r
+       </para>\r
+       <para>\r
+       The function blocks in more detail:\r
+       <variablelist>\r
+         <varlistentry><term><command>GTK 1/2</command></term>\r
+           <listitem>\r
+             <para>\r
+                 Handling of all user input/output (all windows, dialogs and such). \r
+                 Source code can be found in the <filename>gtk</filename> directory.\r
+             </para>\r
+           </listitem>\r
+         </varlistentry>\r
+         <varlistentry><term><command>Core</command></term>\r
+           <listitem>\r
+             <para>\r
+                 Main "glue code" that holds the other blocks together, source \r
+                 code can be found in the root directory.\r
+             </para>\r
+           </listitem>\r
+         </varlistentry>\r
+         <varlistentry><term><command>Epan</command></term>\r
+           <listitem>\r
+             <para>\r
+                 Ethereal Package ANalyzing (XXX - is this correct?) the packet \r
+                 analyzing engine, source code can be found in the \r
+                 <filename>epan</filename> directory.\r
+             </para>\r
+         <itemizedlist>\r
+           <listitem>\r
+             <para>\r
+                 Protocol-Tree - Keep data of the capture file protocol information.\r
+             </para>\r
+           </listitem>\r
+           <listitem>\r
+             <para>\r
+                 Dissectors - The various protocol dissectors in \r
+                 <filename>epan/dissectors</filename>.\r
+             </para>\r
+           </listitem>\r
+           <listitem>\r
+             <para>\r
+                 Plugins - Some of the protocol dissectors are implemented as plugins, source \r
+                 code at <filename>plugins</filename>.\r
+             </para>\r
+           </listitem>\r
+           <listitem>\r
+             <para>\r
+                 Display-Filters - the display filter engine at \r
+                 <filename>epan/dfilter</filename>.\r
+             </para>\r
+           </listitem>\r
+         </itemizedlist>\r
+           </listitem>\r
+         </varlistentry>\r
+         <varlistentry><term><command>Capture</command></term>\r
+           <listitem>\r
+             <para>\r
+                 Capture engine.\r
+             </para>\r
+           </listitem>\r
+         </varlistentry>\r
+         <varlistentry><term><command>Wiretap</command></term>\r
+           <listitem>\r
+             <para>\r
+                 The wiretap library is used to read/write capture files in libpcap \r
+                 and a lot of other file formats, the source code is in the\r
+                 <filename>wiretap</filename> directory.\r
+             </para>\r
+           </listitem>\r
+         </varlistentry>\r
+         <varlistentry>\r
+         <term><command>Win-/libpcap (not part of the Ethereal package)</command></term>\r
+           <listitem>\r
+             <para>\r
+                 The platform dependant packet capture library, including the capture \r
+                 filter engine. That's the reason why we still have different display \r
+                 and capture filter syntax, as two different filtering engines used.\r
+             </para>\r
+           </listitem>\r
+         </varlistentry>\r
+       </variablelist>\r
        </para>\r
   </section>\r
 \r