Harsh J

Memoirs of a QWERTY Keyboard

Archive for the ‘python’ tag

PyQt – Signals, Slots and Layouts Tutorial

18 comments

Note: If you’re new to using PyQt but are interested in great cross-platform GUI application development please read the PyQt Introduction article.

Having seen how a simple PyQt application code looks, let’s delve into user-interaction. We’ll learn about Qt’s signal-to-slot connection model for processing input and other events, and layouts for proper placement of widgets on a window.

The PyQt Class Hierarchy

PyQt is completely built upon the Object-Oriented concepts, so it is important to understand how all classes are related to each other in it.

Almost all GUI classes extend upon their Abstract class which defines common behaviour for similar widgets. These abstract classes, or any widget class, inherit QWidget, the base class of all drawable GUI components. QWidget inherits QObject, a class that has nothing to do with GUI but forms the base class of every PyQt class and helps provide the framework-related features.

The following hierarchy diagram depicts this clearly for the QPushButton class:

The QPushButton Class Hierarchy

The QPushButton Class Hierarchy

The QPaintDevice class helps draw (or paint) things on the screen, thus its also used with anything that’s drawable – We’ll learn more about Painting in a later article.

References: QWidget
Read the rest of this entry »

Written by Harsh

May 14th, 2009 at 11:37 am

Posted in Software

Tagged with , , , , ,

Ubuntu 9.04 Python 2.6 Site-Packages Directory

5 comments

Strangely the site-packages directory used by Python (2.6) to place/install modules and packages is nowhere to be found in Ubuntu’s Jaunty Jackalope. The newer directory is called dist-packages, no idea why (Only know that it sounds like its for distribution-installed modules).

So to place a package or a link to one, simply do so in the /usr/local/lib/python2.6/dist-packages/ directory.

Written by Harsh

May 13th, 2009 at 1:09 am

Posted in Linux,Software

Tagged with , ,

Basics of PyQt

one comment

Note: If you’re new to using PyQt but are interested in great cross-platform GUI application development please read the PyQt Introduction article.

This is a total beginners-only post. In this post, I will talk about what PyQt is, what it does and what are its major components you should know about before you start thinking about developing with it. I’ve made a simple Google Docs presentation about these and its viewable below or in full screen at this link.

Read the rest of this entry »

Written by Harsh

April 29th, 2009 at 9:34 am

Posted in Software

Tagged with , , , ,

The PyQt Intro

9 comments

This article is an introduction to the PyQt GUI Application Development Framework that uses Python and Nokia’s Qt.

Contents:

  1. Pretext
  2. Prerequisites
  3. Sample Code
  4. Breaking Down the Code
  5. Getting Further

Pretext

Ever wondered how to easily write good programs using Python? Programs that would run on any platform – from Windows to Mac OS X along with the various Linux variants? Programs that look good, look native, and also work great?

Here’s one solution – PyQt! With it you can create complete, working applications that may look like this:

Fresco - An application developed with PyQt4

Nokia’s Qt is a free (LGPL) cross-platform C++/Java based application-framework, with GUI being its most prominent feature.

PyQt is simply a python-binding to the C++ libraries that Qt provides. Using PyQt one can write neat looking GUI applications that do a lot, and do so easily.

Nokia's Qt 4

A series of articles, starting with this one will aim to tutor interested programmers into using this wonderful library, and developing applications with it.

Prerequisites

The most-minimal pre-requisites are:

  • Basic Python programming knowledge.
  • A little know-how about GUI and the event-based-programming concepts.

Two primary resources where we start from:

  1. Nokia’s Qt
  2. Riverbank Computing’s PyQt

Downloading and installing PyQt is fairly easy on Linux thanks to the various package managers. Do check out the download links at each of the above-mentioned links to get them on other platforms as well. Installation help is also provided by Riverbank Computing to help you set-up the PyQt4 library on your OS.

Sample Code

So let’s start off in the same style as almost everything do in a programmer’s perspective: Hello World!

Below is a well documented program for the same:


import sys

# Importing the necessary Qt classes.

from PyQt4.QtGui import QLabel, QApplication

