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

[WIP] Improve Che IDE extensibility model #6642

Closed
4 tasks
vparfonov opened this issue Oct 9, 2017 · 3 comments
Closed
4 tasks

[WIP] Improve Che IDE extensibility model #6642

vparfonov opened this issue Oct 9, 2017 · 3 comments
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.

Comments

@vparfonov
Copy link
Contributor

vparfonov commented Oct 9, 2017

Problem

The current Eclipse Che architecture for the client side IDE is using GWT and Guice/Gin for the dependency injection. Eclipse Che IDE is composed of API Core functions and plugins. With GWT, all plugins are statically linked at compile time, it means that adding a plugin to the assembly requires to build each time this build take long time

Goals

  1. Need to allow developer develop only own plugin and include it to the compiled Che IDE without rebuild all app
  2. Make possible develop client-side plugin on pure JavaScript
  3. Consider Che plugin as single artifact which contains:
  • server side code;
  • client side code;
  • some meta information;

Tasks

@vparfonov vparfonov added kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. team/ide labels Oct 9, 2017
@vparfonov vparfonov changed the title Improve Che IDE extensibility model [WIP] Improve Che IDE extensibility model Oct 9, 2017
@benoitf
Copy link
Contributor

benoitf commented Oct 10, 2017

About #2, I would like to see what it will be before trying to do a direct 1-1 mapping.

I'm interested in the simplicity of the API and if it will match the full the loading/unloading sequence of a plugin

For reference, here are two documents I've provided
https://docs.google.com/document/d/1OcC8cnmPzwQybSi58OSQKTngXEqV46oFEyGn6phpB6U/edit
https://docs.google.com/document/d/1t7bOjC6MkgJdv14KSwcYqh2xBrWQWaYCgkatRUmZzfc/edit

@bmicklea
Copy link

@vparfonov can you please add and link the tasks in the Tasks section?

@slemeur
Copy link
Contributor

slemeur commented Jan 31, 2018

Will be addressed by #8266

@slemeur slemeur closed this as completed Jan 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.
Projects
None yet
Development

No branches or pull requests

4 participants