Added detailed description about extension types

[JonasHelming]

fixed #185

Contributed on behalf of STMicroelectronics

Signed-off-by: Jonas Helming jhelming@eclipsesource.com

[vince-fugnitto]

Please update the commit message, there are currently typos:

Added detailled description about extenssion types

Added detailed descriptions about extension types

I think there is still some work to be done regarding the overall content of the documentation added to make it clearer and more informative.

[alvsan09]

It would be great if the new image for extensions depicts:

• How @Theia extensions can contribute to FE and BE
• FE and BE run on different processes (and even different hosts)
• Vscode extensions and Theia plugins run in a separate process (extension host)
• The illustration can hopefully reflect the RPC communication lines between FE and BE, and FE to extensions host (via BE).
• There is a one to one relationship between the number of FE and number of plugin hosts.

The above took me sometime to understand and hopefully it would be useful for others,
I hope I got it right :-)

[JonasHelming]

Please update the commit message, there are currently typos:

Added detailled description about extenssion types

Added detailed descriptions about extension types

I think there is still some work to be done regarding the overall content of the documentation added to make it clearer and more informative.

Will do when I do the final squash

[JonasHelming]

It would be great if the new image for extensions depicts:

• How @Theia extensions can contribute to FE and BE
• FE and BE run on different processes (and even different hosts)
• Vscode extensions and Theia plugins run in a separate process (extension host)
• The illustration can hopefully reflect the RPC communication lines between FE and BE, and FE to extensions host (via BE).
• There is a one to one relationship between the number of FE and number of plugin hosts.

The above took me sometime to understand and hopefully it would be useful for others,
I hope I got it right :-)

I agree, all your points should be documented. However, I do not want to overload the diagram here, it is already a little more complex then I wanted it to be. This article is really meant as an overview. I believe your suggestion should go into a section called "architecture" or "extension architecture". Would you mind to paste your suggestion into a separate ticket?

[alvsan09]

I agree, all your points should be documented. However, I do not want to overload the diagram here, it is already a little more complex then I wanted it to be. This article is really meant as an overview. I believe your suggestion should go into a section called "architecture" or "extension architecture". Would you mind to paste your suggestion into a separate ticket?

I have created the following issues as per your suggestion: ##186 (comment)

[JonasHelming]

@vince-fugnitto : Are you waiting for Marcs review or are we good to go here?

[JonasHelming]

Please update the commit message, there are currently typos:

Added detailled description about extenssion types

Added detailed descriptions about extension types

I think there is still some work to be done regarding the overall content of the documentation added to make it clearer and more informative.

Done!

[vince-fugnitto]

I believe the changes are fine for the moment and provide additional details as to what exists currently 👍 We can always re-visit the documentation to go more in depth (and possibly technical) in future iterations.