Switch branches/tags
Nothing to show
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


WebWorks Extension Example (Memory Extension)

This document describes how to generate a WebWorks Extension for retrieving the free memory.

This example follows an older format. It is recommended that you use the new template for your extension starting point

The implementation is split into two parts: Native and JavaScript

This project implements an example extension that retrieves the current amount of free memory on the device.

The resources here include:

  • sample_application/ - Resources for a WebWorks application that uses the Memory Extension to get the amount of free memory on the device.
  • ext/ - The JavaScript source files and the compiled native portions that make up the complete example Memory Extension.
  • NDK_project/ - The native source files for the Memory Extension, which can be imported to Momentics.

The Memory Extension implementation should be used in conjunction with this read me file to understand how to create a WebWorks extension.

The sample code for this application is Open Source under the Apache 2.0 License.

How to add an WebWorks Extension to your WebWorks Installation

  1. Navigate to the Framework/ext folder of your WebWorks Installation and create a folder for your extension.
  2. Copy you JavaScript files to the root folder of your extension folder.
  3. Create a device and a simulator folder in the root of your extension folder.
  4. Build the native portion of your native extension. One shared library for the device and another for the simulator.
  5. Copy the shared library for the device into the device folder.
  6. Copy the shared library for the simulator into the simulator folder.

After completing the above steps you should be able to build WebWorks applications that can use your memory extension. If done correctly, the file structure of your extension should match the file structure of the output folder in the ext folder.

IMPORTANT: Make sure that your WebWorks applications whitelist the extension otherwise the application will not be able to use the extension.

Native Part - Overview

This part of the document will describe:

  1. How to setup a native extension project in eclipse.
  2. The steps needed to implement a JNEXT extension on the native side.
  3. How to build your native extension project.

How to create an Extension Project with the Native SDK

  1. Open the Momentics IDE. Navigate to the workbench and from the program menu select File -> New -> BlackBerry C/C++ Project.
  2. Enter a name for your project in the window that appears and click next.
  3. In the following window, choose C++ for the language, Managed Build for the Build Style and an empty shared library project for the project type. When you're done click next.
  4. Select the active configuration you want to use for this project then click next.
  5. If you wish to use a Native SDK that is different from the workspace SDK then uncheck the option to use the workspace SDK selection and select a different SDK. When you are done, click Finish. You should see your new project appear in the Project Explorer window.
  6. In order to build an extension you'll need to import extension resources into your new project.

How to import extension resources

  1. Right click on your project and select the import menu item. In the window that appears select the file system as an import source and click next.
  2. The next window will prompt you to provide a path to a folder. Select the public and src folders located in the native_src folder of the extension template folder. Import both of the folders and their contents. Then click finish. Your project should now have a public folder and a source folder which contains source and header files. If done correctly, the file structure of your project should match the file structure of the project folder in the extension template folder.

After following the instructions below to implement an extension you should build your extension for both the device and the simulator.

How to implement a JNEXT extension on the native side

The native and JavaScript portion of a WebWorks extension communicate with each other through the use of an extension framework provided by JNEXT. The native interface for the JNEXT extension can be viewed in the plugin header file located in the public folder of your project. It also contains constants and utility functions that can be used in your native code. Your native extension must be derived from JSExt which is defined in plugin.h. Therefore your extension should include this header file.

The MemoryExtension sample code included in the ext folder implements the native extension interface to JNEXT.

Each native extension must implement the following callback functions:

extern char* onGetObjList( void );
extern JSExt* onCreateObject( const string& strClassName, const string& strObjId );

The onGetObjList function returns a comma separated list of classes supported by this JNEXT extension. It is used by JNEXT to determine the set of classes that can be instantiated by this JNEXT extension.

The onCreateObject function is the other callback that must be implemented by the native JNEXT extension. It takes two parameters. The first parameter is the name of the class requested to be created from the JavaScript side. Valid names are those that are returned in onGetObjList. The second parameter is the unique object id for the class. This method returns a pointer to the created extension object.

The native extension must also implement the following class:

class JSExt
    virtual ~JSExt() {};
    virtual string InvokeMethod( const string& strCommand ) = 0;
    virtual bool CanDelete( void ) = 0;
    std::string m_id;

The m_id is an attribute that contains the JNEXT id for this object. The id is passed to the class as an argument to the constructor. It is needed to trigger events on the JavaScript side from native.

The CanDelete method is used by JNEXT to determine whether your native object can be deleted.

The InvokeMethod function is called as a result from a request from JavaScript to invoke a method of this particular object. The only argument to this function is a string passed from JavaScript that this method should parse in order to determine which method of the native object should be executed.

