Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documantation how to add support for a new language #746

Merged
merged 2 commits into from
Aug 14, 2019
Merged

Conversation

svor
Copy link
Contributor

@svor svor commented Jul 2, 2019

Signed-off-by: Valeriy Svydenko [email protected]

What does this PR do?

Describes how to add support for a new language into Eclipse Che.

What issues does this PR fix or reference?

https://github.com/eclipse/che-docs/issues/718

@svor svor added the kind/docs label Jul 2, 2019
@svor svor requested review from rkratky and tsmaeder July 2, 2019 06:51
@svor svor requested a review from slemeur as a code owner July 2, 2019 06:51
@svor svor self-assigned this Jul 2, 2019
Copy link
Contributor

@tsmaeder tsmaeder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like it in general.

@tsmaeder tsmaeder mentioned this pull request Jul 9, 2019
19 tasks
@tsmaeder
Copy link
Contributor

@rkratky @slemeur could you review & merge if appropriate, please?

* A bulleted list of conditions that must be satisfied before the user starts following this assembly.
* You can also link to other modules or assemblies the user must follow before starting this assembly.
* Delete the section title and bullets if the assembly has no prerequisites.
* Install the latest Che-Theia plug-in Yeoman generator by running:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should it also explain from where to start? Using with stack for example?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tsmaeder tsmaeder mentioned this pull request Jul 25, 2019
20 tasks
@svor
Copy link
Contributor Author

svor commented Jul 26, 2019

@slemeur I've added such information into Additional resources

@slemeur
Copy link
Contributor

slemeur commented Jul 26, 2019

Thanks @svor. I'd prefer to also get the link in the content directly, this way it will be simpler to the reader and the information will be handy. The reader might not think that the documentation would refered at the end of the page.

@svor
Copy link
Contributor Author

svor commented Jul 26, 2019

@slemeur I added a reference about how to develop Che-theia plug-in with Yeoman in Prerequisites section.

Copy link
Contributor

@slemeur slemeur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @svor

* You can also link to other modules or assemblies the user must follow before starting this assembly.
* Delete the section title and bullets if the assembly has no prerequisites.

* Install the latest Che-Theia plug-in Yeoman generator. To do that you need to follow the documentation about link:extending-che.html#bootstrapping-che-theia-plug-in-development-with-yeoman_developing-che-theia-plug-ins[how to develop Che-Theia plug-in with Yeoman.]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why going through using a theia plugin where few lines bellow we say that the prefered way is with a VSCode ext ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because writing VS Code extensions is well documented, we don't need to repeat this here.

[discrete]
== Procedure

. Start each step with an active verb.
. Generate a sample by running `yo @theia/plugin`. When prompted, confirm the choices for *Backend plug-in*, *Samples*, and then *Language sample*. This creates a project and a ready-to-use plug-in, which provides support for XML Language Server and can be deployed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we provide a devfile for that ?

Copy link

@rkratky rkratky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. Suggestions added.

@svor svor force-pushed the sv/language branch 2 times, most recently from d2d77d3 to 31f022c Compare August 2, 2019 12:40
@svor
Copy link
Contributor Author

svor commented Aug 2, 2019

@rkratky Thanks for suggestions. The PR was updated

@sunix
Copy link
Contributor

sunix commented Aug 6, 2019

Any reason why this is done as a Theia plugin and not a VSCode extension ?

@rkratky
Copy link

rkratky commented Aug 6, 2019

Theia plugin and not a VSCode extension

@sunix, I'd suggest opening a separate issue (or sending a message to devtools-che) to discuss the intended strategic direction in this regard. This PR doesn't seem like to the right place to decide the overall Che-Theia plug-in vs. VS Code extension question.

@sunix
Copy link
Contributor

sunix commented Aug 6, 2019

@rkratky my only point is that, we already had that discussion in April in devtool-che and it was very clear at the time that when we write a extension for the IDE we choose either and in that prefered order if possible:

  • VSCode extension (with or without sidecar container)
  • Theia plugin (with or without sidecar container)
  • Theia extension.

I don't know why we don't follow that on our doc ... these parts of the documentation should guide the community to help us in growing this plugin registry https://github.com/eclipse/che-plugin-registry/tree/master/v3/plugins. As I see, 100% of our plugin are VSCode extension + sidecar container. Talking about Theia plugin is confusing.

Signed-off-by: Valeriy Svydenko <[email protected]>
MichalMaler added a commit to MichalMaler/che-docs that referenced this pull request Aug 7, 2019
@rkratky
Copy link

rkratky commented Aug 7, 2019

I don't know why we don't follow that on our doc ...

@slemeur, could you please weigh in? Should this doc be reoriented?

@sunix
Copy link
Contributor

sunix commented Aug 8, 2019

another point is that this is explaining how to create a theia plugin and build it ... and then ? how would the user try that in Che ? There are few missing important parts: test it locally or package it as a Che plugin with a sidecar containers how to test on a running Che. At least if we don't want to add all these details in here, it should guide the user and provide links to other parts of the documentation that explain how to do it.

To me this documentation is not completed.

@tsmaeder tsmaeder mentioned this pull request Aug 14, 2019
24 tasks
@sunix
Copy link
Contributor

sunix commented Aug 14, 2019

#746 (comment) @tsmaeder

Because writing VS Code extensions is well documented, we don't need to repeat this here.

Could we just add a link to it and explain how to package it in this doc ? The goal of this doc is to give a guidance to our user how to add support for a new language IN CHE ... the prefered way ... not the way that is not already documented elsewhere ...

@slemeur
Copy link
Contributor

slemeur commented Aug 14, 2019

LGTM and create an issue with clear requirements on improving this doc.
@sunix can you describe what you expected to be improve in the doc in an issue and link it to this?

@rkratky rkratky merged commit 6fd9f92 into master Aug 14, 2019
@rkratky rkratky deleted the sv/language branch August 14, 2019 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants