Adding contents #87
Adding contents #87
Conversation
…tions in the sdk section
# Conflicts: # reference_guide/project_model/sdk.md
reference_guide/project_model/sdk.md
Outdated
| To let user select an SDK, see [ProjectJdksEditor](https://upsource.jetbrains.com/idea-ce/file/idea-ce-8c9022ae739b82b2ee8f3355da98b9bbce2cb915/java/idea-ui/src/com/intellij/openapi/projectRoots/ui/ProjectJdksEditor.java). | ||
| To let user select an SDK, see [ProjectJdksEditor](upsource:///java/idea-ui/src/com/intellij/openapi/projectRoots/ui/ProjectJdksEditor.java). | ||
|
|
||
| However, it is not recommended to use "SDK" in non-IDEA IDEs. "SDK" is IntelliJ-specific (as well as `ProjectJdksEditor` mentioned above) and doesn't work in PyCharm, RubyMine, etc. |
There was a problem hiding this comment.
Can you please remove this paragraph? It's incorrect: the SDK infrastructure in the project model is fully supported in all IDEs, and is actively used at least in PyCharm and RubyMine. Only the ProjectJdksEditor is specific to IntelliJ IDEA.
There was a problem hiding this comment.
Oh..... Ok, let me change this
tutorials/annotator.md
Outdated
| title: Annotator | ||
| --- | ||
|
|
||
| Syntax highlight on a complete AST is based on [`Annotator`](upsource:///platform/analysis-api/src/com/intellij/lang/annotation/Annotator.java), |
There was a problem hiding this comment.
This topic doesn't appear to be saying anything new; why add it?
There was a problem hiding this comment.
Because it's a grey chapter. If you consider it unnecessary, we should remove it, both this file and the "Annotator" subsection in the index.
There was a problem hiding this comment.
No, there is something to be written for this topic (because annotators make sense not only for custom language developers; there are usecases when an annotator for Java is useful), but I'd rather create a topic only when there is some actual content. Before that, it's OK to leave a placeholder in the TOC.
tutorials/kotlin.md
Outdated
|
|
||
| It's not yet very well-documented but there're many good resources for learning how to write build scripts for an IntelliJ plugin with Kotlin script, like [intellij-rust](https://github.com/intellij-rust/intellij-rust/blob/master/build.gradle.kts), [julia-intellij](https://github.com/ice1000/julia-intellij/blob/master/build.gradle.kts), [covscript-intellij](https://github.com/covscript/covscript-intellij/blob/master/build.gradle.kts) or [zig-intellij](https://github.com/ice1000/zig-intellij/blob/master/build.gradle.kts). | ||
|
|
||
| `build.gradle.kts` basically look like: |
tutorials/kotlin.md
Outdated
|
|
||
| After gradle 4.4, gradle starts supporting `build.gradle.kts`, an alternative to `build.gradle` written in Kotlin. | ||
|
|
||
| It's not yet very well-documented but there're many good resources for learning how to write build scripts for an IntelliJ plugin with Kotlin script, like [intellij-rust](https://github.com/intellij-rust/intellij-rust/blob/master/build.gradle.kts), [julia-intellij](https://github.com/ice1000/julia-intellij/blob/master/build.gradle.kts), [covscript-intellij](https://github.com/covscript/covscript-intellij/blob/master/build.gradle.kts) or [zig-intellij](https://github.com/ice1000/zig-intellij/blob/master/build.gradle.kts). |
There was a problem hiding this comment.
I would not make any statements about some technology not being well-documented (it's always subjective, and even if true, will likely change soon).
| @@ -11,6 +11,8 @@ Create an empty plugin project, | |||
| see | |||
| [Creating a Plugin Project](/basics/getting_started/creating_plugin_project.md). | |||
|
|
|||
| **Attention: "module" is IntelliJ-specific.** | |||
There was a problem hiding this comment.
Once again this nees to be rephrased. Modules are not IntelliJ-specific; the UI for selecting a module type and creating a module through the project wizard is.
|
Done. |
|
Thanks a lot for your contribution! |
|
😃 My honor |
https://-based links toupsource:///