eXist-db / dashboard

eXist-db Dashboard
GNU Lesser General Public License v2.1
11 stars 19 forks source link
dashboard exist-db xar xquery

eXist-db Admin Dashboard

Admin Dashboard is a replacement of the older Dashboard and will replace it from eXist-db 5.0.0 onwards.

Building for development

The application is build with Apache Ant by executing

ant xar

This creates an unoptimized package for development purposes.

Building for production

To create a minified package execute:

ant production-xar

A note on client-side dependencies

Admin Dashboard is made of Web Components using bower for handling client-side dependency management. bower builds upon the nodejs stack and therefore require a nodejs installation to work.

Usually when using dependency tools the dependent modules are loaded dynamically from remote repositories. This has certainly advantages but also introduce the danger of undetected deep version changes and other problems when sources become unavailable for some reason. A discussion on this topic can be found here. Furthermore it requires the installation of npm and bower.

As nodejs (npm) is not available or common to everyone the dependencies are therefore kept in the repo which eases building the app.

What it does

Admin Dashboard provides a common UI for adminitration tools in a responsive sidebar layout. The layout uses the Material Design Guidelines to provide a common UI across a wide range of devices.

Currently it contains:

More modules can be plugged later on.

Features

Architecture

Admin Dashboard composes a set of Web Components into a common UI. As Web Component support is not on the same level in all browsers Polymer is used to polyfill the gaps. E.g. while Chrome already fully implements the current state of Web Components natively Firefox does not have a shadowDOM implementation at the time of this writing. Polymer bridges this gap as good as possible and provides cross-browser compatibility for all modern browsers.

For more information see https://webcomponents.org

To truly understand the impact of Web Components just a few points should be mentioned: Web Components provide truly encapsulated custom HTML elements that behave as any other HTML element but may attach styling, logic and shadowDOM to the element. As part of HTML5 they'll become native browser functionality once fully estabilshed.

Use of components in Admin Dashboard

Admin Dashboard is made of a lot of Web Components that can be found in 'bower_components' directory.

Most of those are publicly available components available from webcomponents.org but there is also a set of components specifically developed for eXist-db. These are organised in logical groups that are hosted in their own repositories.

Usually you don't have to deal with these details as this is done via bower (see bower.json) but this information is just provided for developers that want to enhance Admin Dashboard.

Here's a list repositories involved:

Hybrid Components

PackageManager, UserManager and Launcher are not just Web Components but fully functional as a standalone xar application in eXist-db. As such each of them can be checked out and build separatly. This allows to have eXist-db installations that have no Admin Dashboard at all but just e.g. a Launcher. On production system however you might want no launcher at all and only a PackageManager.

These scenarios are made possible by these hybrid components.

Compatibility

The application has been tested on:

Admin Dashboard is built with Polymer 2. See their compatibility table here.