gorkem

schemaVersion: 2.0.0
components:
  - name: gatsby
    container:
      image: quay.io/eclipse/che-nodejs10-ubi:nightly
      mountSources: true
      memoryLimit: 700Mi
      endpoints:
        - name: web
          targetPort: 8000

gorkem

---
specVersion: 0.0.1
name: nodejs-rest-http
projects:
  - name: node-rest
    source:
      type: git
      location: "https://github.com/nodeshift-starters/nodejs-rest-http.git"
tools:
  - name: theia-editor

gorkem

Developing Che IDE plugins using JavaScript

Since version 6.XXX it is possible to develop plugins to Che IDE using JavaScript. This tutorial covers getting started topics for developing JavaScript based Che IDE plugins, refer to API documentation for API specific information.

Your plugin's life-cycle

Each Che JS plugin is independent WebPack AMD library. We considered to not add ability to share JS libraries across plugins. IDE will pick up the plugin description files, add all static information(contributions) and load plugin script file and calls activate function.

Plugin Description

gorkem

File Level Operations

A workspace edit represents changes to many resources managed in the workspace. The edit should either provide changes or documentChanges. If the client can handle versioned document edits and if documentChanges are present, the latter are preferred over changes.

A workspace edit can optionally provide resource changes. If present resource changes are applies after the changes/documentChanges has been applied.

interface  WorkspaceEdit{
  TextEdit[] changes 
  TextDocumentEdit[] documentChanges 

gorkem

gorkem

JSDT 2.0 (Bower / npm / JSON editor)

There has been no news for quite a while from the Eclipse JavaScript Development Tools (JSDT). Basically, the project was in a deep support phase for a couple of years. However, the situation has changed dramatically and now we are glad to say that the JSDT project has been officially rebooted. This article, which is dedicated to Bower, npm & JSON editor, is the opening one of the JSDT 2.0 series.

Introduction

Bower and npm are considered to be the most popular JavaScript package managers. Bower focuses on pure front-end, whereas npm mainly deals with Node.js modules. The main advantages of using package managers are:

• Dependencies are defined in a single manifest file: bower.json / package.json

• No need to commit dependencies to version control repository

• Easy to distribute among team members

gorkem

JSDT

• Continue the working on Integration of dependency management tools like node.js/bower/npm into JSDT, thus in order to make it possible for developers to use such tools right from the IDE. A number of CQs is created and approved, due to make it possible to invoke native node.js/bower/npm utilities installed in user environment:

  • https://dev.eclipse.org/ipzilla/show_bug.cgi?id=9479 - Use of node.js installation on user environment Version: v0.12.2 and later
  • https://dev.eclipse.org/ipzilla/show_bug.cgi?id=9487 - Use of npm installation on user environment Version: v2.7.5
  • https://dev.eclipse.org/ipzilla/show_bug.cgi?id=9488 - Use of Bower installation on user environment Version: v1.4.1 and later
  • https://bugs.eclipse.org/bugs/show_bug.cgi?id=459732 - Bower IDE contribution

• An extension point for configuring and invoking node.js and npm. The default implementation should allow users to select their node/npm installation as preference but tools like JBT should be able to extend and prov

gorkem

var wpi = require('wiring-pi');
wpi.setup();
var pin = 1; //Change pin number according to your wiring
wpi.pinMode(pin, wpi.OUTPUT);
var value = 1;
setInterval(function() {
  wpi.digitalWrite(pin, value);
  value = +!value;
}, 500);