Re: [che-dev] Plugins API

[Gennady Azarenkov <gazarenkov@xxxxxxxxxxx>]

Hi Vlad,

Interesting context and good questions.

That's what we do for projects management.

During construction of container responsible for managing source code (we call this side workspace-agent) we deploy there all the services necessary for:

- managing project metainformation and remote file system: that is what we call Che Project API

- APIs for project type specific calls, provided by specific extensions, such as in case of java: JDT based codeassistant, autocompletion and other intellisense/editor related calls (so far we do not have generic abstractions for it so really java specific things).

So before we go to more specifics, let me ask you if you goal is rather:

1/ to reuse some of yours existed Eclipse plugin Java code to make it accessible remotely

2/ same as #1 but not necessary Eclipse code dependent (to make extension using Java from scratch)

3/ same as #2 but using Erlang, not Java  services (Erlang based REST API for "smart editor")   

Thanks

Gennady

Gennady Azarenkov - CTO @ codenvy.com

On Tue, Feb 2, 2016 at 11:40 AM, Vlad Dumitrescu <vladdu55@xxxxxxxxx> wrote:

From: Tyler Jewell <tyler@xxxxxxxxxxx>

For your points:
1. I have cc'd the engineers that have spent the most time either
architecting the plug-in framework, and / or using it to build our plug-ins
especially the Java / Maven ones.
2. As a general rule, the objective is to be able to plug existing
libraries for various languages to run natively within the workspace, and
then to create Che plug-in wrappers around those libraries, turning them
into RESTful services. This is what was done for Java, and some _javascript_.
I believe that our abstractions are clean here, but I imagine that the
cleanliness of the abstractions themselves get stronger as more languages
are added in.  I am just the project lead, not the architect - so those
CC'd can provide better descriptions.

Could you share a little about which languages you'd like to add support
for?

Tyler Jewell

Hi Tyler,

Thanks for your answers.

I am currently the developer for erlide, the Eclipse support for Erlang. The evolution of the architecture has been from a fully Java implementation towards using an Erlang runtime as a backend for the IDE services. My biggest architectural problem has been coming up with a remote API, hopefully a generic one. I still don't have a good one and when I read about Che, I realized that its APIs might be just what I needed. 

Also, many Erlang users are using it for developing web applications and they would benefit from being able to use Che instead of the regular Eclipse, as it's better suited for web development, so I am also looking at providing Erlang support for Che.

best regards,

Vlad

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev