Language Selection

English French German Italian Portuguese Spanish

Qt in the land of Gnome: issue of copyright

Filed under
Software
Ubuntu

Recently Mark Shuttleworth wrote about how Qt will become part of the Ubuntu 11.10 desktop, and that Qt-based apps will eventually be considered as possible default Ubuntu apps. Obviously, this would be a big change from using GTK-only applications (that is, aside from Firefox and Open/Libreoffice applications), but Mark encourages GNOME developers to consider using Qt, too. He writes, “Perhaps GNOME itself will embrace Qt, perhaps not, but if it does then our willingness to blaze this trail would be a contribution in leadership.”

I agree on this, and think that enabling usage of Qt in GNOME projects would be a contribution in leadership. It would be great if developers had the option of using tools like Qt Creator and Qt Quick when building applications for GNOME-based desktops (or other devices!).

The question is: How do you make that happen? All technical matters aside, how do you encourage GNOME developers to consider using Qt for their applications?

To me, one major consideration in further developing the Qt-to-GNOME bridge, and encouraging developers to use Qt in GNOME-based desktops, involves copyright.

rest here




More in Tux Machines

Games and Emulation

Linux Devices

Koozali SME Server 8.2 Reaches End of Life on March 31, Upgrade to Koozali SME 9

Koozali Foundation, through Terry Fage, announced the availability of a final set of updates for the Koozali SME Server 8.2 operating system, which will reach end of life this week. Patching some of the reported bugs, the new packages released today for Koozali SME Server 8.2 are e-smith-ibays-2.2.0-16.el5.sme.noarch.rpm, e-smith-manager-2.2.0-14.el5.sme.noarch.rpm, smeserver-clamav-2.2.0-15.el5.sme.noarch.rpm, smeserver-locale-*-2.2.0-56.el5.sme.noarch.rpm, and smeserver-yum-2.2.0-26.el5.sme.noarch.rpm. Read more

Development News

  • GCC for New Contributors
    I’m a relative newcomer to GCC, so I thought it was worth documenting some of the hurdles I ran into when I started working on GCC, to try to make it easier for others to start hacking on GCC. Hence this guide.
  • #1: Easy Package Registration
    Last month, Brian Ripley announced on r-devel that registration of routines would now be tested for by R CMD check in r-devel (which by next month will become R 3.4.0). A NOTE will be issued now, this will presumably turn into a WARNING at some point. Writing R Extensions has an updated introduction) of the topic.
  • Emacs as C IDE and JHBuild
    Although Builder clearly is The Future as GNOME IDE, I still all my coding in Emacs, mostly because I have been using it for such a long time that my brain is to all the shortcuts and workflows. But Emacs can be a good IDE too. The most obvious everyday features that I want from an IDE are good source code navigation and active assistance while editing. In the first category are tasks like jumping to symbol's definition, find all callers of a function and such things. For editing, auto-completion, immediate warnings and error reporting, semantic-aware re-factoring are a must. Specifically for GNOME related development, I need all this to also work with JHBuild.