easygui_qt 0.2.3a

Design philosophy

Like the original EasyGUI, EasyGUI_Qt seeks to provide simple GUI widgets that can be called in a procedural program. EasyGUI_Qt is NOT event-driven: all GUI interactions are invoked by simple function calls.

The archetype is get_string(message) which pops a box whose purpose is exactly the same as Python’s input(prompt), that is, present the user with a question/prompt, have the user enter an answer, and return the provided answer as a string. Thus easygui_qt.get_string() can be used as a drop-in replacement for input(). Similarly, instead of using a print() function to display a message, show_message() is used which pops a message window.

Unlike the original EasyGUI, which sometimes used cryptic names like msgbox or ynbox, EasyGUI_Qt attempts to use descriptive names which follow PEP8 convention. Thus, instead of msgbox, it uses show_message; instead of ynbox, it has get_yes_or_no. Most function names start with either get_ or set_.

EasyGUI_QT is based on PyQt; it leverages the available dialogs that come with PyQt whenever possible. This makes it possible to have automatic translation of some GUI elements (such as text on standard buttons) provided the locale is set correctly and that the local distribution of PyQt includes the appropriate translation: when EasyGUI_Qt runs, it scans the standard PyQt location for translation files and note which ones are present and can be used when the locale is set.

An attempt is made at avoiding duplication of essentially identical functionality. Thus, multiple selections from a list of choices is done only one way: by using a dialog where choices appear as labels in text and not labels on buttons.

Similar projects

The following is an incomplete lists of a few cross-platform projects that share some similarity with EasyGUI_Qt, but use back-ends other than PyQt

• easygui: the original; tk back-end

• anygui: multiple back-ends; well known but no longer supported

• psidialogs: multiple back-ends supported - possibly the most complete project from that point of view.

• python-dialog: dialog/Xdialog/gdialog back-end

There are quite a few lesser known projects but none that seem to be actively supported. If you are aware of other projects that should be mentioned, do not hesitate to contact me and let me know.

0.2.3a

• changed extention of some demos (from .pyw to .py) as they were not uploaded to pypi

0.2.3

• added demos dir to setup.py so that it can be included on pypi

0.2.2a

• changing path on image in readme in attempt to help pypi display properly

0.2.2

• changed the syntax for calls to super() to be compatible with Python 2. Note that the intention is to be a Python 3 project, but if simple changes can make it compatible with Python 2, they will be incorporated.

• changed name of set_save_file_name to get_save_file_name

• changed name of yes_no_question to get_yes_or_no

• added get_list_of_choices

• added demo launcher

0.2.1

• Moved the demos directory to a more sensible location

• added get_directory_name

• added get_file_names

• added set_save_file_name

• attempt to fix bug for Python 3.2 where inspect.signature was not defined

0.2.0

The API has been changed since the initial release and the following widgets have been documented, with images inserted in the documentation.

• get_choice

• get_float

• get_int

• get_integer

• get_string

• set_font_size

• set_default_font

• select_language

• set_locale

• show_message

• yes_no_question

0.1.0

• First release on PyPI.