hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-30 18:27:49 +08:00
Code Issues Packages Projects Releases Wiki Activity

[md] Links to initial sources to confluence dropped

Browse Source
This commit is contained in:
Anna Bulenkova 2015-04-14 10:36:40 +02:00
parent 1e67b732f3
commit 2e1a13e356
64 changed files with 0 additions and 320 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
HOWTO.md
View File

@ -1,16 +1,6 @@
Rules for migrating documents from other sources Rules for migrating documents from other sources
==== ====
#Tracking content source
If you migrate any documents from other sources (e.g. Confluence of Development Forum) to IntelliJ Doc Engine,
please mark the newly created Markdown file with INITIAL_SOURCE tag like the following sample shows.
```
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Build+Number+Ranges
-->
```
#TODOs and issues under development #TODOs and issues under development
Any issues in a document needed to be re-worked, extended, and\/or newly written should be marked with. Any issues in a document needed to be re-worked, extended, and\/or newly written should be marked with.

7
action_system.md
View File

@ -3,13 +3,6 @@ layout: editable
title: Action System title: Action System
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+Action+System
-->
## Executing and Updating Actions ## Executing and Updating Actions
The system of actions allows plugins to add their own items to IDEA menus and toolbars. The system of actions allows plugins to add their own items to IDEA menus and toolbars.

4
annotator.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Annotator title: Annotator
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Annotator
-->
Annotator helps highlight and annotate any code based on specific rules. Annotator helps highlight and annotate any code based on specific rules.
### 1. Define an annotator ### 1. Define an annotator

6
annotator_test.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Annotator Test title: Annotator Test
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Annotator+Test
-->
In this test we will check if the annotator, implemented in the In this test we will check if the annotator, implemented in the
[Annotator](annotator.html) section [Annotator](annotator.html) section
of the of the

4
architectural_overview.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Architectural Overview title: Architectural Overview
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+Architectural+Overview
-->
The goal of this topic is to describe the architecture of IntelliJ IDEA from a plugin developer's point of view. It will be organized in a The goal of this topic is to describe the architecture of IntelliJ IDEA from a plugin developer's point of view. It will be organized in a
task-based manner: rather than listing all the things that you can do with each object and describing how they are all implemented, it will try task-based manner: rather than listing all the things that you can do with each object and describing how they are all implemented, it will try
to answer questions "what can I do with this object", "how do I get to this object" and so on. to answer questions "what can I do with this object", "how do I get to this object" and so on.

6
build_number_ranges.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Build Number Ranges title: Build Number Ranges
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Build+Number+Ranges
-->
This reference of build number ranges can be used to specify correct since-build and until-build versions in the This reference of build number ranges can be used to specify correct since-build and until-build versions in the
<!--TODO link to file in sample--> <!--TODO link to file in sample-->
[plugin.xml]() [plugin.xml]()

5
cls_prerequisites.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Prerequisites title: Prerequisites
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Prerequisites
-->
### 1. Download and install IntelliJ IDEA ### 1. Download and install IntelliJ IDEA

