Programs Using Wxwidgets Python

What is wxPython? Is a cross-platform GUI toolkit for the programming language. It allows Python programmers to create programs with a robust, highly functional graphical user interface, simply and easily. It is implemented as a set of Python extension modules that wrap the GUI components of the popular cross platform library, which is written in C++. Like Python and wxWidgets, wxPython is Open Source, which means that it is free for anyone to use and the source code is available for anyone to look at and modify.

The earliest I can get hold of a Min. 5 system is on monday. Detailed description of the capabilities of the VBScript RegExp Object. Programs Using Wxwidgets Python. Download - Update. Star - Update. Download the. Free trial version below to get started. Double- click the downloaded.

And anyone can contribute fixes or enhancements to the project. WxPython is a cross-platform toolkit. This means that the same program will run on multiple platforms without modification. Currently Supported platforms are Microsoft Windows, Mac OS X and macOS, and Linux or other unix-like systems with GTK2 or GTK3 libraries. In most cases the native widgets are used on each platform to provide a 100% native look and feel for the application. Since the programming language is Python, wxPython programs are simple, easy to write and easy to understand.

Hello World, Part 2 Okay, now let's put a little more flesh on the bones of that Hello World sample to give a little better idea of what creating a wxPython application is all about. The finished application looks like these screenshots when run: And here is the source code.

The docstrings and the comments in the code will help you understand what it is doing. #!/bin/python '' Hello World, but with more meat. '' import wx class HelloFrame ( wx. Frame ): '' A Frame that says Hello World '' def __init__ ( self, * args, ** kw ): # ensure the parent's __init__ is called super ( HelloFrame, self ). __init__ ( * args, ** kw ) # create a panel in the frame pnl = wx. Panel ( self ) # and put some text with a larger bold font on it st = wx.

StaticText ( pnl, label = 'Hello World!' , pos = ( 25, 25 )) font = st. GetFont () font. The Sims 3 Isola Da Sogno Torrent Multi more. PointSize += 10 font = font.

SetFont ( font ) # create a menu bar self. MakeMenuBar () # and a status bar self. CreateStatusBar () self. SetStatusText ( 'Welcome to wxPython!' ) def makeMenuBar ( self ): '' A menu bar is composed of menus, which are composed of menu items. This method builds a set of menus and binds handlers to be called when the menu item is selected.

'' # Make a file menu with Hello and Exit items fileMenu = wx. Menu () # The ' t.' Syntax defines an accelerator key that also triggers # the same event helloItem = fileMenu. Append ( - 1, '&Hello.

T Ctrl-H', 'Help string shown in status bar for this menu item' ) fileMenu. AppendSeparator () # When using a stock ID we don't need to specify the menu item's # label exitItem = fileMenu. ID_EXIT ) # Now a help menu for the about item helpMenu = wx. Menu () aboutItem = helpMenu.

ID_ABOUT ) # Make the menu bar and add the two menus to it. The '&' defines # that the next letter is the 'mnemonic' for the menu item. On the # platforms that support it those letters are underlined and can be # triggered from the keyboard. MenuBar = wx.

MenuBar () menuBar. Append ( fileMenu, '&File' ) menuBar. Append ( helpMenu, '&Help' ) # Give the menu bar to the frame self.

SetMenuBar ( menuBar ) # Finally, associate a handler function with the EVT_MENU event for # each of the menu items. That means that when that menu item is # activated then the associated handler function will be called. EVT_MENU, self. OnHello, helloItem ) self.

EVT_MENU, self. OnExit, exitItem ) self.

EVT_MENU, self. OnAbout, aboutItem ) def OnExit ( self, event ): ''Close the frame, terminating the application.' Close ( True ) def OnHello ( self, event ): ''Say hello to the user.' MessageBox ( 'Hello again from wxPython' ) def OnAbout ( self, event ): ''Display an About Dialog'' wx.

MessageBox ( 'This is a wxPython Hello World sample', 'About Hello World 2', wx. ICON_INFORMATION ) if __name__ == '__main__': # When this module is run (not imported) then create the app, the # frame, show it, and start the event loop. App () frm = HelloFrame ( None, title = 'Hello World 2' ) frm.

This topic was written by Robin Dunn, author of the wrapper. What is wxPython? WxPython is a blending of the wxWidgets GUI classes and the Python programming language. Python So what is Python? Go to to learn more, but in a nutshell Python is an interpreted, interactive, object-oriented programming language.

It is often compared to Tcl, Perl, Scheme or Java. Python combines remarkable power with very clear syntax. It has modules, classes, exceptions, very high level dynamic data types, and dynamic typing. There are interfaces to many system calls and libraries, and new built-in modules are easily written in C or C++. Python is also usable as an extension language for applications that need a programmable interface. Python is copyrighted but freely usable and distributable, even for commercial use.

WxPython wxPython is a Python package that can be imported at runtime that includes a collection of Python modules and an extension module (native code). It provides a series of Python classes that mirror (or shadow) many of the wxWidgets GUI classes.

This extension module attempts to mirror the class hierarchy of wxWidgets as closely as possible. This means that there is a class in wxPython that looks, smells, tastes and acts almost the same as the class in the C++ version. WxPython is very versatile.

It can be used to create standalone GUI applications, or in situations where Python is embedded in a C++ application as an internal scripting or macro language. Currently wxPython is available for Win32 platforms and the GTK toolkit (wxGTK) on most Unix/X-windows platforms. See the wxPython website for details about getting wxPython working for you. Why Use wxPython? So why would you want to use wxPython over just C++ and wxWidgets? Personally I prefer using Python for everything.

