[Solved] "Git is not available" error with Qt creator 2.6.0

koahnig · wrote on 28 Nov 2012, 19:58

I have installed Qt creator 2.6.0 and only subversion installed.
Whatever I do with subversion I am getting the error message "Git is not available."
I have Git not installed and the "Options"/"Version Control" settings for Git are on their default values. Do I miss another place to switch Git off?

sierdzio · wrote on 29 Nov 2012, 06:40

You can manage plugins here:
Help->About Plugins...

koahnig · wrote on 30 Nov 2012, 14:46

Thanks that helped.
I didn't think of that as a plugins issue.

However, switching off all but Subversion plugin brought another problem. There is apparently a problem with the dialog. When the last plugin (Vcbase) is switched off, only Subversion plugin has the check mark, all entries including the Subversion entry will be greyed out. Furthermore, subversion entry will not be present under "Tools" anymore.
However, other plugins than Gitorious may be switched on when not installed. Only Vcbase is required to be able to access the subversion.

koahnig · wrote on 30 Nov 2012, 15:51

Bug report on JIRA filed "QTCREATORBUG-8360":https://bugreports.qt-project.org/browse/QTCREATORBUG-8360

tobias.hunger · wrote on 30 Nov 2012, 16:08

... and rejected;-)

koahnig · wrote on 30 Nov 2012, 16:38

[quote author="Tobias Hunger" date="1354291700"]... and rejected;-)[/quote]

OK, the naming is not really obvious at first sight. Maybe a couple more letters are appreciated.
If possible, you could use "VcsBase(required for all)" or place on first position in the menu.

tobias.hunger · wrote on 30 Nov 2012, 21:22

I am not aware of any changes in this area since I joined the team before the 1.3 release, so it is rather well tested code that nobody complained about so far. Not that this makes it perfect or anything, but it is a sign that it is either obvious or so rarely used that nobody will notice changes for a couple of years;-)

The plugins are sorted alphabetically. There are lots of dependencies between plugins, I really do not think it makes much sense to put plugins others depend upon at the top. That would break the grouping... most plugins depend on projectexplorer and core, many on texteditor, so where should those get listed?

You can check the details of a plugin for the dependencies needed for it to function (in case it is disabled and you want to use it).

sierdzio · wrote on 30 Nov 2012, 21:51

I find the current state rather good and intuitive, I don't remember any problems in understanding. In fact, Qt Creator is the best IDE I used to date :)

Well, just felt the need to say that, without giving any really constructive argument. Srx.

koahnig · wrote on 1 Dec 2012, 12:13

Well, I have started using creator more often lately. Without knowing details on plugins, it is not obvious at first sight that VcsBase is the basis of all other plugins in that category. I had rated it simply as another tool similar to subversion.

Only after your response (Tobias) I had a closer look at the plugin's name, but it took me a bit of time. At first I thought my report was missing information.

@sierdzio I am not questioning the quality of creator. Probably running through the starting pains with it at this time. ;-)

sierdzio · wrote on 1 Dec 2012, 12:28

[quote author="koahnig" date="1354363984"]@sierdzio I am not questioning the quality of creator. Probably running through the starting pains with it at this time. ;-) [/quote]

I know, that's why I felt so reluctant to share my feelings - I knew it would sound out of place in this conversation ;) and it's why I apologised in advance. Have a good weekend, both of you!

tobias.hunger · wrote on 1 Dec 2012, 13:45

koahnig: If you have an idea of how to improve this, please tell me:-) I think the current grouping based on related functionality makes more sense than grouping the plugins by dependencies (which is mostly a implementation detail of the plugin after all).

koahnig · wrote on 1 Dec 2012, 15:07

[quote author="koahnig" date="1354293497"]
If possible, you could use "VcsBase(required for all)" or place on first position in the menu.
[/quote]
I do not know if this suggestion or something similar is possible at all. However, it would have stopped me from writing a bug report.
I am not a beginner and, therefore, typically careful enough not to cry that there is a bug(problem) everywhere but not in my code.
Such a dependency as in this case is not obvious.

More out of curiosity, am I correct that "VcsBase" is simply the requirement for all the others and has no subversioning functionality on its own?

Another possibility for improving the plugin menu could be to mark plugins required by others in general. This could be either coloring or an additional symbol. If more sub-grouping levels are possible, it could be also that only "VcsBase" builds the first level and all the others are in a sub-level.
However, I have no idea if this could be realized easily. Sometimes those suggestions are easy to come up with, but hard to implement. ;-)

Certainly, I would not mess the current overall grouping. It makes sense to me.

sierdzio · wrote on 1 Dec 2012, 15:28

[quote author="koahnig" date="1354374444"]Another possibility for improving the plugin menu could be to mark plugins required by others in general.[/quote]

Since we are at it, would it not be more appropriate to move the whole Plugins menu into Tools->Options?

tobias.hunger · wrote on 1 Dec 2012, 15:55

Check the plugins: They tend to depend on several several plugins. E.g. subversion depends on TextEditor, ProjectExplorer, VcsBase and Core. Some plugins have soft dependencies as well (they will work without some other plugin, but they can't offer the full functionality).

Displaying all that information will make things rather complex. I really prefer the really simple tree we have with its grouping based on functionality.

koahnig · wrote on 1 Dec 2012, 16:04

[quote author="Tobias Hunger" date="1354377301"]Check the plugins: They tend to depend on several several plugins. E.g. subversion depends on TextEditor, ProjectExplorer, VcsBase and Core. Some plugins have soft dependencies as well (they will work without some other plugin, but they can't offer the full functionality).

Displaying all that information will make things rather complex. I really prefer the really simple tree we have with its grouping based on functionality.[/quote]
Agreed. With this complexity it is impossible to get a meaningful tree structure. Still learning. :D

[quote author="sierdzio" date="1354375684"]...
Since we are at it, would it not be more appropriate to move the whole Plugins menu into Tools->Options?
[/quote]

I would support this suggestion. When looking for the original problem, I certainly never thought of options under help. Even so I was definitely in the plugins menu already.