6
cls_tutorial.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Custom Language Support Tutorial title: Custom Language Support Tutorial
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Custom+Language+Support
-->
In this tutorial we will add basic support for In this tutorial we will add basic support for
[.properties](http://en.wikipedia.org/wiki/.properties) [.properties](http://en.wikipedia.org/wiki/.properties)
language and it's usages within Java code. language and it's usages within Java code.

4
code_style_settings.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Code Style Setting title: Code Style Setting
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Code+Style+Settings
-->
### 1. Define code style settings ### 1. Define code style settings
```java ```java

6
color_scheme_management.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Color Scheme Management in Intellij IDEA 12.1+ title: Color Scheme Management in Intellij IDEA 12.1+
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/pages/viewpage.action?pageId=49463468
-->
# Preface # Preface
Color scheme management in Intellij IDEA 12.1 was changed to ease the work of scheme designers and make schemes look equally well for different programming languages even if not designed specifically for these languages. Previously language plug-ins were using fixed default colors incompatible, for example, with dark schemes. The new implementation allows to specify a dependency on a set of standard text attributes which are linked to a scheme but not to any specific language. Language-specific attributes still can be set by a scheme designer if needed but it's optional. New color schemes have got a new .icls (Idea CoLor Scheme) extension to avoid confusion about compatibility problems with older platform versions: Color scheme management in Intellij IDEA 12.1 was changed to ease the work of scheme designers and make schemes look equally well for different programming languages even if not designed specifically for these languages. Previously language plug-ins were using fixed default colors incompatible, for example, with dark schemes. The new implementation allows to specify a dependency on a set of standard text attributes which are linked to a scheme but not to any specific language. Language-specific attributes still can be set by a scheme designer if needed but it's optional. New color schemes have got a new .icls (Idea CoLor Scheme) extension to avoid confusion about compatibility problems with older platform versions:

4
commenter.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Commenter title: Commenter
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Commenter
-->
A commenter allows user to comment the code at the cursor or selected code automatically via *⌘/*. A commenter allows user to comment the code at the cursor or selected code automatically via *⌘/*.
### 1. Define a commenter ### 1. Define a commenter

6
commenter_test.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Commenter Test title: Commenter Test
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Commenter+Test
-->
In this test we will check if the commenter, implemented in the In this test we will check if the commenter, implemented in the
[Commenter](commenter.html) [Commenter](commenter.html)
section of the section of the

3
completion_contributor.md
View File

@ -3,9 +3,6 @@ layout: editable
title: Completion Contributor title: Completion Contributor
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Completion+Contributor
-->
The easiest way to provide completion is to use a completion contributor. The easiest way to provide completion is to use a completion contributor.

5
completion_test.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Completion Test title: Completion Test
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Completion+Test
-->
In this test we will check if code completion, implemented in the In this test we will check if code completion, implemented in the
[Reference Contributor](reference_contributor.html) section [Reference Contributor](reference_contributor.html) section

2
creating_plugin_project.md
View File

@ -3,8 +3,6 @@ layout: editable
title: Creating a Plugin Project title: Creating a Plugin Project
--- ---
This section explains how you can create a new plugin project from a scratch using the New Project wizard. This section explains how you can create a new plugin project from a scratch using the New Project wizard.
Optionally, you can import an existing project or import a project from external models. Optionally, you can import an existing project or import a project from external models.
You can also add a new plugin module to an existing *Intellij IDEA* project. You can also add a new plugin module to an existing *Intellij IDEA* project.

6
custom_language_support.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Custom Language Support title: Custom Language Support
--- ---
<!--
INITIAL_SOURCE http://confluence.jetbrains.com/display/IDEADEV/Developing+Custom+Language+Plugins+for+IntelliJ+IDEA
-->
Please ask questions or suggest missing topics in [plugin development forum](http://devnet.jetbrains.com/community/idea/open_api_and_plugin_development). Please ask questions or suggest missing topics in [plugin development forum](http://devnet.jetbrains.com/community/idea/open_api_and_plugin_development).
## Introduction ## Introduction

5
dialog_wrapper.md
View File

@ -3,11 +3,6 @@ layout: editable
title: DialogWrapper title: DialogWrapper
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+DialogWrapper
-->
## DialogWrapper ## DialogWrapper

6
editor_components.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Editor Components title: Editor Components
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Editor+Components
-->
## EditorTextField ## EditorTextField
Compared to Compared to

6
external_builder_api.md
View File

@ -3,12 +3,6 @@ layout: editable
title: External Builder API and Plugins title: External Builder API and Plugins
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/External+Builder+API+and+Plugins
-->
### External Build Process Workflow ### External Build Process Workflow
When the user invokes an action that involves executing an external build (Make, Build Artifacts, etc.), the following steps happen: When the user invokes an action that involves executing an external build (Make, Build Artifacts, etc.), the following steps happen:

5
faq.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Plugin Development FAQ title: Plugin Development FAQ
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Plugin+Development+FAQ
-->
This FAQ is a topical index of questions that have been asked (and answered) on our This FAQ is a topical index of questions that have been asked (and answered) on our
[OpenAPI forum](http://intellij.net/forums/forum.jspa?forumID=23) [OpenAPI forum](http://intellij.net/forums/forum.jspa?forumID=23)

6
file_and_class_choosers.md
View File

@ -3,12 +3,6 @@ layout: editable
title: File and Class Choosers title: File and Class Choosers
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/File+and+Class+Choosers
-->
## File Choosers ## File Choosers
To let a user choose a file, directory or multiple files, use the To let a user choose a file, directory or multiple files, use the

4
find_usages_provider.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Find Usages Provider title: Find Usages Provider
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Find+Usages+Provider
-->
A find usage provider uses a word scanner to build an index of words present in every file. A find usage provider uses a word scanner to build an index of words present in every file.
A scanner breaks the text into words, defines the context for each word and passes it to the find usage provider. A scanner breaks the text into words, defines the context for each word and passes it to the find usage provider.

6
find_usages_test.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Find Usages Test title: Find Usages Test
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Find+Usages+Test
-->
In this test we will check if the find usages provider, implemented in the In this test we will check if the find usages provider, implemented in the
[Find Usages Provider](find_usages_provider.html) [Find Usages Provider](find_usages_provider.html)
section of the section of the

4
folding_builder.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Folding Builder title: Folding Builder
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Folding+Builder
-->
A folding builder helps you to fold the code regions and replace it with specific text. A folding builder helps you to fold the code regions and replace it with specific text.
### 1. Define a folding builder ### 1. Define a folding builder

6
folding_test.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Folding Test title: Folding Test
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Folding+Test
-->
In this test we will check if the folding builder, implemented in the In this test we will check if the folding builder, implemented in the
[Folding Builder](folding_builder.html) [Folding Builder](folding_builder.html)
section of the section of the

4
formatter.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Formatter title: Formatter
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Formatter
-->
*A formatter allows to reformat the code automatically based on code style settings.* *A formatter allows to reformat the code automatically based on code style settings.*
### 1. Define a block ### 1. Define a block

6
formatter_test.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Formatter Test title: Formatter Test
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Formatter+Test
-->
In this test we will check if the formatter, implemented in the In this test we will check if the formatter, implemented in the
[Formatter](formatter.html) [Formatter](formatter.html)
section of the section of the

4
go_to_symbol_contributor.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Go To Symbol Contributor title: Go To Symbol Contributor
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Go+To+Symbol+Contributor
-->
*A go to symbol contributor helps user to navigate to any PSI element by it's name.* *A go to symbol contributor helps user to navigate to any PSI element by it's name.*
### 1. Define helper method for generated PSI elements ### 1. Define helper method for generated PSI elements

6
grammar_and_parser.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Grammar and Parser title: Grammar and Parser
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Grammar+and+Parser
-->
### 1. Define a token type ### 1. Define a token type
```java ```java

7
indexing_and_psi_stubs.md
View File

@ -3,13 +3,6 @@ layout: editable
title: Indexing and PSI Stubs title: Indexing and PSI Stubs
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Indexing+and+PSI+Stubs+in+IntelliJ+IDEA
-->
## Introduction ## Introduction
The indexing framework provides a quick way to locate certain elements (for example, files containing a certain word or methods with a particular name) in large code bases. Plugin developers can use the existing indexes built by the IDE itself, as well as build and use their own indexes. The indexing framework provides a quick way to locate certain elements (for example, files containing a certain word or methods with a particular name) in large code bases. Plugin developers can use the existing indexes built by the IDE itself, as well as build and use their own indexes.

5
language_and_filetype.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Language and File Type title: Language and File Type
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Language+and+File+Type
-->
### 1. Define a language ### 1. Define a language

6
lexer_and_parser_definition.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Lexer and Parser Definition title: Lexer and Parser Definition
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Lexer+and+Parser+Definition
-->
The lexer defines how the contents of a file is broken into tokens. The lexer defines how the contents of a file is broken into tokens.
The easiest way to create a lexer is to use [JFlex](http://jflex.de/) The easiest way to create a lexer is to use [JFlex](http://jflex.de/)

4
line_marker_provider.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Line Marker Provider title: Line Marker Provider
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Line+Marker+Provider
-->
Line markers help to annotate any code with icons on the gutter. Line markers help to annotate any code with icons on the gutter.
These icons may provide navigation to related code. These icons may provide navigation to related code.

5
lists_and_trees.md
View File

@ -3,11 +3,6 @@ layout: editable
title: List and Tree Controls title: List and Tree Controls
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+List+and+Tree+Controls
-->
### JBList and Tree ### JBList and Tree

5
localization_guide.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Localization Guide title: Localization Guide
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Localization+Guide+for+IntelliJ+IDEA
-->
The purpose of the document is to describe steps necessary to create localized versions of IDEA. The purpose of the document is to describe steps necessary to create localized versions of IDEA.

5
messaging_infrastructure.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Messaging infrastructure title: Messaging infrastructure
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+Messaging+infrastructure
-->
# Purpose # Purpose

5
misc_swing_components.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Miscellaneous Swing Components title: Miscellaneous Swing Components
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Miscellaneous+Swing+Components
-->
### Messages ### Messages

5
multiple_carets.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Supporting multiple carets title: Supporting multiple carets
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Supporting+multiple+carets
-->
## Introduction ## Introduction

5
notifications.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Notifications title: Notifications
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+Notifications
-->
## Notifications ## Notifications

5
parsing_test.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Parsing Test title: Parsing Test
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Parsing+Test
-->
The first test will check if the parser, implemented in the The first test will check if the parser, implemented in the
[Lexer and Parser Definition](lexer_und_parser_definition.html) [Lexer and Parser Definition](lexer_und_parser_definition.html)

3
persisting_state.md
View File

@ -3,9 +3,6 @@ layout: editable
title: Persisting State of Components title: Persisting State of Components
--- ---
<!--INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Persisting+State+of+Components-->
The IntelliJ Platform provides an API that allows components or services to persist their state between restarts of the IDE. The IntelliJ Platform provides an API that allows components or services to persist their state between restarts of the IDE.
You can use either a simple API to persist a few values, or persist the state of more complicated components using the You can use either a simple API to persist a few values, or persist the state of more complicated components using the

4
plugin_compatibility.md
View File

@ -3,10 +3,6 @@ layout: editable
title: Plugin Compatibility with IntelliJ Platform Products title: Plugin Compatibility with IntelliJ Platform Products
--- ---
<!--INITIAL_SOURCE
https://confluence.jetbrains.com/display/IDEADEV/Plugin+Compatibility+with+IntelliJ+Platform+Products
-->
# {{page.title}} # {{page.title}}
All products based on the IntelliJ Platform (IntelliJ IDEA, RubyMine, WebStorm, PhpStorm, PyCharm and AppCode) share the same underlying platform API. All products based on the IntelliJ Platform (IntelliJ IDEA, RubyMine, WebStorm, PhpStorm, PyCharm and AppCode) share the same underlying platform API.

5
plugin_structure.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Plugin Structure title: Plugin Structure
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+Plugin+Structure
-->
Plugins are the only supported way to extend IDEA functionality. Plugins are the only supported way to extend IDEA functionality.
A plugin uses API exposed by IDEA or other plugins to implement its functionality. A plugin uses API exposed by IDEA or other plugins to implement its functionality.

5
popups.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Popups title: Popups
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+Popups
-->
## Popups ## Popups

5
project_structure.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Structure of Project title: Structure of Project
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Structure+of+IntelliJ+IDEA+Project
-->
<!--TODO split into parts accordingly to the table of contents--> <!--TODO split into parts accordingly to the table of contents-->
This topic considers the concept of **IntelliJ IDEA** projects and related subjects, such as _modules_, _facets_, _libraries_, _SDK_. This topic considers the concept of **IntelliJ IDEA** projects and related subjects, such as _modules_, _facets_, _libraries_, _SDK_.

5
psi_cookbook.md
View File

@ -3,11 +3,6 @@ layout: editable
title: PSI Cookbook title: PSI Cookbook
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/PSI+Cookbook
-->
This page gives a list of recipes for the most common operations for working with the PSI (Program Structure Interface) in IntelliJ IDEA. Unlike [Developing Custom Language Plugins for IntelliJ IDEA], it talks about working with the PSI of existing languages (such as Java). This page gives a list of recipes for the most common operations for working with the PSI (Program Structure Interface) in IntelliJ IDEA. Unlike [Developing Custom Language Plugins for IntelliJ IDEA], it talks about working with the PSI of existing languages (such as Java).

5
psi_helper_and_utilities.md
View File

@ -3,11 +3,6 @@ layout: editable
title: PSI Helpers and Utilities title: PSI Helpers and Utilities
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/PSI+Helpers+and+Utilities
-->
### 1. Define helper methods for generated PSI elements ### 1. Define helper methods for generated PSI elements

3
quick_fix.md
View File

@ -3,9 +3,6 @@ layout: editable
title: Quick Fix title: Quick Fix
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Quick+Fix
-->
A quick fix allows to apply an automatic changes to the code via *⌥⏎*. A quick fix allows to apply an automatic changes to the code via *⌥⏎*.

3
reference_contributor.md
View File

@ -3,9 +3,6 @@ layout: editable
title: Reference Contributor title: Reference Contributor
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Reference+Contributor
-->
References is one of the most important and tricky parts in the implementation of a custom language support. References is one of the most important and tricky parts in the implementation of a custom language support.
Resolving references means the ability to go from the usage of an element to the declaration of the element, completion, rename refactoring, find usages, etc. Resolving references means the ability to go from the usage of an element to the declaration of the element, completion, rename refactoring, find usages, etc.

5
reference_test.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Reference Test title: Reference Test
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Reference+Test
-->
In this test we will check if references, implemented in the In this test we will check if references, implemented in the
[Reference Contributor](reference_contributor.html) [Reference Contributor](reference_contributor.html)

5
rename_test.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Rename Test title: Rename Test
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Rename+Test
-->
In this test we will check if in-place rename, implemented in the In this test we will check if in-place rename, implemented in the
[Reference Contributor](reference_contributor.html) [Reference Contributor](reference_contributor.html)

5
run_configurations.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Run Configurations title: Run Configurations
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Run+Configurations
-->
# Purpose # Purpose

6
spring_api.md
View File

@ -3,12 +3,6 @@ layout: editable
title: Spring API title: Spring API
--- ---
<!--
INITIAL_SOURCE http://confluence.jetbrains.com/display/IDEADEV/Spring+API+Guide
-->
## Using Spring-API ## Using Spring-API
To develop plugins integrating with Spring-API you will need to use IntelliJ IDEA _Ultimate Edition_ version 13.1 (or higher). To develop plugins integrating with Spring-API you will need to use IntelliJ IDEA _Ultimate Edition_ version 13.1 (or higher).

3
structure_view_factory.md
View File

@ -3,9 +3,6 @@ layout: editable
title: Structure View Factory title: Structure View Factory
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Structure+View+Factory
-->
A structure view factory allows to show the structure of any file in a *Structure* tool window for easy navigation between items. A structure view factory allows to show the structure of any file in a *Structure* tool window for easy navigation between items.

5
syntax_highlighter_and_color_settings_page.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Syntax Highlighter and Color Settings Page title: Syntax Highlighter and Color Settings Page
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Syntax+Highlighter+and+Color+Settings+Page
-->
### 1. Define a syntax highlighter ### 1. Define a syntax highlighter

3
testing_plugins.md
View File

@ -3,9 +3,6 @@ layout: editable
title: Testing Plugins title: Testing Plugins
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Testing+IntelliJ+IDEA+Plugins
-->
## General Testing Approach ## General Testing Approach

5
tests_prerequisites.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Tests Prerequisites title: Tests Prerequisites
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Tests+Prerequisites
-->
### 1. Create a folder for tests ### 1. Create a folder for tests

5
tomcat_integration.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Tomcat Integration title: Tomcat Integration
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Tomcat+Integration
-->
The source code of the Tomcat plugin included in IntelliJ IDEA Ultimate is available as a sample for implementing application server integration plugins. The source code of the Tomcat plugin included in IntelliJ IDEA Ultimate is available as a sample for implementing application server integration plugins.
You can find the code under *lib\src\src_tomcat.zip* in the main IntelliJ IDEA Ultimate distribution. You can find the code under *lib\src\src_tomcat.zip* in the main IntelliJ IDEA Ultimate distribution.

5
tool_windows.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Tool Windows title: Tool Windows
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+Tool+Windows
-->
## Tool Windows ## Tool Windows

5
ui_components.md
View File

@ -3,11 +3,6 @@ layout: editable
title: User Interface Components title: User Interface Components
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+User+Interface+Components
-->
The IntelliJ Platform includes a large number of custom Swing components. Using those components in your plugins will ensure that your plugin looks and works consistently with the UI of the rest of the IDE, and can often reduce the code size compared to using the default Swing components. The IntelliJ Platform includes a large number of custom Swing components. Using those components in your plugins will ensure that your plugin looks and works consistently with the UI of the rest of the IDE, and can often reduce the code size compared to using the default Swing components.

5
virtual_file_system.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Virtual File System title: Virtual File System
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/IntelliJ+IDEA+Virtual+File+System
-->
The virtual file system (VFS) is a component of IntelliJ IDEA that encapsulates most of its activity for working with files. It serves the following main purposes: The virtual file system (VFS) is a component of IntelliJ IDEA that encapsulates most of its activity for working with files. It serves the following main purposes:

5
work_with_icons_and_images.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Work with Icons and Images title: Work with Icons and Images
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IDEADEV/Work+with+Icons+and+Images
-->
Icons and images are used widely by IntelliJ IDEA plugins. Icons and images are used widely by IntelliJ IDEA plugins.
Plugins need icons mostly for actions, custom components renderers, tool windows and so on. Plugins need icons mostly for actions, custom components renderers, tool windows and so on.

5
writing_tests_for_plugins.md
View File

@ -3,11 +3,6 @@ layout: editable
title: Writing Tests For Plugins title: Writing Tests For Plugins
--- ---
<!--
INITIAL_SOURCE https://confluence.jetbrains.com/display/IntelliJIDEA/Writing+Tests+for+Plugins
-->
In this tutorial you will learn how to write and run automated tests for your plugin. In this tutorial you will learn how to write and run automated tests for your plugin.

6
xml_dom_api.md
View File

@ -1,14 +1,8 @@
--- ---
layout: editable layout: editable
title: XML DOM API title: XML DOM API
--- ---
<!--
INITIAL_SOURCE http://confluence.jetbrains.com/display/IDEADEV/Accessing+XML+through+IntelliJ+IDEA+DOM
-->
<!-- TODO content: DOM <=> PSI, Go To Symbol, editor gutter icon->DOM --> <!-- TODO content: DOM <=> PSI, Go To Symbol, editor gutter icon->DOM -->