I only use C++ when I absolutely have to eke more performance out of an algorithm, and even then I usually code it as an extension module and leave the majority of the program in Python. Another good thing to use wxPython for is quick prototyping of your wxWidgets apps. With C++ you have to continuously go though the edit-compile-link-run cycle, which can be quite time consuming. 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++/wxWidgets app should be a straight forward task. Other Python GUIs There are other GUI solutions out there for Python. Tkinter Tkinter is the de facto standard GUI for Python. It is available on nearly every platform that Python and Tcl/TK are. Well because Tkinter is just a wrapper around Tcl's GUI toolkit, Tk. This has its upsides and its downsides. The upside is that Tk is a pretty versatile toolkit.

It can be made to do a lot of things in a lot of different environments. It is fairly easy to create new widgets and use them interchangeably in your programs. The downside is Tcl. When using Tkinter you actually have two separate language interpreters running, the Python interpreter and the Tcl interpreter for the GUI. Since the guts of Tcl is mostly about string processing, it is fairly slow as well.

(Not too bad on a fast Pentium II, but you really notice the difference on slower machines.) It wasn't until the latest version of Tcl/Tk that native Look and Feel was possible on non-Motif platforms. This is because Tk usually implements its own widgets (controls) even when there are native controls available. Tkinter is a pretty low-level toolkit. You have to do a lot of work (verbose program code) to do things that would be much simpler with a higher level of abstraction. PythonWin PythonWin is an add-on package for Python for the Win32 platform. It includes wrappers for MFC as well as much of the Win32 API.

Because of its foundation, it is very familiar for programmers who have experience with MFC and the Win32 API. It is obviously not compatible with other platforms and toolkits. PythonWin is organized as separate packages and modules so you can use the pieces you need without having to use the GUI portions. Others There are quite a few other GUI modules available for Python, some in active use, some that haven't been updated for ages. Most are simple wrappers around some C or C++ toolkit or another, and most are not cross-platform compatible. See for a listing of a few of them. Using wxPython I'm not going to try and teach the Python language here.

You can do that at the. I'm also going to assume that you know a bit about wxWidgets already, enough to notice the similarities in the classes used. Take a look at the following wxPython program. You can find a similar program in the wxPython/demo directory, named DialogUnits.py. If your Python and wxPython are properly installed, you should be able to run it by issuing this command. 74: Things to Notice At line 2 the wxPython classes, constants, and etc. Are imported into the current module's namespace.

If you prefer to reduce namespace pollution you can use 'from wxPython import wx' and then access all the wxPython identifiers through the wx module, for example, 'wx.wxFrame'. At line 13 the frame's sizing and moving events are connected to methods of the class. These helper functions are intended to be like the event table macros that wxWidgets employs. But since static event tables are impossible with wxPython, we use helpers that are named the same to dynamically build the table. The only real difference is that the first argument to the event helpers is always the window that the event table entry should be added to. Notice the use of wxDLG_PNT and wxDLG_SZE in lines 19-29 to convert from dialog units to pixels.

These helpers are unique to wxPython since Python can't do method overloading like C++. There is an OnCloseWindow method at line 34 but no call to EVT_CLOSE to attach the event to the method.

Does it really get called? The answer is, yes it does. This is because many of the standard events are attached to windows that have the associated standard method names. I have tried to follow the lead of the C++ classes in this area to determine what is standard but since that changes from time to time I can make no guarantees, nor will it be fully documented. When in doubt, use an EVT_*** function. At lines 17 to 21 notice that there are no saved references to the panel or the static text items that are created.

Those of you who know Python might be wondering what happens when Python deletes these objects when they go out of scope. Do they disappear from the GUI? Remember that in wxPython the Python objects are just shadows of the corresponding C++ objects. Once the C++ windows and controls are attached to their parents, the parents manage them and delete them when necessary.

For this reason, most wxPython objects do not need to have a del method that explicitly causes the C++ object to be deleted. If you ever have the need to forcibly delete a window, use the Destroy() method as shown on line 36. Just like wxWidgets in C++, wxPython apps need to create a class derived from (line 56) that implements a method named OnInit, (line 59.) This method should create the application's main window (line 62) and show it. And finally, at line 72 an instance of the application class is created. At this point wxPython finishes initializing itself, and calls the OnInit method to get things started.

(The zero parameter here is a flag for functionality that isn't quite implemented yet. Just ignore it for now.) The call to MainLoop at line 73 starts the event loop which continues until the application terminates or all the top level windows are closed.

Classes Implemented in wxPython The following classes are supported in wxPython. Most provide nearly full implementations of the public interfaces specified in the C++ documentation, others are less so. They will all be brought as close as possible to the C++ spec over time. • • • • • • • wxBMPHandler • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • wxGIFHandler • • • • • • • • • • • • • • • • • • • • • • • • wxJPEGHandler • • • • • • • • • • • • • • • • • • • • • • • • wxNotebookEvent • • • • • • • • • wxPNGHandler • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • wxToolBarTool • • • • • • • • • • • Where to Go for Help Since wxPython is a blending of multiple technologies, help comes from multiple sources. See for details on various sources of help, but probably the best source is the wxPython-users mail list. You can view the archive or subscribe by going to Or you can send mail directly to the list using this address: Generated on Fri May 19 2017 23:00:07 for wxWidgets by 1.8.8.