Qt 3.1.1 Released
prototype writes "Trolltech has released a maintenance release to Qt bringing the version up to 3.1.1. This release fixes some build issues with the professional edition as well as problems reports on Solaris and HP-UX, changes to build with Borland Kylix and a bunch of other minor updates. This bugfix release maintains both forward and backward compatibility (source and binary) with Qt 3.1.0. The full changelog on the release can be found here. Patches are also available using xdelta 1.1.3 (but not for Mac OS X as size of the the resulting patch is nearly as large as the complete package)."
Maybe I missed the bus, but what's forward compatibility? Isn't that really just backward compatibility in a future version? Does this require omniscience to acheive? What's the secret here?
Mostly minor & annoying stuff is fixed.
;)
ActiveQt: fortunately not on unix
--
Stefan
DevCounter ( http://devcounter.berlios.de/ )
An open, free & independent developer pool
created to help developers find other developers, help,
testers and new project members.
That is pretty close to pi. If old tradition holds, pi is the optimal version number, and from there on things tend to get worse - until we reach 6.28. Let's hope it won't go that way with Qt.
I like that Slashdot announces major releases of major applications, but please stop announcing "maintenance release"s here unless they contain some significant stuff that is really worth discussing... We have Freshmeat for these kinds of announcements...
My other account has a 3-digit UID.
I can't find any patches or full packages to download in the pub/qt/source folder. the last file is qt-x11-free-3.1.0.tar.bz2
Vote for global prefs bug
Mod parent up! Where can qt-3.1.1 be downloadable???
Forward compatibility is a big deal, and can be planned. Y2K bug--lack of longer date format; HTML--ignore unrecognized tags BASIC--use line numbers in increments of 10 so adding new lines is easy.
allow for new features... leave "space" in ruleset to allow for new rules in the future. Avoiding hacks and shortcuts, or accounting for being able to make it right later, are good ways to keep your software feature proof.
Please use [ informative / summarizing ] SUBJECT LINES
Flame me here