Introduction to Atom

Atom is an open-source text editor (mostly used by developers){:rel=”nofollow”} which is multi-platform and developed by GitHub company. It is based on Electron, the Github-developed framework, which allows developers to build native desktop applications for any operating systems by writing Javascript code.

The main interesting feature of Atom is that it also has a great package management tool and packages are also written in Javascript so it’s quite easy for anyone to create one. This article aims to talk about it. Finally, its community is also active as it already has a lot of available packages: 5 285 at this time. You can browse all packages by going to the following address: https://atom.io/packages.

However, if you cannot find a package that fits your needs you can start creating your own and we will see how simple it is.

Generate your first package

In order to create your own package, don’t worry, you will not start from scratch. Indeed, we will use the Package Generator command which is brought to us by Atom core. To do that, you will just have to navigate into Packages -> Package Generator -> Generate Atom Package .

In order to generate your package, you can choose the language between Javascript and Coffeescript . This article will use Javascript.

When the command is executed, Atom will open a new window into your package project, by default named my-package .

Package structure

We will now see in details what’s inside our package project directory:

├── CHANGELOG.md ├── LICENSE.md ├── README.md ├── keymaps │ └── my-package.json <- Key shortcuts registered by your package ├── lib │ ├── my-package-view.js │ └── my-package.js <- Entry point of your package ├── menus │ └── my-package.json <- Menus declaration of your package into Atom application ├── package.json <- Description and library dependencies of your package ├── spec <- Tests directory (Jasmine) of your package │ ├── my-package-spec.js │ └── my-package-view-spec.js └── styles <- Stylesheets used by your package └── my-package.less

The first element to add to your package is the package.json file which has to contain all information of your package such as its name, version, license type, keywords that will enable you to find your package into Atom registry and also your package dependancies.

Please also note that there is a section called activationCommands which allows to define the executed command when your package is loaded.

Next, we have the keymaps/my-package.json file which allows you to define shortcuts into your package very easily. Here is the default example:

{ "atom-workspace" : { "ctrl-alt-p" : "my-package:toggle" } }

Next, we will go into your package entry point. It is located into lib/my-package.js file. This file exports a default object which contains a subscriptions property and also activate() and deactivate() methods.

During package activation (inside activate() method), we will register a CompositeDisposable type object inside our subscriptions property and that will allow us to add and maybe later remove some commands offered by our package:

activate ( state ) { this . subscriptions = new CompositeDisposable (); this . subscriptions . add ( atom . commands . add ( ' atom-workspace ' , { ' my-package:toggle ' : () => this . toggle () })); }

Now that our command is registered, we can test it by simply typing the following words, into the Atom command palette: My Package: Toggle . This command will execute the code contained in the toggle() method of the class and will display a little modal at the top of the window. You can add as many commands as you want and I really encourage you to decouple your code.

Add settings for your package

The Config component allows your package to have some settings.

To add a new setting, you just have to define a config property into your package’s class which is an object containing each settings definition, as follows:

config: { "gitlabUrl" : { "description" : "If you rely on a private Gitlab server, please type your base URI here (default: https://gitlab.com)." , "type" : "string" , "default" : "https://gitlab.com" } }

Atom settings allow multiple setting types ( boolean , color , integer , string , …) so it can fit your needs on setting values by your users.

Once it is added, if you reload your package, you will see your package settings appearing into Atom settings:

In order to retrieve the value (or default value) defined by a user for a given setting in your code, you just have to use the following line:

let gitlabUrl = atom . config . get ( ' gitlabUrl ' );

Components overview

So you are now ready to develop your package. We will have a quick overview of some interesting components that Atom brings to you and allows you to use in your package.

TextEditor: Interact with the text editor

With the TextEditor component, you will be able to insert some text into user’s text editor, to save the current file, to go back and forth the history, to move the cursor into editor, to copy/paste into clipboard, to play with line indentation, to scroll, and to do so much more…

Here are some examples to insert text in a specific position and to save the file automatically:

editor . setCursorBufferPosition ([ row , column ]); editor . insertText ( ' foo ' ); editor . save ();

ViewRegistry & View: Create and display your own window

