Qt GUI Toolkit
If you are new to GUI programming, you might find that your first widget comes up blank on the screen or not at all. There are two very common reasons for this to happen.
First of all, a widget's window on the screen can be overwritten at any time by the window system. The window system does not store the contents for you, it just calls the widget's paint event function when the widget needs to be refreshed. Thus, if you draw on the widget but the paint event function doesn't reproduce the drawing exactly, you might not see any effect on the widget. Generally, the best method is to do all your drawing in the paint event function, and just instruct the widget to do a repaint whenever its state changes.
Secondly, when you create a widget, it is not visible. In Qt, you have to call the show member function to make widgets visible; other toolkits have a similar function.
Finally, I would like to mention a few points I consider important when designing and implementing GUI programs:
Keep it simple. When you build new widgets and dialogs try to keep their interfaces as small and elegant as possible. Don't add a lot of functions that might be nice to have in the future.
Don't crowd the screen. Try to keep your dialogs as intuitive and minimalistic as possible. A dialog should be both functional and pleasing to the eye.
Use double-buffering. At least when all or parts of a widget will change significantly over time. Programs that don't flicker look a lot more professional than the ones that do.
Cache like crazy. If there are parts of your program that do time-consuming operations, e.g., generation of pixmaps, save the result so that you don't have to do the same operations over and over.
Keep your member variables private—this is good object-oriented practice. In GUI programming it is even more important. A change in a variable often means that you have to update the screen. If you set variables via member functions, you can guarantee that the screen is always up-to-date.
Put your drawing code in one place—preferably in a single member function. Bugs in the relationship between the values in your member variables and what the widget displays are then located in one place. (You will be glad you did.)
Use standard types as arguments to signals and slots. If your signal contains an int, it can be connected to a large number of slots. If it contains an argument of the type MyNumber, the widget or dialog will not be as useful as a component.
The Qt source and binary versions for several platforms (including Linux of course) can be downloaded from the net at ftp://ftp.troll.no/qt/.
Eirik Eng (email@example.com) is a co-founder of Troll Tech AS, and works there as a developer. He has a siv.ing. (M.S.) degree from the Norwegian Institute of Technology and has worked with GUIs and OOP since 1991. His main hobby is office gardening (perfect for people who spend a lot of time at the office). This year he is especially proud of his 4 foot high (and still growing) eggplants and his tamarind tree.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide