Designer is a Good Resource
If you have not done it yet, please check the previous sessions:
All files for this session are here: Session 3 at GitHub
Designer is a Good Resource
Today we are going to make our application look better, and introduce some new things, like resource files.
When we finished Session 2, our main window looked like this:
There are several things wrong with that picture. Let's tackle them one at a time, using Qt Designer.
That's just wrong. While I have not yet chosen a name for this example application, it's silly to have the window title (and taskbar entry!) say "MainWindow"!
Here's how you change objet properties in Designer.
First, you select the object you want to modify. You can do that by clicking on it, or by selecting it from the Object Inspector. For some widgets one or the other is easier. For example, it may be hard to find empty space in a window to click and select the window itself, or click in a very small widget, like a separator. In those cases, just use the Inspector.
Once you have the right object selected, look at the Property Editor.
There is a list of properties (obvious ;-) separated by titles like "QObject" or "QWidget". Don't worry about those titles much, just look for what you need, (it often is pretty obvious!).
In our case it's the windowTitle property.
I will not be writing these detailed explanations and pictures for each property. I trust you can find them if I tell you "The windowTitle property of the MainWindow Object".
Let's change that to "Todo".
The window icon is the default generic icon. This is important because it appears in the taskbar along the window title, and if you are using it in some operating systems or configurations, the user may only see the icon!
Finding icons to use in your applications is a big problem. There are several things you can do:
Hire a graphics designer to do icons for you.
This, of course, is rather expensive, specially if you are a hobbyist.
Search the web and see what you can find.
For example, if I look for "todo icon" in google, I find many, some really nice. However, many of those are subject to copyright, so it's a better idea to look for them in places like wikimedia commons:
Or maybe Open Clipart:
But my point is: those two icons are not all that awesome, and searching for a nice one is going to take a while. If you will need 10 or 15 icons in your application, the problem is even worse, because you want the icons to be consistant!
Find a set of KDE (or maybe GNOME) icons you like, and steal consistently. This is my preferred solution.
An added perk is that all KDE (or GNOME) icon themes have consistent internal names. That way you can later on switch to another theme very easy.
Then there is the icons file format. If the icon theme you like is available in SVG format, that's good. SVG is scalable, which means the icons will look good at all sizes without the need to include multiple copies in different sizes.
In this tutorial I will use icons from the Reinhardt set. Why? I like them, and the style is simple enough that I feel I can hack a fitting icon using Inkscape if needed (as I did in this case, see below).
So, in short: choose an icon theme you like, and use only icons from that theme, if possible.
For this app's icon, I made this out of a piece of "mark_as_ham.svg" and some green colour:
So, after all this icon talk, how do we use it? Well... that needs yet more talk, because there are two ways: use icon files and use a resource file.
In Designer, go to the windowIcon property of MainWindow. Click on the down arrow. Select "Choose File". The bad news: doing this makes packaging and distribution a bit harder later on. The worse news: this will not work with a SVG icon. So forget about it.
In Designer, go to the windowIcon property of MainWindow. Click on the down arrow. Select "Choose Resource". You will see a rather empty window.
A resource file is a XML file that contains references to all the icons you want to use. Later, this is compiled to a python module, which you can use from your application. As long as that python module is distributed along with the others, you will be fine, so there is never a problem of not finding an icon, or worrying about where they are installed. Things will just work. So it's worth a bit of effort getting this right.
Here's how I do it:
Click on the pencil button in the top right to get to the "Edit Resources" window.
Click on the "New Resource File" button in the bottom-left. Call it "icons" (or whatever you want)
Click in the "Add prefix" button (fourth from the left). I called my prefix "/"
Click in the "Add files" button (fifth from the left). Add todo.svg (finally!), click OK.
Steps 1, 2 and 3 are only needed the first time you use an icon. To add the icons we will use later it's just step 4.
So now your resource window looks like this:
Choose it, and that's it, the window has the right icon! Well ... not really.
First compile the UI. Remember we need to do this whenever we change something using designer!
$ pyuic4 window.ui -o windowUi.py
Then run the program:
$ python main.py Traceback (most recent call last): File "main.py", line 11, in <module> from windowUi import Ui_MainWindow File "/home/ralsina/Desktop/proyectos/pytut/session3/windowUi.py", line 41, in <module> import icons_rc ImportError: No module named icons_rc
This is because you also need to compile the icons.qrc file we created. This is done using
$ pyrcc4 icons.qrc -o icons_rc.py
And the icon works now :-)
Since it's boring having to remember to run
pyrcc4, I wrote a trivial script to handle it, build.sh. If you are in windows, a similar BAT file is trivial.
Luckily, the next two UI fixes are much simpler!
At the left of our task list there is a tree decoration. Since this is not meant to be a tree, they are just a waste of space. They can be removed with the rootIsDecorated property of the list widget.
I think the default margins here (4 pixels) look old fashioned. I prefer 0 pixels. YMMV.
You can change them in the layout[something]Margin properties of centralWidget.
I also prefer to set these in our QTreeWidget:
uniformRowHeights True (better performance for long lists)
See the docs to see what they do!
So, after running build.sh, this is how the app looks now:
In this session, we did no coding at all, we just worked on designer and graphical details. This may not seem too important to you, if you are a hardcore coder, but trust me: it is. Making apps as pleasant to use and look at as you can within your possibilities is very important if you want the first release to make any kind of impact. I learned it the hard way by releasing ugly apps ;-)
It doesn't matter if your graphical design skills are limited, like mine, try not to overreach and do your best.
In session 4 we will dive into coding, and make this app functional for the first time, introducing one of the neatest features in Qt: Actions.