Added Theia project goals #280
Conversation
Signed-off-by: Jonas Helming <jhelming@eclipsesource.com>
Co-authored-by: colin-grant-work <colin.grant@est.tech>
Co-authored-by: colin-grant-work <colin.grant@est.tech>
Co-authored-by: colin-grant-work <colin.grant@est.tech>
Co-authored-by: colin-grant-work <colin.grant@est.tech>
Co-authored-by: colin-grant-work <colin.grant@est.tech>
Co-authored-by: colin-grant-work <colin.grant@est.tech>
Co-authored-by: colin-grant-work <colin.grant@est.tech>
Co-authored-by: colin-grant-work <colin.grant@est.tech>
Co-authored-by: colin-grant-work <colin.grant@est.tech>
|
@colin-grant-work Thank you for this great review! |
|
|
||
| Theia provides a workbench frame, i.e., a window management system permitting the display of views, editors, and menus and makes available tools and interactions allowing the user to modify of the window layout, trigger commands, and use key bindings and other concepts known from a desktop tool such as drag and drop. | ||
|
|
||
| ## Reusable Common Tool Features |
There was a problem hiding this comment.
minor: we might want a better title for this section.
There was a problem hiding this comment.
Do you have a suggestion?
There was a problem hiding this comment.
I'm not sure, perhaps Reusable and Extensible Components? If I understand correctly you're trying to describe how extensions which contribute functionality to the framework can be re-used across different products and can be extended to suit an application's potentially unique requirements. I did not understand the use of "tool features" in this context.
There was a problem hiding this comment.
What if we moved this paragraph into the next section? Reusability is what facilitates 'Extensibility and Adaptability': we provide components that are generic enough to be of interest to a variety of tools, and they're flexible enough to be reused with customizations.
There was a problem hiding this comment.
Hmm, I am not sure about this. I personally find the fact that the platform provides features that you can resue important enough for a dedicated point. It is one of the core motivations to use a platform. Need a file explorer in your tool? Get it by just reusing it! So I would not mix "extensibility and adaptability" (section below) into this section.
Co-authored-by: Vincent Fugnitto <vincent.fugnitto@ericsson.com>
Co-authored-by: Vincent Fugnitto <vincent.fugnitto@ericsson.com>
Signed-off-by: Jonas Helming <jhelming@eclipsesource.com>
Signed-off-by: Jonas Helming <jhelming@eclipsesource.com>
|
|
||
| ## Use Standards And Don’t Reinvent The Wheel | ||
|
|
||
| Theia uses/reuses industrial standard technologies and practices whenever applicable. This keeps the scope of the project minimal and decreases the maintenance cost. This applies to the use of frameworks and development tools as well as to general concepts such as UX. |
There was a problem hiding this comment.
Could use the debug adapter protocol and LSP as examples here?
|
|
||
| ## VS Code Compatibility | ||
|
|
||
| Theia provides the ability to host VS Code extensions. This allows adopters to benefit from features that are provided as VS Code extensions and make them part of their tool offering. It also allows end users of Theia-based tools to install additional features, if the adopter providing a tool allows users to do so. When applicable, the default Theia UX aligns with the VS Code UI, although adopters can deviate from this. |
|
+1 |
fixed #279
Signed-off-by: Jonas Helming jhelming@eclipsesource.com