If you want the native code to be able to trigger an event on the JavaScript side then you'll need to call the SendPluginEvent function which has the following signature:

void SendPluginEvent( const char* szEvent, void* pContext );

The first parameter is a space delimited string consisting of the m_id (inherited attribute from JSExt) followed by the arguments you wish to pass to the JavaScript on event function. The second parameter is the m_pContext (inherited attribute from JSExt).

How to build your native Extension

  1. Right click your project and select the Clean Project option.
  2. Right click your project again and select Build Configurations -> Build Selected... .
  3. A window will appear that shows all the available build configurations for the project. Depending on the profile you wish to use select the Device and corresponding Simulator build profiles and click ok.
  4. You should see the shared libraries generated in the folders for each Build Configuration that you selected.

How to change the name of the build artifact.

  1. Right click on your project and selecting properties.
  2. Expand the C/C++ Build option and select the Settings option.
  3. In the main window select the build configuration you wish to configure and select the build artifact tab.
  4. You should see fields for the type, name, extension and prefix of the artifact tab which you can modify to change the build artifact that is generated. When you have completed your changes then select ok.

Please note that each modification of the build artifact corresponds to a single configuration. If you wish to modify the build artifacts of all the build configurations you will need to modify each build configuration.

JavaScript Part - Overview

Under the javascript_src folder there are following JavaScript files:

  • client.js - Considered to be a client side, exports APIs that are accessible from the client's application. client.js file name is mandatory.
  • index.js - Considered to be a server side, exports APIs that are accessible from the client.js and able to communicate with native side. index.js file name is mandatory.
  • manifest.json - Descriptor defines Whitelisting flag, ID and Dependencies for the extension.

example.memory is the extension ID as it defined in manifest.js and serves as a prefix to all methods and fields defined in the client.js

example.memory.getMemory - Call this method to get free memory bytes example.memory.monitorMemory - Call this method to register and be notified of memory events.

####See sample code below:

    function memoryUsageCallback(memoryInByte) {
        alert("Event Callback. Free memory: " + memoryInByte);

    var freeMemory = example.memory.getMemory();
    alert("Free memory: " + freeMemory);


JavaScript Part - In Depth

The interaction between client.js and index.js is made by using APIs of webworks object.

The client side can make synchronous or asynchronous calls to the server side. When making a call to server side, each method in client.js should provide the ID, method name and arguments to execSync to get a synchronized call or to execAsync when the request is asynchronous. This will result in the invocation of a corresponding method name in index.js.

The webworks object has an event API that can be used to communicate between the client and server side. The client registers a callback against the event API which the server side can trigger. An example of this functionality is the monitor memory function which registers a callback on the client side:

    window.webworks.event.add(_ID, "example.memory.memoryEvent", cb);

Where the arguments to the function are the feature id, event id and the callback. Once the event is registered on the client side it can be triggered by the server side whenever the memory usage changes:

    _event.trigger("example.memory.memoryEvent", arg);

The server side uses the event id to trigger the client side callback and passes the new memory usage as an argument for the callback.

JNEXT Interface

The interaction between index.js and the native side is made by using APIs of JNEXT interface. To accomplish this a constructor function MemoryJNext is attached to JNEXT. The object is expected to have a following structure:

  • onEvent - Events from the native side are passed as a String to this method. onEvent is a mandatory name.
  • init - It performs several key operations:
    1. Requires the module exported by native side - JNEXT.require("memoryJnext"). The name of required module memoryJnext should match the name of a shared library .so file.
    2. Creates an object using acquired module and saves the id returned by the call - self._id = JNEXT.createObject("memoryJnext.Memory").
    3. Registers itself to be notified on events so onEvent will be called - JNEXT.registerEvents(_self).
  • getId - Returns the id previously saved - return self._id.
  • Methods and fields used by index.js to redirect, when required, calls that initially came from client.js to the native side. This example has two: getMemoryJNext and monitorMemoryJNext

index.js creates a MemoryJNext object and save its instance in variable, then redirects calls to methods in index.js to the corresponding MemoryJNext method.

    //Code in user's app.
    var freeMemory = example.memory.getMemory();

    //Code in user app trigger this code in client.js
    return window.webworks.execSync(_ID, "getMemoryServer", null);

    //Code in client.js trigger this code in index.js
    getMemoryServer: function (success, fail, args, env) {

    //Finally in index.js code that belongs to MemoryJNext object is triggered where
    //call to native side takes place and returned value is passed back to the user.
    _self.getMemoryJNext = function () {
        return JNEXT.invoke(_self._id, "getMemoryNative");