# We use the from foo import * syntax here because
# all of Qt's objects begin with a Q
# and thus we shouldn't run into namespace problems.

if __name__=='__main__':

	App = QApplication(sys.argv)

	# All Qt programs need an
	# QApplication instance.

	# We pass the sys.argv as its arguments
	# because Qt is adept at handling some
	# of the default command-line options
	# like style, size, etc by itself.

	Label = QLabel( "Hello World!" )

	# QLabel is the class providing a
	# simple label

	Label.show()

	# Like in most GUI toolkits, we have
	# to manually set it to show

	App.exec_()

	# Notice the _ after exec, this is to
	# avoid the confusion with Python's
	# exec() built-in-function

	# exec_() starts the main application
	# loop. Something like main() of other
	# toolkits.

This is how it looks when run, a simple application that displays some popular text:

A simple Hello World application written with Qt

Breaking it down

The first thing we have initialized under our ‘__main__’ is the QApplication instance, App. Every GUI application needs this instance to be present. It handles the look and feel of the application and is the main thread of the same. Without it Qt will error out and not run any GUI.

Next we create a label. A label is a simple text-displaying widget used in many forms to describe the input fields and other things. In Qt, its called the QLabel and resides under the QtGui namespace. We create one with a simple Hello World text under the object name Label.

Now we call the show() method of the label so that it appears on the screen. This method is applicable to all QWidget-class children, and QLabel is one among them. Calling show() draws the label widget’s window on the screen.

Finally, we start the application loop, the one responsible for making an application run as an infinite loop waiting for user-interaction. Its done by the exec_() method of QApplication (App is the instance name). Note the _underscore_ in the function name, this is to avoid confusion between Python’s own exec() built-in-function.

Getting Further

Tutorials

FAQs

Read the rest of this entry »

Written by Harsh

April 26th, 2009 at 8:01 am

Posted in Software

Tagged with , , , , , ,

Getting the latest Django Documentation to run offline

4 comments

Yes, really.

Yes, really.

Ok so you have started with Django, the Python web-framework and are finding yourself wasting a lot of precious little seconds on their regularly updated documentation online?

(The docs folder in your downloaded django tarball is just not so up to date!)

Well then this is the guide for you. It will explain in neat little steps on how to go about obtaining the freshest of all django documentation online (From their code repository) and build it for use on your local machine or web-server.

First off, here are the requirements you will need installed before you begin:

  1. SVN (Subversion)
  2. Sphinx (Python)
  3. make, etc… build tools

For example, on a Debian/Ubuntu system you would run:

harsh@work:~$ sudo apt-get install subversion python-sphinx make

Fetch the documentation

Once you have got them all installed, lets start the process by fetching the documentation files from Django’s SVN repository:

harsh@work:~$ mkdir django && cd django

harsh@work:~/django$ svn co http://code.djangoproject.com/svn/django/trunk/docs

After the above command finishes downloading the documentation files (It’s checking-out source code from the repository), you should have a folder named docs under the current working folder (~/django in my example’s case).

Build the HTML documentation

Our next task is to build these reStructuredText (reST) files into HTML using Sphinx. We issue the following command to do so:

harsh@work:~/django$ cd docs

harsh@work:~/django/docs$ make html

Very simple! All the built files would go to the ~/django/docs/_build folder if you’re following my example. This folder would contain two folders named doctree and html. The html one is our sweet nectar of immortality!

Note: There are other make [options] that you could probably use, such as pickle, latex, etc. Also, the file conf.py under the documentation root might be of interest to people who would like to customize things a little more.

Done!

Now that we have our files ready, we can move it to a preferred place. For me it was /var/www (My local web-server root). So all I then had to do was:

harsh@home-desktop:~/django/docs$ mv _build/html /var/www/django-doc

That’s it. Now you can just browse to this folder either directly (Files) or by putting it on your local development server. Enjoy!

P.s. With some more configuration, you can automate this process and even make it update weekly or so for you. So add all the salt you would like for taste, and happy hacking!

Written by Harsh

December 19th, 2008 at 12:52 am