File: wx319.htm

package info (click to toggle)
wxwin2-doc 2.01-1
  • links: PTS
  • area: main
  • in suites: potato
  • size: 6,540 kB
  • ctags: 5,968
  • sloc: cpp: 15,157; makefile: 434; sh: 6
file content (23 lines) | stat: -rw-r--r-- 1,270 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
<HTML>
<head><title>Why use wxPython?</title></head>

<BODY BGCOLOR=#FFFFFF>
<A NAME="wxpwhy"></A><CENTER>
<A HREF="wx.htm"><img align=center src="contents.gif" BORDER=0 ALT="Contents"></A> <A HREF="wx317.htm#wxPython"><img align=center src="up.gif" BORDER=0 ALT="Up"></A> <A HREF="wx318.htm#wxpwhat"><img align=center src="back.gif" BORDER=0 ALT="Previous"></A> <A HREF="wx320.htm#wxpother"><img align=center src="forward.gif" BORDER=0 ALT="Next"></A> </CENTER><HR>

<H2>Why use wxPython?</H2>
<P>
So why would you want to use wxPython over just C++ and wxWindows?
Personally I prefer using Python for everything. I only use C++ when
I absolutely have to eek more performance out of an algorithm, and even
then I ususally code it as an extension module and leave the majority
of the program in Python.<P>
Another good thing to use wxPython for is quick prototyping of your
wxWindows apps.  With C++ you have to continuously go though the
edit-compile-link-run cycle, which can be quite time comsuming.  With
Python it is only an edit-run cycle.  You can easily build an
application in a few hours with Python that would normally take a few
days or longer with C++.  Converting a wxPython app to a C++/wxWindows app
should be a straight forward task.<P>

</BODY></HTML>