Your first plugin deprecated

Hello and welcome to the world of OX App Suite development. This document is designed to get you started with developing your first plugin for OX App Suite as quickly and simply as possible. However, along the way we will also tempt you to learn more by linking to some more in-depth documentation about the various topics we cover.

General development workflow

Installing the Development Tools

First, you need to install some tools which are necessary for UI development.

TL;DR version:

npm install -g grunt-cli yo generator-ox-ui-module

Or if needed, there is a complete article about setting up an environment for grunt.

Create a Workspace

All your app development can take place inside one working directory. The examples will assume you have created a directory named myplugin inside your home directory:

mkdir ~/myplugin
cd ~/myplugin

It doesn't need to be in your home directory, and the actual name should reflect the name of your plugin. The main point is that all commands will be executed in this directory and all paths will be relative to this directory from now on.

Now, you can generate a grunt configuration using:

yo ox-ui-module

The source code of your plugin will reside in the subfolder named apps. To avoid name collisions please pick a unique subfolder inside that. The easiest and recommended way is to use a domain name that you own. Typically, the domain elements are reversed, like in Java. example.com becomes com.example:

mkdir -p apps/com.example

Writing a Plugin

As an example, let's create the smallest possible plugin and test it. It requires only two files: apps/com.example/register.js for the source code of the plugin:

define('com.example/register', function () {
    'use strict';
    alert('Hello, World!');
});

and apps/com.example/manifest.json for the manifest which tells the UI that your plugin exists and what to do with it:

{ "namespace": "core" }

Building a Plugin

The source code of your plugin can't be used by OX App Suite as it. It first has to be processed by the build system. This step will check the source code for syntax errors, compress it, and depending on the structure of your code, many other things. The processed code is then written to a directory named build by default. Start the build with this command:

grunt

If your editor supports it, you can configure it to call the build system after every file save. Take care to call it from the top directory of your app's workspace, not from the directory of the saved file.

Testing a Plugin

The freshly built code can now be tested. Instead of uploading your code to an OX App Suite server, you can use the appserver proxy to inject your code into the UI code of any existing OX App Suite installation. For example, to start appserver using www.ox.io as the server, you will need a local configuration pointing to that server. You can register for a free user account on www.ox.io.

You can generate it with this command:

grunt show-config:local --output=grunt/local.conf.json

To use the remote www.ox.io OX App Suite server, open up the file grunt/local.conf.json in your editor and add https://www.ox.io/appsuite/ to the server setting of the appserver section. Also make sure that the protocol setting is set to https. Else you will get https redirect errors in your browser.

INFO: If you are using a locally installed OX App Suite server (in a VM or similar in your local network), just modify the server + protocol accordingly.

Then start the development server:

grunt dev

This command will serve your plugin from the local directory build, and get everything else from the URL specified in the server setting.

Once appserver is running, you can access OX App Suite by opening your browser using this address:

https://localhost:8337/appsuite

After logging in, the plugin should be loaded and display the alert message.

Development cycle

Once you are sure that your setup works, you can extend the example and write the actual code for your plugin. The dev task will detect any changes and rebuild your plugin and even reload all browsers connected to https://localhost:8337/appsuite.

While developing always keep in mind, that there is an article about debugging the user interface which helps you avoid and fix typical errors.

Packaging

Together with our ox-ui-module generator (from version 0.8.0), we provide you with generators for packaging information.

To enable some grunt tasks to help you, you can optionally install (with npm install) grunt-contrib-compress and grunt-exec. You will need those to run the grunt tasks described below.

Generating a source tarball

There is a grunt tasks to create source packages. You can use it to create a tar.gz file containing all sources needed to build the project. This source package should contain all dependencies that are installed during npm install (basically containing your node_modules directories). To generate this file, run:

grunt dist:source --include-dependencies

This file (can be found in the dist/ directory) together with the distribution specific packaging information will be needed to build the package.

RPM packages

In order to generate a spec file for your project, run:

yo ox-ui-module:rpm-pkg

Will generate a spec file, with some default values read from your package.json file. So you might want to make this file as complete as possible. However, yeoman will ask you about the information missing.

Please remember, that the generated spec file is only a scaffold for a real one. It will work for very simple cases, but as soon as your package gets more complicated, you will have to adjust it to your needs.

Once you have the spec file in your project, you can use

grunt rpm-build --include-dependencies
# or rpm-build if you are on shared-grunt-config-0.6.0

DEB packages

Creating packages for the Debian distribution works similar to rpm packages. Just run:

yo ox-ui-module:deb-pkg

This will generate a debian directory containing all needed files. Some default values will be read from your package.json file. So you might want to make this file as complete as possible. However, yeoman will ask you about the information missing.

Please remember, that the generated spec file is only a scaffold for a real one. It will work for very simple cases, but as soon as your package gets more complicated, you will have to adjust it to your needs.

Once you have a debian/ directory for your project, you can go on. Now you can run:

grunt dpkg-buildpackage --include-dependencies

i18n

To use the proven way to translate your OX App Suite plugin, you should now check out the documentation about all i18n tasks.

Getting the code

A repository showing the latest version of this example can be found in this project.