Applied new master define for CommandBar vs. PocketPC mixed bar.

[wxWidgets.git] / wxPython / SWIG / README.txt

diff --git a/wxPython/SWIG/README.txt b/wxPython/SWIG/README.txt
index 59fb0b59ec2c58180edc84276a40ac5871b6bb9b..83bcaf7763aa7ca2e4379eaf4135aba49d1725ba 100644 (file)
--- a/wxPython/SWIG/README.txt
+++ b/wxPython/SWIG/README.txt
@@ -8,6 +8,16 @@ wxPython.  These have been submitted to SWIG's SourceForge patch
 tracker, so hopefully they will get incorporated into the main SWIG
 source tree soon.
 
+wxPython currently uses the 20-Feb-2004 version of SWIG.  You can get
+that version from their CVS using these commands::
+
+
+    cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/swig login
+    <press ENTER for empty password>
+
+    cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/swig \
+       checkout -D 20-FEB-2004 SWIG
+
 
 ------------------------------------------------------------------------
 
@@ -21,6 +31,38 @@ swig.python-docstring.patch  Adds "autodoc" and "docstring" features.
                             pythoncode to the begining of a
                             SWIG-generated proxy function or method.
 
+                            Add support for two new options to the
+                            %module directive.  The first allows you
+                            to specify a docstring for the proxy
+                            module, you use it like this::
+
+                              %module(docstring="blah") modulename
+
+                            And then when generating the
+                            modulename.py file SWIG will make a
+                            docstring using the value given.  
+
+                            The second %module option allows you to
+                            specify the name of the package that the
+                            module will live in.  This is useful when
+                            the .i file is %imported by other .i
+                            files.  If they are to live in separate
+                            packages then the importer can't do local
+                            imports of the importee.  If both modules
+                            have the same package name then nothing
+                            is generated differently than the current
+                            SWIG functionality.  If they are
+                            different then the package name of the
+                            importee is prepended to the import
+                            statement and the base class declarations
+                            in the importer.  For example::
+
+                              %module(pacakge="wx") _core
+
+                            Multiple %module options can be specfied,
+                            separated by commmas.
+
+
 swig.xmlout.patch           Fixes a couple problems in the XML output
                             of SWIG: an extra "/>" was removed and
                             newlines in attribute values were changed