dahicke wrote:

I found this Masters thesis. You should take a look at it. I think this is a implementation of what you are talking about:
http://vakken.groept.be/Vakken/MastersThesis0910/3230.pdf

Dave

Personally I do not know more about the plugin than what I put into the plugin wiki page. I ran into that via my google alert on Qt Creator, but was not able to ever hunt down any code. I think I tried to contact the author once, but did not get any reply.

It will most likely not even compile against a new version of Creator (provided nobody kept updating the plugin).

Pitty. I would have liked to see it work.

On the other hand: I find it hard to get/keep plugins working with Creator at all. It is basically impossible with the stock Creator you get from the SDK. I really hope it will become as easy to get and run plugins in Creator as it is in browsers nowadays.

Andre: You can have simple plugins that do not integrate too deeply and those are easy to keep up to date… once you want better integration it gets tricky — with browsers as well as with Qt Creator;-)

There is a simple solution though: Contribute your plugins and we’ll no longer break them out of ignorance;-)

PS: I added a UML plugin to our GSoC proposal page [wiki.qt-project.org]. Please register yourself if you would like to mentor or work on it! Other ideas are of course also welcome.

We do need more mentors, so if you want to help getting a student up to speed with Qt development, now is your chance to step up!

I think the issue is not that the code has changed that much, but that for me, as a user of Qt Creator and the plugins, I basically need to compile the whole stack from stratch to get things to work: to compile the plugin, I need to compile Creator myself. To compile creator, I need to compile Qt myself. And even then I need to manually fiddle with version numbers in files and setting up paths for compiling and linking. That does not help me get my real job done faster.

It would love to see a system where plugin developers can contribute their plugin to some central place, and for a new build of (released) build of Creator the matching builds of the plugins are created that you can then install from within the application itself. If the plugins no longer work with the newer creator, fine, don’t offer them anymore and notify the maintainer of the plugin of the breakage. The maintainer can then fix and re-commit, and the users can be notified of a new version of the plugin being available. One can dream, right?

[I] would love to see a system where…

Hear hear! That’s a great idea. I would love to see that, as well.

Yes, people mentioned that at the last Qt contributor’s summit already. Not much has happened since then, mostly since it was pretty clear that we can’t keep using our Nokia-internal build infrastructure after going open governance.

Now we need to get the Qt-project build infrastructure set up first. We are all waiting for the nightly builds, aren’t we? Once that is done we should be in a better position to get a plugin repository or something set up…

Maybe we the 2012 contributor summit is a good place to discuss this? ;-)

Hello,

I’m interesed too to give my 2cents help on this plugins.

What’ the actual QT Creator Software Enginnering environment ?

UML Tool ?
Testing Way ?
…

We don’t use UML much. Most changes are pretty small and well contained, so that is not really necessary most of the time.

We do have some unit tests (some stand alone, others built into Creator) and do squish tests on the whole application.