4e802980f2
* [webhelp] Fixes for TXP00152, TXP00002, test build 27 Jul 22:26 * [webhelp] Fixes for Part #4 TXP00010, EXCEPT decimal numbers in section titles * [webhelp] Fixes for Part #5 TXP00017 * [webhelp] Fixes for Part #4 TXP00010 - removed numbers from page section titles in "Custom Language Support Tutorial" and "Testing a Custom Language Plugin". * [webhelp] Removed numbers from page section titles in rest of project *.md files. * [new webhelp] Build #44 changes * [new webhelp] Maintenance merge from master * [new webhelp] Add placeholder file for webhelp import. * [webhelp] Correct redirects for file name changes * [webhelp] TOC not needed in webhelp * [format] {:toc} not needed for webhelp * add {:disable-links} to ensure demo links are not interpreted as real links. * Put all badges on the same line to simplify composition. * formatter.md: fix upsource link * fix some links * api_changes_list.md: remove note * migrate to webhelp - initial * fix GH edit URL * remove sdkdocs-template setup in VCS config * remove recently_updated.md * restore COC/CONTRIBUTING.md * api_changes_list.md: remove note * useful_links.md: IPE Co-authored-by: JohnHake <john.hake@jetbrains.com> Co-authored-by: Yann Cébron <yann.cebron@jetbrains.com>
3.8 KiB
The Structure View implementation used for a specific file type can be customized on many levels.
If a custom language plugin provides an implementation of the StructureView interface, it can completely replace the standard structure view implementation with a custom user interface component.
However, for most languages, this is not necessary, and the standard StructureView implementation provided by IntelliJ Platform can be reused.
The starting point for the structure view is the PsiStructureViewFactory interface, which is registered in the com.intellij.lang.psiStructureViewFactory extension point.
Examples:
PsiStructureViewFactoryfor Properties language plugin- Custom Language Support Tutorial: Structure View
To reuse the IntelliJ Platform implementation of the StructureView, the plugin returns a TreeBasedStructureViewBuilder from its PsiStructureViewFactory.getStructureViewBuilder() method.
As the builder model, the plugin can specify a subclass of TextEditorBasedStructureViewModel, and by overriding methods of this subclass, it customizes the structure view for a specific language.
Example:
StructureViewModel for Properties language plugin
The main method to override is getRoot(), which returns the instance of a class implementing the StructureViewTreeElement interface.
There exists no standard implementation of this interface, so a plugin will need to implement it completely.
The structure view tree is usually built as a partial mirror of the PSI tree.
In the implementation of StructureViewTreeElement.getChildren(), the plugin can specify which of the child elements of a specific PSI tree node need to be represented as elements in the structure view.
Another important method is getPresentation(), which can be used to customize the text, attributes, and icon used to represent an element in the structure view.
The implementation of StructureViewTreeElement.getChildren() needs to be matched by TextEditorBasedStructureViewModel.getSuitableClasses().
The latter method returns an array of PsiElement-derived classes, which can be shown as structure view elements.
It is used to select the Structure View item matching the cursor position when the structure view is first opened or when the Autoscroll from source option is enabled.
Example:
StructureViewTreeElement for Properties language plugin