FMF should be closer to QtCreator

[GoogleCodeExporter]

This is just an idea, and I don't want to loose it, so I keep it here.

FMF should keep it's source closer to QtCreator. It was forked off somewhat 
QtCreator 2.1, at the moment I am writing there is coming out 2.6.
Much has changed since then:
* plugins directories are not called "fooplugin", but just "foo"
* foo.pluginspec now is foo.pluginspec.in to enable templates

, just to  mention two (I remember just new) of many, many other changes and 
bug fixes.

We should be closer to the QtCreator "upstream" code, as this provides:

* easier upgrade path when a new QtCreator version comes out
* additional bugs fixed without finding and merging them from the upstream code
* interoperability with the QtCreator team
* maybe giving back some improvements (making QtCreator a better choice for 
Rich Client applications)
* etc, etc.

Original issue reported on code.google.com by christian.a.reiter@gmail.com on 28 Oct 2012 at 8:38

[GoogleCodeExporter]

This is really hard, as some features are not included in QtCreator (eg: 
auto-translation of registered action in ActionManager). Each time we update 
the ActionManager we have to re-add/adapt our patch...
Last lib update (from QtC2.1 -> QtC 2.5.2) was painful as many changes occur in 
the UI management/MainWindow.
I believe there are many common code that we can easily update. With one only 
restriction, keep yourself informed of the QtC update + FMF updates... Which 
sounds not simple :D

Original comment by eric.mae...@gmail.com on 28 Oct 2012 at 9:23

[GoogleCodeExporter]

Yes, maybe some things are not too easy. But exactly for e.g. the 
autotranslation of the registered action we could submit a good patch to 
upstream, if it made sense? Then we would not need to reapply the patch each 
time, and QtCreator benefits too.

Then, e.g. we could use more of QtCreators capabilities. In the FMF main form 
view, the whole widget is a custom widget with a FormTreeView and the Episode 
Toolbar/ FormDataWidgetMapper on the right.
This would be nicer with the QtCreator built-in Core::NavigationView and 
INavigationWidgetFactory (the left part where navigation happens in QtCreator).

Original comment by christian.a.reiter@gmail.com on 28 Oct 2012 at 10:38

[GoogleCodeExporter]

After considering many things like keeping up to date the code, a relatively 
small codebase that is taken from QtC, and the effort, and OTOH the very small 
benefit as most of the QtC API is perfectly stable according to the Devs.

So We could close this bug, as it is not really necessary/important.

Original comment by christian.a.reiter@gmail.com on 4 Dec 2012 at 11:29

• Changed state: WontFix