Qt Now Open for Community Contributions

Today, we at Qt Software have opened our repositories to the public. Any developer can now help guide and shape the future development of Qt by contributions of code, translations, examples and other material to Qt and Qt-related projects. We have also published our roadmap and released Qt Jambi under the LGPL. Read on for details.

Since we moved to Git as our version control system in late summer 2008, the web-based Gitorious was an obvious choice for helping us manage the contributions. We have funded its founder Johan Sørensen and one of his colleagues to work on tweaks and added functionality like team support and wikis that are now available to all projects using Gitorious. We will continue to work on improvements to Gitorious together with the project in the future.

The new contribution site will not only host Qt itself but also a number of Qt-related tools and projects including the Qt Creator IDE, Qt Jambi and various Qt Labs projects.

Details about the contribution model can be found on our website or in Tor Arne's blog posting.

Qt Roadmap Published on qtsoftware.com

Along with the launch of the open repositories, we are publishing a roadmap that gives an overview of current features in development and research projects and helps you understand Qt's future direction. Not only that, we would love you to help us shape this direction through feedback and contributions.

Qt Jambi 4.5.0_01 Released Under LGPL

Additionally, we have released Qt Jambi to the open repositories today. This is the final feature release which will be followed by a one-year maintenance period. We are confident that a commited group of developers will take over and make it a successful open source community project.

Read more about the Jambi release in Eskil's blog posting.

Dot Categories: 


Can I subscribe/CC myself to tasks at http://www.qtsoftware.com/developer/task-tracker/ finally?

No, not yet. This will happen a bit later when we change the Task Tracker infrastructure.

Cool, guess it's time to sub those printing patches I've been working on...

Please do so. Qt-4 printing is basically broken. I find that I can't even print with LPR.

However, QPrint is never going to be a substitute for KPRINT (which has gone missing in KDE-4.x.y)

by STiAT

Finally. I hope that gets you some more guys contributing. I love how Qt has changed in terms of licensing and community work.

I've been working on a QAbstractItemProxy that automatically groups items based on the value of any column. It's used in Amarok to add folder grouping to the saved playlists. It has a lot of potential uses, so I'm gonna develop it further on gitorious and hopefully it will become part of Qt one day.


It is nice to see Qt available in a safer language. While I am not all that clear about how much safer Java is is than C++, it is certainly an improvement.

There is a great letter to the editor in Communications of the ACM, May, 2009: "Logic of Lemmings in Compiler Innovation" regarding the lack of safe programing languages in common use.

I hope to see Qt ported to other, even safer, languages. The most popular of these is FORTRAN >= 95 (which has now become a general purpose language that even supports OOP) which is not as illogical as it sounds at first.

There is another issue which is that of the need for a good compiler. I haven't yet tried GCJ-4.4.0, so I don't know how it is coming along. Obviously, a good compiler is necessary for the success of any language in OSS. And that is where FORTRAN fails. The current GNU FORTRAN compiler needs a lot of work to become 2003 or 2008 compliant, although the current version is becoming a adequate 95 compiler for non-numeric uses -- there is also the competing G95 project. So, perhaps Qt for FORTRAN 95 would be a good thing and finally provide a safe language for GUI applications.


Qt Jambi is not news. It's a product that has existed for 2 years now. Other "safe" languages for which Qt bindings exist are Ruby, C# and Python, probably even more.

If you want to start working on a Fortran 95 binding for Qt, talk to the KDE bindings team. I'm sure they can use the help and they may provide some hints on where to start.

Where are the compilers for Ruby, C#, & Python. Is there a difference between a port and language bindings?

Perhaps you missed the significance of the Jambi announcement. It is not that it is new. What is new is that it is being converted to a community based OSS project.

Yes, there are other language projects for Qt. IIUC, bindings for Pascal are being developed. Pascal is a very safe language although it has declined in popularity.


Java translates into bytecode which is then run in a VM. Python translates into bytecode which is then run in a VM.

So if Java counts as a compiled language, Python is one as well.

Java is a programing language. Any true programing language can be either compiled or run on an interperter (there are various kinds and a VM is one of these).

What makes it a "compiled language" is not the language itself, but rather, it is the existence of a compiler. Now, if you had read the whole thread, you would note the mention of the GCJ compiler:


which will compile Java either to byte code to be run on a virtual machine or compile it to machine code (just like C++). It can even compile Java classes and use them with C++ programs (sort of compiled JNI).

The same could probably be done for other languages (Python, Ruby, C#) that are usually interpreted. It was even done for BASIC although it isn't a true programing language.

You have a very strange definition of what makes a programming language "true".

Your remark makes little sense. IAC, the reasons that BASIC isn't a true programing language are technical and might not make any sense outside of a technical computer science discussion.

Or do you mean the reason that Java is a true programing language? It is just as much a programing language as C++ is.

i would suggest mentioning at least in a couple of of words what jambi is - it's a bit less popular than qt itself ;)

I know that opening the development is in general a good idea, but I was wondering if you had in mind some sort of control of what can go in and what falls out the scope of Qt.
If everyone is able to commmit whatever he thinks is right then Qt may become bloatware soon.

Also, have you considered merging Qwt into Qt?

About what to focus in the future... well, I have currently a necessity which could share with you:
I'm trying to make a synth app. This kind of app has typically a lot (>100) of widgets on the screen at the same time. Also I use a lot of CSS gradients and SVG to mimic the appearance of these kind of apps in other systems.
I've found that resizing the window (or moving a toolbar from horizontal to vertical, which in turn resizes the content also) is very slow with this setup. I know that there are some performance improvents in the making so I'm waiting this with expectation.
Maybe you should use this usecase as some sort of stress test. I can provide an example ui file if you want.
Also there is a widget I'd love to see: the "piano keyboard" widget, which seems ubiquitous in these kind of apps. I don't have much programming/design skills or time to make a beautiful SVG piano keyboard with an arbitrary number of keys, animation of keys pressed, arbitrary resizing, etc. so I'd love to see anybody implementing this.

Anyway, I want to thank the trolls for the best toolkit available.
You guys never cease to amaze me.

I'll look into setting up a development environment for Qt tomorrow. I want http://www.qtsoftware.com/developer/task-tracker/index_html?method=entry... implemented, and it seems rather easy.