Slashdot Mirror

Any chance that part of the motivation for taking control of Nokia was an attempt to undermine Qt (commercial licensing now under Digia: http://www.digia.com/)?

It's $149 per month for multi-mobile, $215 per month for single-desktop, with discounts for various combinations. It's all pretty simple if you just got to their purchase page.

QtQuick2 requires OpenGL. I didn't say I'm using OpenGL directly. However there is Qt3D and QtQuick3D that you might have a look at http://doc-snapshot.qt-project... http://doc.qt.digia.com/qt-qui... .
As for the graphs, there are some commercial graphs supplied by digia http://blog.qt.digia.com/blog/... or KDAB http://www.kdab.com/kdab-produ... or freely available QWT http://qwt.sourceforge.net/ .

QtQuick2 requires OpenGL. I didn't say I'm using OpenGL directly. However there is Qt3D and QtQuick3D that you might have a look at http://doc-snapshot.qt-project... http://doc.qt.digia.com/qt-qui... .
As for the graphs, there are some commercial graphs supplied by digia http://blog.qt.digia.com/blog/... or KDAB http://www.kdab.com/kdab-produ... or freely available QWT http://qwt.sourceforge.net/ .

It's like you forgot that Google exists. http://qt.digia.com/Qt-in-Use/

When last I heard, a few years ago, QT had been acquired by Nokia. More recently, it seems that Nokia is being acquired by the borg(Microsoft).

It would seem that QT is to be owned by Microsoft. Is this correct? If so, what does that hold for QT? I realize that QT is LGPL or some such, but that doesn't mean that Microsoft won't ruin it or snuff it out. See Oracle and MySQL for a road map. Hopefully I am wrong.

Fortunately, yes, you are wrong. Digia bought the business side of Qt from Nokia in 2012. The free-software side of Qt is the Qt Project.

C and open source is a great solution,

absolutely, stood the test of time in a way no other language has.

right up until you have to make an identical GUI work across a Microsoft and *nix platform.

there you just show your lack of google-fu. There's Qt which is awesome, or even GTK, or a host of others.

Nowadays you need a GUI that works on Macs too, and mobile.

That said, the whole concept of a thick GUI is dying, the state-of-the-art is currently HTML-based GUIs, and they are as identical as you can get (if you host in the same rendering engine - eg webkit).

The problem you have to worry about is the first sentence. every application in the enterprise that isn't written by Microsoft is built on Java. the industry *is* moving away from Java, as its seen to be either legacy, slow, bloated, or just insecure. The problem is that those industries are looking for alternatives and are choosing Microsoft. The number of jobs for ASP.NET MVC 4 are staggering right now, in a way that I would never have expected for web-based development. We have to be careful MS doesn't scoop up all the old Java systems.

Here
You can tell this is in Qt because the text on "Button 1" and "Button 2" aren't centered in the button correctly. The icons in the tool bar don't follow cocoa conventions and look out of place.

Digia and the Qt Project has been exploding with great new work.

Qt 5.1 is adding initial support for Qt Quick Controls formerly "Desktop Components". These are packaged Qt Quick controls such as sliders and tables with skins for each of the different platforms.

The Qt Project has just recently started shipping the Qt Installer Framework which is a cross-platform installer framework (that is used by the Qt installers). After managing multiple installers on different platforms for my own open source work, I'm really looking forward to digging into this.

Another huge project is the new Qt Build System or qbs. This is a replacement for QMake and I'm really excited to see how it shapes up against CMake.

With the recent advancements in the C++ standard and Qt, it is a very exciting time to be a C++ developer.

Digia and the Qt Project has been exploding with great new work.

Qt 5.1 is adding initial support for Qt Quick Controls formerly "Desktop Components". These are packaged Qt Quick controls such as sliders and tables with skins for each of the different platforms.

The Qt Project has just recently started shipping the Qt Installer Framework which is a cross-platform installer framework (that is used by the Qt installers). After managing multiple installers on different platforms for my own open source work, I'm really looking forward to digging into this.

Another huge project is the new Qt Build System or qbs. This is a replacement for QMake and I'm really excited to see how it shapes up against CMake.

With the recent advancements in the C++ standard and Qt, it is a very exciting time to be a C++ developer.

Digia and the Qt Project has been exploding with great new work.

Qt 5.1 is adding initial support for Qt Quick Controls formerly "Desktop Components". These are packaged Qt Quick controls such as sliders and tables with skins for each of the different platforms.

The Qt Project has just recently started shipping the Qt Installer Framework which is a cross-platform installer framework (that is used by the Qt installers). After managing multiple installers on different platforms for my own open source work, I'm really looking forward to digging into this.

Another huge project is the new Qt Build System or qbs. This is a replacement for QMake and I'm really excited to see how it shapes up against CMake.

With the recent advancements in the C++ standard and Qt, it is a very exciting time to be a C++ developer.

The project runs on Linux and on Nokia's N900 and N9 phones. I'm looking for help to port it to Symbian, Android, and iOS devices.

AFAICT it was a licensing issue for the longest time. Previously, the licensing options for Qt forced developers to either use GPL for their code, or to buy a commercial license from Trolltech if they wanted their code proprietary. It wasn't a bad deal for free software, but not a good proposition for luring developers to the platform. Of course, today the available licenses from Digia also include LGPL, but that came pretty late.

Yep, 2009 in fact.

http://en.wikipedia.org/wiki/Qt_(framework)#Licensing

AFAICT it was a licensing issue for the longest time. Previously, the licensing options for Qt forced developers to either use GPL for their code, or to buy a commercial license from Trolltech if they wanted their code proprietary. It wasn't a bad deal for free software, but not a good proposition for luring developers to the platform. Of course, today the available licenses from Digia also include LGPL, but that came pretty late.

Qt brings you the best of world worlds. Please check http://blog.qt.digia.com/

Websites are actually the least of the problems - a single IP usually covers them. In Windows, you have them laid out like http://www.microsoft.com/office, whereas in the unixes, you have virtual hosts laid out like http://qt.digia.com/ that easily share a single IP. This shortage hits offices - like when they use VoIP phones, those addresses cannot be put behind NAT, even though the laptops can be. That's where these IPs would get eaten faster than one can produce them as far as IPv4 goes, and that's where they're running into problems. Not an issue w/ IPv6, but would have remained a problem even if they had grown it simply to 48 bits or less. Websites just have to be dual stacked i.e. accessible from both IPv4 and IPv6 hosts. Virtual hosting would guarantee that every virtual host on a website gets accessed, and for IPv6, the admin has the choice of either using virtual hosts, thereby keeping the practice unchanged to avoid any learing curve issues, or else assigning different IPv6 IPs to each virtual host, making each of them a separate real host in its own right.

Your explanation that it's software and should be easy to replace just ignores the scope of what has to be changed, and in how many places. No matter what change they had made to that firmware, they'd have had to do it everywhere - make sure that every router supports it, every OS supports it, every server supports it.... No different from what's been and is being done w/ IPv6 right now. Right now, in IPv6, the main stumbling block is the core routers, which do have to be modified to do a maximum transfer of 128 bits as opposed to 32. And the edge routers need to handle the simplified routing protocols as well. Those are the new parts.

On the landfills, the router manufacturers would have to assess their policies on which of their routers are remotely or field upgradable, and which ones absolutely have to be replaced. While they may love to sell as many routers as they produced in the past, I can see them quickly getting into an allocation situation if they tried that. So the only routers that would make it to the landfills would be the ones that can NOT be upgraded, maybe b'cos they were made in the 90s. Otherwise, most routers that have adequate memory would just need to have their OSs updated and include IPv6 support in it.

Digia

Annual Report

Market Cap of â55m so its not as big as say, RedHat, but it is bigger than Nokia... or will be in a few months :)

