The examples in this section all use the importLib command to import pluggable views or pluggable libraries. They use individual property files to set import configuration properties.

The configuration properties you use in an Ant build file and the effects of importing these libraries are identical.

This example in a Windows environment imports a pluggable library with the local library resources shown below. No configuration properties are set. The library is registered with the MashZone NextGen Server at the default URl (http://localhost:8080/mashzone/edge/api) using the default MashZone NextGen admininstrator account.

This example is identical to the library in Example: Default Library Import with No Properties but adds to control how the import process runs.

This example sets basic properties for a pluggable library, including an ID, a title, a description and a loadConfirmation property.

The id property is required and its value must match the name of the root library folder. The name and description properties provide general information about the library for MashZone NextGen administrators who manage pluggable libraries or developers who may see this in the App Editor.

MashZone NextGen uses the loadConfirmation property to confirm when this library is completely loaded when it is used in pluggable views or custom apps. It is not required, but it is highly recommended. In this example, the value of loadConfirmation is simply the class name for this library. The value generally needs to be a boolean expression of the classes or objects that must be present before the library can be used successfully.

To register a pluggable view, you must include the type property with a value of view.

This example also includes the helpUrl property to provide a user assistance topic for users when they choose to add this pluggable view to a mashable or mashup. The helpUrl property for this example points to a local HTML resource in the pluggable view library, although you can point to external resources.

This pluggable view is identical to the pluggable view in Example: Pluggable View Import Basics, but it uses the mobile property to indicate that this pluggable view is not mobile compatible:

This example of a pluggable view is identical to the pluggable view in Example: Pluggable View Import Basics, but it uses two properties to customize where the pluggable view appears in the MashZone NextGen View Gallery for users and what image is used as the thumbnail.

The subtype property identifies the category (the group) where a pluggable view appears in the Gallery. This can be a category you define or one of the built-in categories in the MashZone NextGen View Gallery.

For the thumbnail, you can simply include the image in a /thumbnail folder within the pluggable view resources or use the thumbnailUrl property.

Pluggable views and custom apps can both use libraries bundled in MashZone NextGen or use pluggable libraries that have been imported to MashZone NextGen. (These pluggable libraries may be directly hosted in MashZone NextGen or may be hosted externally.) Library dependencies are defined in the dependsOn property which MashZone NextGen uses to automatically load required libraries and handle duplicate dependencies, if any.

Software AG does not and cannot authorize any use of third party software that is not permitted by these third party software licenses. You may, however, be able to obtain licenses directly from third parties. In addition, any other software that you add and/or use in connection with MashZone NextGen is subject to its own licensing requirements and may void the terms of the EULA for MashZone NextGen.

This example defines one pluggable library for D3js that supports a variety of diagrams and charts and also defines a pluggable view for MashZone NextGen that implements a D3 bar chart.

The resources and properties for the D3js pluggable library are:

The properties for the pluggable view library that depends on the D3 library to create a bar chart are:

This example has a single dependency. Multiple dependencies are allowed, simply list each library ID separated with commas. See also Finding Bundled or Other Pluggable Libraries.

You can also use third-party libraries that are bundled in MashZone NextGen in your pluggable views. Or find other pluggable libraries that have already been added to MashZone NextGen.

To find a list of available libraries, open an custom app (or start a new one) in the App Editor. Click Add and select the Library list. This list shows all libraries bundled in MashZone NextGen plus any imported pluggable libraries that have not been hidden.

This example defines a pluggable view library that uses the bundled jQuery Fancy Zoom plug-in:

Pluggable libraries can also point to third-party libraries that are hosted externally.

Software AG does not and cannot authorize any use of third party software that is not permitted by these third party software licenses. You may, however, be able to obtain licenses directly from third parties. In addition, any other software that you add and/or use in connection with MashZone NextGen is subject to its own licensing requirements and may void the terms of the EULA for MashZone NextGen.

This example shows the properties to import a pluggable library for the Report Grid charts library, which is hosted externally. There are no resources, so a folder for the library is only required to hold a properties file if you are using libImport.

You use the libPath property to define the base URL to all resources. Use the js and css properties to define relative paths to the specific external resources for this library. In this example, only one JavaScript file is used, but you can point to multiple files in both properties.