Skip to main content

Qt SDK 1.1

While working on my PhD, I got to know the Qt software developers kit from (then) Trolltech. Nowadays, the Qt SDK is property of Nokia and is available under both a commercial and a LGPL license. The older free GPL license did not allow people to develop non-free software using the free version of the libraries.

The idea is still the same: in an abstracted fashion, you can develop applications, by writing them once and compiling them on different platforms. At the time I used it, I did manage to compile my proof-of-concept on Windows, Linux and OSX, with very little platform-specific lines of code.

The newest release of the SDK is a merger of the former desktop-oriented and the mobile SDK's, meaning that a single SDK allows you to target Windows, OSX and Linux computers, but also a wide range of mobile devices.

http://labs.qt.nokia.com/2011/01/20/qt-sdk-1-1-technology-preview-released/

The released version is a technology preview, which means it is deemed rather complete, but is still undergoing further testing before it is officially called a released product.

My main reasons to go for something like Qt:

  • abstract platform-specific (and nasty) things into a logical and consistent API
    • networking
    • reading/writing files
    • User Interface (very important > GUI behaves as "native" as possible, e.g. you get the real OSX menu on Mac, while the same code gives a typical Windows menu running on Windows)
    • lots more: OpenGL, utility classes, XML, SQL
  • They are working hard on responsive interfaces, supporting multi-touch
  • Good use of design patterns: abstraction, model/view framework, graphics framework...
  • Mostly C++ but can be used from other languages: java, Python...
  • liberate license: free to use
  • well documented
If you do, I suggest to buy a good book. I can recommend:
I recently bought "Advanced Qt Programming: Creating Great Software with C++ and Qt4", but haven't found the time to read it yet.

And if you are curious, it does not support the iPhone/iPad or Android, but some clever people seem to get away with it anyway: http://www.qt-iphone.com, http://code.google.com/p/android-lighthouse 

Labels:

Comments

  1. TheRohan07 February, 2011

    The Qt SDK 1.1 technology preview provides developers with the opportunity to experience the next step in tools support for Qt based development.

    The Qt SDK 1.1 technology preview is available in the following versions and installation packages:

    * 32- or 64-bit Microsoft Windows XP Service Pack 2, Windows Vista, or Windows 7.
    * 32-bit Ubuntu Linux 8.04 or later.
    * 64-bit Ubuntu Linux 8.04 or later.
    * 64-bit Apple Mac OS X 10.6 or later.

    Check the link to download Qt SDK 1.1 (Technology Preview): http://bit.ly/dIiUGQ

    ReplyDelete

Post a Comment

Popular posts from this blog

Improve usage of BIM during early design phases

When I was collecting ideas for a book chapter on BIM (that seemed to never have emerged after that), I collected 10 ideas, which I believe still reflect good recommendations to improve the usage of BIM during the early design phases. These ideas are related to BIM software, but you can apply them in any flavor, as long as you can model with Building Elements, Spaces and have control over representation. Introduction This article gives an overview of several recommendations and tips, to better apply BIM applications and BIM methodologies, in the context of the early design phases. Many of these tips are applicable in any BIM application and they are based on experience gathered from teaching, researching and using BIM software. Sometimes they could help software developers to improve the workflow of their particular BIM implementation. Tip 1 : Gradually increase the amount of information In the early design phases, the architect makes assumptions and lays out the main design in...
2 comments
Read more

Getting BIM data into Unity (Part 0 - Introduction)

This post reflects on work that I carried out, elaborated during my guidance of a few Master thesis students, to better integrate BIM models into Unity. This will be a multi-part post. This makes each article a bit shorter to read, but allows more in-depth information overall. Hope you like it. Please comment with feedback and further improvements. Basic methodology Unity can import geometry from FBX and Collada (DAE) files primarily. There are a few other formats, but these are the preferred ones. When integrating CAD or BIM files into a realtime environment, you have to convert the geometry. During my Unity teaching and the writing of the book Unity for Architectural Visualization ( buy from Packt ), I’ve come up with a basic diagram explaining geometry exchange between CAD and BIM software and Unity. Throughout these posts, we’ll go more into detail. We start with ArchiCAD, but will tackle Revit in a follow-up post. Promised!
Post a Comment
Read more

PythonOCC : Open Source interactive CAD shell (and how to run it on OSX)

What is PythonOCC? PythonOCC is an Open Source (LGPL) Python-wrapper for OpenCASCADE. So what is OpenCASCADE (OCC)? This is an advanced Open Source (custom license) modeling kernel, comparable to commercial engines, such as ACIS or Parasolid, which are used in quite some commercial CAD programs. When you want to develop CAD software, you could use OCC and write programs in C++. And why using Python? With this wrapper, you can create CAD and geometry scripts in Python, which is an interpreted Object-oriented scripting language. You can write almost "on-the-fly" and seriously reduce the implementation effort, by skipping the compiling-phase. You can even interact with a running program in the Python interpreter. Want to read more about this? The OpenCASCADE official website  (currently Linux and Windows are officially supported) The PythonOCC website/blog  (beware that the core of the actions happen in the development repositories). So far so good. Now the nasty, techn...
4 comments
Read more