mirror of
https://github.com/JetBrains/intellij-sdk-code-samples.git
synced 2025-07-28 01:07:49 +08:00
[site] cosmetics
This commit is contained in:
parent
b09beecf53
commit
91a1b1b664
@ -18,7 +18,7 @@ For example, the Run toolwindow displays a tab for each active run configuration
|
|||||||
|
|
||||||
There are two main scenarios for the use of tool windows in a plugin.
|
There are two main scenarios for the use of tool windows in a plugin.
|
||||||
In the first scenario (used by the Ant and Commander plugins, for example), a toolwindow button is always visible, and the user can activate it and interact with the plugin functionality at any time.
|
In the first scenario (used by the Ant and Commander plugins, for example), a toolwindow button is always visible, and the user can activate it and interact with the plugin functionality at any time.
|
||||||
In the second scenario (used by the Analyze Dependencies action, for example), the toolwindow is created to show the results of a specific operation, and can be closed by the user after the operation is completed.
|
In the second scenario (used by the ```Analyze Dependencies``` action, for example), the toolwindow is created to show the results of a specific operation, and can be closed by the user after the operation is completed.
|
||||||
|
|
||||||
In the first scenario, the toolwindow is registered in *plugin.xml* using the ```<toolWindow>``` extension point.
|
In the first scenario, the toolwindow is registered in *plugin.xml* using the ```<toolWindow>``` extension point.
|
||||||
The extension point attributes specify all the data which is necessary to display the toolwindow button:
|
The extension point attributes specify all the data which is necessary to display the toolwindow button:
|
||||||
|
Loading…
x
Reference in New Issue
Block a user