wxWidgets

History

Robin Dunn 3734a86630 If a wxPy[Command]Event has been cloned then we need to propogate the Skip value from the original back to the clone after it has been processed. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@22424 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775		2003-07-31 19:21:48 +00:00
..
contrib	build fixes and reSWIGs for wxMSW	2003-07-25 02:32:46 +00:00
demo	Various testing changes	2003-07-31 19:21:05 +00:00
distrib	User the version number in the dir name of the private wxWindows install.	2003-07-18 02:28:09 +00:00
distutils
docs	wxPython Merge #2 of 2.4 branch --> HEAD (branch tag: wxPy_2_4_merge_2)	2003-07-02 23:13:10 +00:00
samples	wxPython Merge #2 of 2.4 branch --> HEAD (branch tag: wxPy_2_4_merge_2)	2003-07-02 23:13:10 +00:00
scripts	wxPython Merge #2 of 2.4 branch --> HEAD (branch tag: wxPy_2_4_merge_2)	2003-07-02 23:13:10 +00:00
src	If a wxPy[Command]Event has been cloned then we need to propogate the	2003-07-31 19:21:48 +00:00
wx	wxPython Merge #2 of 2.4 branch --> HEAD (branch tag: wxPy_2_4_merge_2)	2003-07-02 23:13:10 +00:00
wxPython	Allways need an App object now	2003-07-29 18:51:17 +00:00
wxSWIG	wxPython Merge #2 of 2.4 branch --> HEAD (branch tag: wxPy_2_4_merge_2)	2003-07-02 23:13:10 +00:00
.cvsignore	wxPython Merge #2 of 2.4 branch --> HEAD (branch tag: wxPy_2_4_merge_2)	2003-07-02 23:13:10 +00:00
b
b.bat
BUILD.osx.txt
BUILD.unix.txt
BUILD.win32.txt	wxPython Merge #2 of 2.4 branch --> HEAD (branch tag: wxPy_2_4_merge_2)	2003-07-02 23:13:10 +00:00
CHANGES.txt	Lots of changes for wxPython to start using many of the new featues in	2003-07-24 00:28:34 +00:00
MANIFEST.in	wxPython Merge #2 of 2.4 branch --> HEAD (branch tag: wxPy_2_4_merge_2)	2003-07-02 23:13:10 +00:00
README.txt
setup.cfg
setup.py	Use the separate contrib libs on MSW too.	2003-07-26 00:20:04 +00:00

README.txt

wxPython README
---------------

Welcome to the wonderful world of wxPython!

So where do you go from here?  The best thing to do is to run the demo
and use its source code to help you learn how to use wxPython.  Most
of the classes available are demonstrated there, and you can view the
sources directly in the demo so it is designed to help you learn.  If
you are on Windows or OS X then you can run the demo just by double
clicking it's icon.  If you are on Linux/Unix then change to the
directory containing the demo and type:

    python demo.py

There are also some sample mini applications available for you to run
and to play with as a learning exercise.

The next thing you should do is join the wxPython-users maillist where
you can interact with a community of other users and developers who
are willing to help you learn, answer questions and solve problems.
To join the mail list just send an email message to the following
address from the account you want to receive the mail messages from
the list:

    wxPython-users-subscribe@lists.wxwindows.org

There is also a good set of class reference documentation available
for wxPython, but currently it is geared for the C++ user.  This may
be a little daunting at first, but with a little practice you'll
easily be able to "translate" from the C++ shown there to Python.  Not
all classes documented are available in Python, but most of the GUI
related classes are.


Other Info
----------

Please also see the following files in this directory:

       CHANGES.txt         Information about new features, fixes,
                           etc. in each release.

       ../README.1st.txt   Instructions for building wxGTK and
                           wxPython on Unix-like platforms the
			   "new way."

       BUILD.unix.txt	   Instructions for building wxPython on
			   various Unix-like platforms the "old way."

       BUILD.win32.txt     Instructions for building wxPython on Windows.

       BUILD.osx.txt       Instructions for building wxPython on Mac OS X.

       licence/*           Text of the wxWindows license.



-----------------
Robin Dunn
robin@alldunn.com