YASR

YASR (Yet Another SPARQL Resultset visualizer) is part of the the YASGUI tool. For more information about YASR, its features, and how to include it in your web site, visit http://yasr.yasgui.org.

Developing YASR

To develop this tool locally, use the following procedure:

• Make sure npm and gulp are installed or use local gulp as bellow, gulp need to be version 3.x.x, errors may occur with with gulp 4 or higher
• It's recommended to use nodejs v.6.11.0 for the following steps. The easiest way to get it is to install the Node version manager (nvm) and then install required node version nvm install 6.11.0.
• If you just checkout the repository, then you must run npm install from the base dir to install needed dependencies.

Run with LIBSASS_EXT="no" npm install if you have gulp-sass error!

• Implement whatever changes are needed, issue a merge request, pass it for codereview to one of the frontend team members and once it's approved, go ahead and merge the branch in the master.
• Once the branch is merged, the source code have to be built. Do it by running ./node_modules/gulp/bin/gulp.js to create the dist (distribution) package. The package contains a regular bundled version of the lib in yasr.js and also a bundled and minified version in yasr.bundled.js. The dist package also contains the style definitions in the yasr.css file.
• Once the distribution is ready, create a branch in the GDB workbench repository. Then copy and overwrite the yasr.bundled.js file in the desired branch in GDB workbench repository under /graphdb-workbench/src/js/lib package. Do the same with the yasr.css by copying it under /graphdb-workbench/src/css/lib.
• After that, create a merge request in the GDB workbench repository from the branch, assign it for review and once it's approved, go ahead and merge it.

Internationalization

YASR and YASQE are used internally in the GraphDB workbench application. It should provide a locale configuration during the initialization of either of them. The provided locale is used to resolve translations for any message or label in both libraries.

The default locale is en. It'll be used if no locale is provided during initialization.

Add new localisation file

• Do a clone of one of the available localisations in the src/i18n folder and translate all messages.
• Import the new localisation file in src/translate.js service like this:

const bundle = {
    "en": require('./i18n/locale-en'),
    "fr": require('./i18n/locale-fr')
};