These components allow you to create views (modals / windows) inside Atom and display them.

You have an example of a modal View into the default package:

export default class MyPackageView { constructor ( serializedState ) { // Create root element this . element = document . createElement ( ' div ' ); this . element . classList . add ( ' my-package ' ); // Create message element const message = document . createElement ( ' div ' ); message . textContent = ' The MyPackage package is Alive! It \' s ALIVE! ' ; message . classList . add ( ' message ' ); this . element . appendChild ( message ); } // ... } let myPackageView = new MyPackageView ( state . myPackageViewState ); let modalPanel = atom . workspace . addModalPanel ({ item : myPackageView . getElement (), visible : false ; }); modalPanel . show ();

NotificationManager & Notification: Alert your users with notifications

Your package can also display a variety of notifications from “success” to “fatal error”:

atom . notifications . addSuccess ( ' My success notification ' ); atom . notifications . addInfo ( ' My info notification ' ); atom . notifications . addWarning ( ' My warning notification ' ); atom . notifications . addError ( ' My error notification ' ); atom . notifications . addFatalError ( ' My fatal error notification ' );

GitRepository

This one is also really interesting: indeed, you can access all the git properties of the current git repository that is used. This way, you will be able to access the current branch name, the repository remote URL and also see if a file is considered as a new or modified file. Let’s see it in action:

let repository = atom . project . getRepositoryForDirectory ( ' /path/to/project ' ); console . log ( repository . getOriginURL ()); // -> git@github.com:eko/atom-pull-request.git console . log ( repository . getShortHead ()); // -> master console . log ( repository . isStatusNew ( ' /path/to/file ' )); // -> true

And more things to discover…

We just made a review of the components that I played with but I invite you to read more on the following link if you want to go further: https://atom.io/docs/api/latest/AtomEnvironment.

Test your package with specs

Our package is now developed but we don’t have to forget about the tests. To do that, Atom uses Jasmine.

Your default package already has a prepared test file:

import MyPackageView from ' ../lib/my-package-view ' ; describe ( ' MyPackageView ' , () => { it ( ' has one valid test ' , () => { expect ( ' life ' ). toBe ( ' easy ' ); }); });

Jasmine specs tests are written in the following way:

describe() : A Jasmine test suite starts with a “describe” function which takes a name as the first argument and a function as the second,

: A Jasmine test suite starts with a “describe” function which takes a name as the first argument and a function as the second, it() : A specification is added by using this function, “it” has to be contained into a specification,

: A specification is added by using this function, “it” has to be contained into a specification, expect() : This one is an assertion, when we expect something to happen.

This is now your turn to play with Jasmine and test your package logic. In order to run the specs tests, you just have to navigate into the following menu: View -> Packages -> Run Package Specs .

Publish your package

Our package is now ready to be deployed! Let’s send it.

To do that, we will use the apm CLI tool which comes with Atom when installing it.

After pushing your code into a Github repository, simply go into your package directory and type the following command:

$ apm publish --tag v0.0.1 minor Preparing and tagging a new version ✓ Pushing v0.0.1 tag ✓ ...

This command will be in charge of creating the new version tag into repository and publish this version into the Atom registry. Congratulations, your package is now published and available on the following URL: https://atom.io/packages/<your-package> !

Continuous Integration

The final step is to ensure that your package will continue to work in the future when you or your contributors will add new features but also when Atom releases a new beta version. To do that, you can use Travis-CI on your repository with the following configuration:

language : objective-c notifications : email : on_success : never on_failure : change script : ' curl -s https://raw.githubusercontent.com/nikhilkalige/docblockr/develop/spec/atom-build-package.sh | sh' env : global : - APM_TEST_PACKAGES="" matrix : - ATOM_CHANNEL=stable - ATOM_CHANNEL=beta

Conclusion

I personally think that this is a little revolution to allow developers to make their own editor and bring the features they want.

Moreover, the Atom API is already very rich and very simple to use and this is certainly the main reason why the community offers a large number of packages. To conclude, as for all libraries, it is not useful to reinvent the wheel by creating already existing packages. The idea is to add features if they don’t already exists, in order to enrich your user experience.