Welcome to Scripted
What is Scripted?
What are the key features?
- Fast startup, lightweight.
- Errors and warnings:
- 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
- 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
- Formatting: JSbeautify is integrated
- Sidepanel: alongside the main editor a sidepanel can be opened - currently this can be used to host a second editor.
- Key binding to external command: Key bindings in the editor can invoke external commands (less, mvn, etc)
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.
How do I try it out?
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 recent versions from 0.6 to 0.8.
Then you can grab the most recent packaged release from here:
OR you can live on the bleeding edge by either cloning the repository:
git clone https://github.com/SpringSource/scripted
or grabbing the latest repo contents as a zip:
Unpack whatever you have and then make sure the files in the bin folder are executable on mac/linux:
chmod 755 bin/*
Then add the bin folder to your path:
then launch it:
(you can use
scripted to launch it if you'd prefer to type more characters...)
When working with Scripted, think about it like using
emacs. From wherever you are in your terminal window you
can launch Scripted and start editing a file.
Launching scripted will cause the Node.js server to start in the background.
Here are some of the more vital key bindings to use once the editor is open:
Cmd/Ctrl+h- open help to show all key bindings (or press '?' in the top right)
Cmd/Ctrl+Shift+E- open/close subeditor
Cmd/Ctrl+Shift+F- open Find File dialog. Inside the dialog, you can search for files in the project by regular expression and:
Clicka result to open it in main editor
Shift+Clicka result to open it in sub-editor
Cmd/Ctrl+Clicka result to open it in a new tab
Cmd/Ctrl+Shift+o- open outline view. A dialog will present the functions and you can quickly navigate to them
Cmd/Ctrl+F- in-file search
Ctrl+Space- content assist
F8- navigate to declaration
Shift+F8- open declaration in subeditor
Cmd/Ctrl+F8- navigate to declaration in new tab
On the left hand side is a traditional navigator for opening different files. Above the editor is a breadcrumb, hover over a component to see other files in that directory.
The editor does support a degree of customization, see the section on the Features page.
Scripted receives most testing in Chrome and Firefox, you may need one of those browsers in order to get the most out of it.
Anything else I need to know before using it?
When you open Scripted on a file, it will attempt to infer the root of your project by locating the nearest
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.
As of Oct 2012 the project is at version 0.2. There is a long way to go but the team have been using Scripted to develop Scripted for a while now.
Where can I ask questions, provide feedback or raise issues?
- The scripted-dev google group is open for questions and discussion
- The issuetracker to raise issues or take a look and vote on existing issues.
What's next for Scripted?
- 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.
- Simple plugin system.
- Debugging. Exploring integration with tools like Chrome Dev Tools and node inspector.
Can I contribute?
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 (similar to other SpringSource projects) - 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.
If you are keen to contribute but aren't sure what to work on, take a look at the public issuetracker for inspiration. The codebase is very new in places and isn't that tricky to get to grips with. Some of the simpler issues that might provide an easy way to get started with the codebase are tagged with the label help-wanted, see here.
If you don't feel like coding but still want to contribute, please join the discussion on the issuetracker and scripted-dev group.