This chapter introduces the idea of the device context, generalizing the concept of a drawing surface such as a window or a printed page. It will discuss the available device context classes and the set of “drawing tools” that wxWidgets provides for hand.
This article came from the book Cross-Platform GUI Programming with wxWidgets, which is finally published:
http://www.informit.com/title/0131473816
Yes, finally published. I’ve ordered my copy and am eagerly waiting for it.
You can cross compile your program and release a Windows executable without ever having to touch the proprietary Microseft Windows XP piece of shit system.
I agree wholeheartedly. I’m 70% through porting an application of mine from Windows to Mac and it has only taken me 3 days. wxWidgets is brilliant.
This is something I’ve been waiting for, for a very long time now!
wxWidgets has made C++ programming as simple as it always should have been. I love writing Windows apps from my Gentoo workstation…
Now, what we need is a killer IDE and there would be much wider, more rapid adoption of wxWidgets…for sure!
Something like Qt Designer that allows you to quickly knock up a GUI, instead of fidgeting with source code, layout managers, and the like. wxGlade works to a certain extent, but it is quite unstable on OS X and isn’t too intuitive.
Something like Qt Designer that allows you to quickly knock up a GUI, instead of fidgeting with source code, layout managers, and the like. wxGlade works to a certain extent, but it is quite unstable on OS X and isn’t too intuitive.
I have not used Qt Designer from Qt4, but Qt3.3+’s version of Qt Designer was a pile of junk.
You had to derive a class from the generated class just to make your code work.
All those springs and other UI spacing things just don’t work. You had to break layout and mess up your design just to add/move something.
Maybe Qt4 has a better designer, but I am never using that thing again.
Trolltech will get it right in Qt5 is what I am guessing.
I have not used Qt Designer from Qt4, but Qt3.3+’s version of Qt Designer was a pile of junk.
No it wasn’t.
You had to derive a class from the generated class just to make your code work.
That’s not true. You could quite easily write all your code in one class, but the derivation method is generally preferred from a good design perspective.
All those springs and other UI spacing things just don’t work.
‘Springs’ (actually spacers) do work. From your previous comments, it’s clear that you didn’t understand them well enough to use them effectively. For the record there are no ‘other UI spacing things’ in Qt.
You had to break layout and mess up your design just to add/move something.
You have to break the layout, true. If that’s upsetting for you, you should probably not use layouts and bear the consequences…
Maybe Qt4 has a better designer, but I am never using that thing again.
As far as layouts are concerned, it is much improved (though I don’t really have any major problems with Qt 3.x). It has a number of other benefits too.
Trolltech will get it right in Qt5 is what I am guessing.
They already have it right. It’s not perfect, but you’re clearly very hard to please. No toolkit wipes your ass for you.