UML Round-trip
-
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?
-
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? ;-)
-
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.