[svn r3383] r3695@delle: sbehnel | 2008-03-03 08:51:17 +0100

 doc updates

--HG--
branch : trunk

3 files changed, 25 insertions, 20 deletions

diff --git a/doc/build.txt b/doc/build.txt
index e219c64f..dc382da4 100644
--- a/doc/build.txt
+++ b/doc/build.txt
@@ -58,11 +58,13 @@ the current developer version by calling::
 
   svn co http://codespeak.net/svn/lxml/trunk lxml
 
-This will create a directory ``lxml`` and download the source into it.  You
-can also `browse the repository through the web`_ or use your favourite SVN
-client to access it.
+This will create a directory ``lxml`` and download the source into it.
+You can also browse the `Subversion repository`_ through the web, use
+your favourite SVN client to access it, or browse the `Subversion
+history`_.
 
-.. _`browse the repository through the web`: http://codespeak.net/svn/lxml
+.. _`Subversion repository`: http://codespeak.net/svn/lxml/
+.. _`Subversion history`: https://codespeak.net/viewvc/lxml/
 
 
 Setuptools
diff --git a/doc/lxml-source-howto.txt b/doc/lxml-source-howto.txt
index 8383f85f..7e000e45 100644
--- a/doc/lxml-source-howto.txt
+++ b/doc/lxml-source-howto.txt
@@ -153,8 +153,9 @@ written out into an HTML documentation site.
 lxml.etree
 ==========
 
-The main module, ``lxml.etree``, is in the file **lxml.etree.pyx**.
-It implements the main functions and types of the ElementTree API, as
+The main module, ``lxml.etree``, is in the file `lxml.etree.pyx
+<http://codespeak.net/svn/lxml/trunk/src/lxml/lxml.etree.pyx>`_.  It
+implements the main functions and types of the ElementTree API, as
 well as all the factory functions for proxies.  It is the best place
 to start if you want to find out how a specific feature is
 implemented.
@@ -219,6 +220,12 @@ public-api.pxi
     modules at the C level.  For example, ``lxml.objectify`` makes use
     of these.  See the `C-level API` documentation.
 
+readonlytree.pxi
+    A separate read-only implementation of the Element API.  This is
+    used in places where non-intrusive access to a tree is required,
+    such as the ``PythonElementClassLookup`` or XSLT extension
+    elements.
+
 saxparser.pxi
     SAX-like parser interfaces as known from ElementTree's TreeBuilder.
 
@@ -295,15 +302,8 @@ lxml.objectify
 
 A Cython implemented extension module that uses the public C-API of
 lxml.etree.  It provides a Python object-like interface to XML trees.
-
-
-lxml.pyclasslookup
-==================
-
-A Cython implemented extension module that uses the public C-API of
-lxml.etree.  It provides a class lookup scheme that duplicates lxml's
-ElementTree API in a very simple way to provide Python access to the
-tree *before* instantiating the real Python proxies in lxml.etree.
+The implementation resides in the file `lxml.objectify.pyx
+<http://codespeak.net/svn/lxml/trunk/src/lxml/lxml.objectify.pyx>`_.
 
 
 lxml.html
diff --git a/doc/main.txt b/doc/main.txt
index f1571850..0f0cbe5a 100644
--- a/doc/main.txt
+++ b/doc/main.txt
@@ -159,13 +159,16 @@ from svn directly, using a command like this::
 
   svn co http://codespeak.net/svn/lxml/trunk lxml
 
-You can also `browse it through the web`_.  Please read `how to build lxml
-from source`_ first.  The `latest CHANGES`_ of the developer version are also
-accessible.  You can check there if a bug you found has been fixed or a
-feature you want has been implemented in the latest trunk version.
+You can also browse the `Subversion repository`_ through the web, or
+take a look at the `Subversion history`_.  Please read `how to build lxml
+from source`_ first.  The `latest CHANGES`_ of the developer version
+are also accessible.  You can check there if a bug you found has been
+fixed or a feature you want has been implemented in the latest trunk
+version.
 
 .. _`how to build lxml from source`: build.html
-.. _`browse it through the web`: http://codespeak.net/svn/lxml
+.. _`Subversion repository`: http://codespeak.net/svn/lxml/
+.. _`Subversion history`: https://codespeak.net/viewvc/lxml/
 .. _`latest CHANGES`: http://codespeak.net/svn/lxml/trunk/CHANGES.txt