feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Doc: enabling and disabling plugin dependencies

Browse Source 
This now happens automatically and disabled plugins
are no longer a problem after version upgrade even if
plugin dependencies have changed.

Change-Id: I06456c81c2ad2fab5730562a4df407cf178fd1cf
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
This commit is contained in:
Leena Miettinen
2015-04-02 15:50:24 +02:00
parent 549590a249
commit 6b27bcefb4
2 changed files with 16 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
doc/src/howto/creator-cli.qdoc
View File

@@ -108,11 +108,22 @@
\row \row
\li -load <plugin> \li -load <plugin>
\li Load the specified plugin. \li Enable the specified plugin and all plugins that it depends on.
You can combine \c -load and \c -noload options and specify both
options multiple times to enable and disable several plugins.
The actions are executed in the specified order.
\row
\li -load all
\li Enables all plugins.
\row \row
\li -noload <plugin> \li -noload <plugin>
\li Do not load the specified plugin. \li Disable the specified plugin and all plugins that depend on it.
\row
\li -noload all
\li Disables all plugins.
\row \row
\li -profile \li -profile

8
doc/src/overview/creator-configuring.qdoc
View File

@@ -158,13 +158,11 @@
New \QC plugins are often introduced as \e {experimental plugins} to let New \QC plugins are often introduced as \e {experimental plugins} to let
you try them out before they are fully supported. Experimental plugins you try them out before they are fully supported. Experimental plugins
are disabled by default and you must enable them for them to become visible are disabled by default and you must enable them for them to become visible
after you restart \QC. after you restart \QC. By default, all the plugins that the plugin depends
on are also enabled.
You can also disable plugins that you do not use, to streamline \QC. You can also disable plugins that you do not use, to streamline \QC.
However, this might cause problems when using another plugin later if the By default, all the plugins that depend on the plugin are also disabled.
dependencies between plugins are changed between \QC versions. Once you
manually disable a plugin, it stays disabled even when you upgrade to a
new \QC version, and you must manually enable it to be able to use it.
To enable and disable plugins, select \uicontrol Help > \uicontrol {About Plugins}. To enable and disable plugins, select \uicontrol Help > \uicontrol {About Plugins}.