Scripted is a fast and lightweight code editor with an initial focus on JavaScript editing.
Scripted is a browser based editor and the editor itself is served from a locally running Node.js
server instance.

What are the key features?

Fast startup, lightweight.

Syntax highlighting for JavaScript, HTML and CSS.

Errors and warnings:

JSHint is integrated to provide error/warning markers on JavaScript code.

AMD and CommonJS module resolution: there is basic resolution where unresolved references will be marked as errors.

Content assist:

Basic content assist for HTML, CSS

For JavaScript, content assist is driven by a type inferencing engine which is aware of AMD/CommonJS module
dependencies and also uses JSDoc comments to help it understand the code.

Hovers: hovering over a JavaScript identifier will bring up the inferred type signature.

Navigation:

press F8 on an identifier (that the inferencer has recognized) and the editor will navigate to the declaration.

this also works on module identifiers (e.g. in define() clauses)

Formatting: JSbeautify is integrated

Sidepanel: alongside the main editor a sidepanel can be opened - currently this can be used to host a second editor.

The editor is actually the Eclipse Orion editor with a few additional bells and whistles.
Anyone familiar with editing in Eclipse will immediately know many of the key bindings
the Scripted editor supports.

The only pre-req for trying it out is that you have Node.js installed. Grab it from here: http://nodejs.org/.
The team has been testing with a range of versions from 0.6 to 0.8 but haven't tested all of them exhaustively. It is recommended
that you try to use the latest (0.8.16 at time of writing).

(possibly with a sudo prefix on linux/mac). This will install the most recently published release. There are no further steps if installing via this route and scr command will immediately be available to launch Scripted.

If you already have a clone of the scripted repo and want to update to the latest master, don't
forget that you also need to update external dependencies that may have changed. Run the following
commands from the root of your clone.

When you open Scripted on a file, it will attempt to infer the root of your project by locating the nearest .git/.project file
in the hierarchy. Knowing the root is important because that is the scope in which searching and dependency analysis is done. If
you don't have one of these markers for the root, you can create an empty .scripted file to indicate the root.

Even smarter inferencing, leading to better content assist and easier navigation.

More panes for the side panel. Currently there is just an editor pane but we intend to include search results panes,
documentation, git information panes, perhaps code preview and simulated code execution panes. The intention will be
for Scripted to try and automatically manage these where possible, so all the content on screen is kept relevant
to the task at hand.

Sure! Just press Fork at the top of this github page and get coding. Before we accept pull requests we just need you to sign a simple contributor's
agreement - which you can find here. Signing the contributor's agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests.
Pull requests should ideally reference a JIRA ticket in the issuetracker that details what the request is addressing.

The codebase is entirely JavaScript/HTML/CSS.

If you are keen to contribute but aren't sure what to work on, take a look at
the github issues for inspiration.
The codebase is very new in places and isn't that tricky to get to grips with.

If you don't feel like coding but still want to contribute, please join the discussion on the issues and scripted-dev group.