This directive allows you to add ACE editor elements.
npm install angular-ui-aceThis directive allows you to add ACE editor elements.
- AngularJS
- Ace 1.x
You can get it from Bower
``sh`
bower install angular-ui-ace#bower
This will copy the UI.Ace files into a bower_components folder, along with its dependencies. Load the script files in your application:
`html`
Add the UI.Ace module as a dependency to your application module:
`javascript`
var myAppModule = angular.module('MyApp', ['ui.ace']);
Finally, add the directive to your html:
`html`
To see something it's better to add some CSS, like
`css`
.ace_editor { height: 200px; }
Ace doesn't provide a one gate access to all the options the jquery way.
Each option is configured with the function of a specific instance.
See the api doc for more.
Although, _ui-ace_ automatically handles some handy options :
+ _showGutter_ : to show the gutter or not.
+ _useWrapMode_ : to set whether or not line wrapping is enabled.
+ _theme_ : to set the theme to use.
+ _mode_ : to set the mode to use.
+ _onLoad_ : callback when the editor has finished loading (see below).
+ _onChange_ : callback when the editor content is changed ().
+ _onBlur_ : callback when the editor is blurred ().
+ _firstLineNumber_ : to set the firstLineNumber (default: 1)
`html`
You'll want to define the onLoad and the onChange callback on your scope:
`javascript
myAppModule.controller('MyController', [ '$scope', function($scope) {
$scope.aceLoaded = function(_editor) {
// Options
_editor.setReadOnly(true);
};
$scope.aceChanged = function(e) {
//
};
}]);
`
To handle other options you'll have to use a direct access to the Ace created instance (see below).
You can specify advanced options and even require options in the directive, as well. For this example, youext-language_tools.js
will have to include the file from the ace source code.
This will copy the UI.Ace files into a bower_components folder, along with its dependencies. Load the script files in your application:
`html`
`html`
To include options applicable to the ACE renderer, you can use the rendererOptions key:
`html`
Trying to use ace with concatenated javascript files usually fails because it changes the physical location of the workerPath. If youworkerPath
need to work with bundled or minified versions of ace, you can specify the original location of the on disk (_not the bundled file_).
This should be the folder on disk where ace.js resides.
`html`
The ui-ace directive plays nicely with ng-model.
The ng-model will be watched for to set the Ace EditSession value (by setValue).
_The ui-ace directive stores and expects the model value to be a standard javascript String._
Simple demo
`html`
or
Check me to make Ace readonly:
For more interaction with the Ace instance in the directive, we provide a direct access to it.
Using
`html`
the $scope.aceLoaded function will be called with the Ace Editor instance as first argument
`javascript
myAppModule.controller('MyController', [ '$scope', function($scope) {
$scope.aceLoaded = function(_editor){
// Editor part
var _session = _editor.getSession();
var _renderer = _editor.renderer;
// Options
_editor.setReadOnly(true);
_session.setUndoManager(new ace.UndoManager());
_renderer.setShowGutter(false);
// Events
_editor.on("changeSession", function(){ ... });
_session.on("change", function(){ ... });
};
}]);
`
We use Karma and jshint to ensure the quality of the code. The easiest way to run these checks is to use grunt:
`sh`
npm install -g grunt-cli
npm install && bower install
grunt
The karma task will try to open Firefox and Chrome as browser in which to run the tests. Make sure this is available or change the configuration in test\karma.conf.js
We have one task to serve them all !
`sh`
grunt serve
It's equal to run separately:
* grunt connect:server : giving you a development server at http://127.0.0.1:8000/.
* grunt karma:server : giving you a Karma server to run tests (at http://localhost:9876/ by default). You can force a test on this server with grunt karma:unit:run.
* grunt watch : will automatically test your code and build your demo. You can demo generation with grunt build:gh-pages.
This repo is using the angular-ui/angular-ui-publisher.
New tags will automatically trigger a new publication.
To test is locally you can trigger a :
`sh``
grunt dist build:bower
it will put the final files in the _'dist'_ folder and a sample of the bower tag output in the _'out/built/bower'_ folder.