Herby Vojčík 7ff4146dce More stringent refresh ban possible. | hace 4 años | |
---|---|---|
resources | hace 5 años | |
src | hace 4 años | |
.gitignore | hace 6 años | |
Gruntfile.js | hace 5 años | |
LICENSE-MIT | hace 6 años | |
README.md | hace 6 años | |
app.js | hace 5 años | |
bootstrap.amd.json | hace 5 años | |
codemirror.amd.json | hace 5 años | |
es6-promise.amd.json | hace 5 años | |
index.html | hace 4 años | |
index.js | hace 6 años | |
jquery-ui-dist.amd.json | hace 5 años | |
jquery.amd.json | hace 5 años | |
local.amd.json | hace 5 años | |
package.json | hace 4 años | |
polyfills.js | hace 5 años | |
require-css.amd.json | hace 5 años | |
requirejs.amd.json | hace 5 años | |
showdown.amd.json | hace 5 años | |
typeahead.js.amd.json | hace 5 años |
Helios IDE for Amber Smalltalk
The following packages need to be installed globally:
node
(NodeJS)npm
(NodeJS package manager)grunt-cli
(build packages on the commandline)@ambers/cli
(for serving and creating Amber applications)There are two ways how to contribute. Both ways require forking this repo first and fetching all required packages via NPM and Bower.
git clone https://lolg.it/amber/helios.git
cd helios
npm run init
If you only want to contribute to Helios itself you can now run Helios as a regular Amber application by executing
amber serve
and visiting http://localhost:4000/
in the browser.
As Helios is still coupled with Amber, you need occasionally make change to Amber itself,
not just to Helios code.
The recommended way is to fork and clone Amber repository itself for development
(see https://github.com/amber-smalltalk/amber/blob/master/CONTRIBUTING.md,
"Setup your Amber clone" part and use your own fork in the "clone Helios" step).
This allows you to develop Amber itself, @ambers/cli
and Helios simultaneously.