Q
Qt Blog
blog.qt.digia.com · Company blog · on HN since 2012
The Qt company's official blog, announcing Qt releases and mobile ports to Android and iOS, with tutorials on new features.
What HN saysHN commenters cite it for release news such as Qt 5.1 and 5.4 and for tutorials on new features.
45HN people shared it
16linked it in comments
53stories submitted
1.2Kstory points
12 years agolast shared
2012people per year2026
Most-shared posts
- 1The Qt Company Introduces a Unified Website5 people · 219 points · first shared 2014 · 145 comments on HN
- 2Qt for Android Port Contributed to the Qt Project3 people · 5 points · first shared 2012 · discussion on HN
- 3Qt for iOS (preview)3 people · 3 points · first shared 2013 · discussion on HN
- 4Qt 5.1 Released With Android and iOS Technology Previews2 people · 95 points · first shared 2013 · 50 comments on HN
- 5Qt 5.4 Released2 people · 18 points · first shared 2014 · 1 comments on HN
- 6Qt 5.1 Alpha Available2 people · 10 points · first shared 2013 · 1 comments on HN
- 7New Qt Scene Graph Renderer2 people · 8 points · first shared 2013 · discussion on HN
- 8Benefits of the Indie Mobile Licensing2 people · 1 points · first shared 2014 · discussion on HN
- 9Evolution of the QML engine, part 12 people · 1 points · first shared 2013 · discussion on HN
- 10Defragmenting Qt and Uniting Our Ecosystem1 people · 134 points · first shared 2014 · 91 comments on HN
- 11Introducing the Qt WebEngine1 people · 106 points · first shared 2013 · 36 comments on HN
- 12Qt Creator 3.1.0 released1 people · 87 points · first shared 2014 · 34 comments on HN
- 13Adding LGPL v3 to Qt1 people · 74 points · first shared 2014 · 18 comments on HN
- 14Qt 5.2 Beta Available1 people · 69 points · first shared 2013 · 17 comments on HN
- 15Preview of Qt 5 for Android1 people · 68 points · first shared 2013 · 13 comments on HN
What HN people wrote when they linked it
zanny · 2014-09-16
qmlbook.org, the examples in Creator, the blog the OP post is from has a lot of tutorials on new features as they come out (http://blog.qt.digia.com/).
fpgeek · 2013-07-15
The could have done even better. Qt for iOS and Qt for Android existed at the time and have now become officially supported (despite all of the major cutbacks Qt development has gone through since then):
http://blog.qt.digia.com/blog/2013/07/03/qt-5-1-released/
If they had embraced Qt as a cross-platform layer back then, they could have been "a better Xamarin than Xamarin". That would have been a great way to get developers and users into their ecosystem. Qt apps could "run everywhere", but they'd run best on Nokia phones (where it would be built-in and integrated). Instead...
NaterGator · 2013-09-10
The author would benefit greatly from using the appropriate UI components to accomplish his goal instead of kludging a rate limiting mechanism onto his MainWindow's resize implementation.
Instead he could build a graphics scene using QGraphicsScene (http://qt-project.org/doc/qt-5.1/qtwidgets/qgraphicsscene.html) with a nice normalized coordinate system which logically represents the namespace size in the SSD on UI elements designed to be rectangles. Adding a view of that scene onto his window is trivial, and as an added bonus he gets the power of Qt's scene graph which will be a boon for both performance (http://blog.qt.digia.com/blog/2013/09/02/new-scene-graph-renderer/) and portability. Qt will efficiently manage resizes and draw the scene optimally without overhead associated with a re-purposed widget.
His approach does achieve the desired goal and is probably appropriate in some circumstances, but in this instance he should take a step back and assess if there is a greater fundamental problem with his design.
mmebane · 2014-12-20
As of Qt 5.4, it's in maintenance mode, and will be deprecated soon.
Source: http://blog.qt.digia.com/blog/2014/12/10/qt-5-4-released/
gulpahum · 2014-10-12
I'm currently rewriting my Mac application. Its prototype was written in Qt, but I'm now dropping Qt for several reasons:
1. I demoed my application to my friends and they all complained that it didn't behave exactly like a native Mac application.
2. Qt5 has a lot of UI bugs on Mac OS X.
3. The LGPL license of Qt may not compatible with Mac App Store [1].
4. I could buy the commercial license of Qt, but it's $215/month for Mac OS X. I don't know if my app is going to sell at all, so I can't afford that kind of burden.
[1] http://blog.qt.digia.com/blog/2014/10/01/benefits-of-the-indie-mobile-…
milliams · 2014-09-16
http://blog.qt.digia.com/blog/2014/09/16/the-qt-company-introduces-a-u… should explain it.
groovy2shoes · 2014-09-16
Previously, there was the community-run Qt Project, as well as the commercial Qt (qt.digia.com). Those two projects are now merged. The announcement is here: http://blog.qt.digia.com/blog/2014/09/16/the-qt-company-introduces-a-u…
untothebreach · 2014-09-16
This blog post explains it: http://blog.qt.digia.com/blog/2014/09/16/the-qt-company-introduces-a-u…
guruz · 2014-05-03
During my time working inside the Qt office, there were quite a few guys using their Nokia N900 or N9s to show QML-based presentations with HDMI output to a big projector.
The framework was this one as far as I remember: http://blog.qt.digia.com/blog/2011/05/30/a-qml-presentation-system/
blub · 2014-04-28
I'd be interested to know what kind of problems Qt has with accessibility, I have personally not used the QAccessible* classes yet and would appreciate any tips from the field.
Some potentially interesting blog posts: http://blog.qt.digia.com/blog/category/accessibility/ I wonder what came out of the major upgrade in Qt 5, from looking around the web it seems to support MSAA fully and also I2A in some form.
bri3d · 2014-02-26
Right, but as noted in the blog you link the application is still only exposed to 1x or 2x scale (where 1pt = 2px), and then everything is scaled back down.
On Windows the app is exposed to the scale factor (for better or worse): https://blog.qt.digia.com/blog/2009/06/26/improving-support-for-higher…
DougBTX · 2014-02-26
> (rather than only available as 1x or 2x scale like on the Mac)
It isn't continuous, but there are more than two scaling levels on OS X:
https://blog.qt.digia.com/wp-content/uploads/2013/04/qtRetinaMacDispla…
More details: https://blog.qt.digia.com/blog/2013/04/25/retina-display-support-for-m…
landr0id · 2013-10-17
Qt 5.2 also adds Windows, Mac, and Android extras (platform-specific things for a native feel) [1]. For example, on Windows you can set the task bar progress, and on OS X you can use some native components, such as the toolbar. The OS X documentation is poor, but there is a GitHub repo/mirror for it [2]
[1] http://blog.qt.digia.com/blog/2013/09/30/qt-5-2-alpha-available/
[2] https://github.com/qtproject/qtmacextras
spacelizard · 2013-10-07
Actually the last few iterations of VS and Office skinning have gotten added into MFC and can be enabled pretty easily for any app. The Ribbon UI is also fully available in MFC and VS. Just no one uses any of this stuff for obvious reasons.
http://msdn.microsoft.com/en-us/library/vstudio/cc137831.aspx
http://msdn.microsoft.com/en-us/library/ee354408.aspx
Spotify actually uses Qt but with a custom stylesheet that makes it look more like iTunes. I have no idea why they did this, I think it makes it look terrible and clunky. Read this for more info:
http://blog.qt.digia.com/blog/2007/11/27/theming-qt-for-fun-and-profit…
sho_hn · 2013-07-23
You're right, sorry - replacing JavaScriptCore with v8 indeed only happened for Qt 5. However, v8 is indeed on the way out again, as mentioned: http://blog.qt.digia.com/blog/2013/04/15/evolution-of-the-qml-engine-p…
daliusd · 2012-12-19
There is Necessitas Qt 4.x port for Android that is pretty solid and was contributed to Qt Project quite recently (http://blog.qt.digia.com/blog/2012/11/08/necessitas-android-port-contr… I have not found good iOS port when I was looking for one. At least for BlackBerry it already is - you can write Qt apps for BB10/PlayBook OS just now.