Incidentally, Nokia bought Qt from Trolltech for â104m... I don't think they sold it for anything near that amount.

They're a small company, mostly focused on ERP, and have a strong alignment with Microsoft. I'd say we can wave goodbye to QT for Linux/KDE in the not too distant future.

For more than ten years, Microsoft has been one of Digia’s key partners. Digia provides its customers with comprehensive solutions based on Microsoft technologies. Digia is actively developing its partnership in line with the Microsoft Partner Network programme.

http://www.digia.com/en/Home/Company/Technology-Partners/

Pekka is a 3rd generation entrepreneur and founder of Digia, a publicly listed mobile sw-company, listed at NASDAQ OMX Helsinki. In this capacity he now acts as the Head of AppCampus, which is a 18 million euro grant fund established by Aalto University, Nokia and Microsoft.

The Qt SDK has an option to be used with LGPL v 2.1 which will allow developers to release proprietary executables without being required to release their source code. Source release is only required if the developers make changes to the Qt SDK itself, which usually shouldn't be an issue. There's also a commercial license available if even this is too onerous.

Well, Nokia still owns Qt... Digia is only handling the commercial software licensing and professional services for Qt. Basically, Digia are licensed to sell the product, but Nokia still owns and develops it in-house.

Not exactly going "all in".

All the details.

Book description of "Programming for the Series 60 Platform and Symbian OS" here