You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Introduction

The front end of a Blueriq application is defined by the theme that is selected at startup. This page gives a short overview of different themes and their configuration.

Themes

Currently there are different themes that can be used, which are:

  • Bootstrap3 (default)
  • Bootcards
  • Dashboard / Forms

In the following paragraphs more information will be given on the mentioned themes.

Bootstrap3

This is the default theme for all projects. This is version 2 of the MVC UI theme.

Sessions and Widgets

This theme supports multiple sessions: it consists of a main session (the actual dashboard) and a session per widget. A widget can be added by the use of the  AQ_Dashboard_FlowWidget container. The dashboard session is the main session which renders the initial page. The main session creates a subscription to the SessionService, and for each of the widgets a new Blueriq session is created and registered to that same subscription. Whenever a page event is triggered on any of the sessions, all page events for all sessions will be returned to the client and distributed to the corresponding widget viewmodels. The widget models then process the page events and that causes the update to the widgets. Widgets can communicate with each other through the message bus. The message bus is available both server and client side: The server side message bus can be used for business logic while the client side message bus can be used for technical solutions (such as refreshing a widget on a particular event).

Configuration

Add the following to application.properties. Note that mvc.themes can contain a list of comma separated themes.

mvc.developmentMode=false
mvc.versionUsed=v2
mvc.themes=bootstrap3

mvc.bootstrap3.templateGroupFile=UI/mvc/v2/bootstrap3.stg
mvc.bootstrap3.templateName=main

Add the following to

Unable to render {include} The included page could not be found.
.

<mvc developmentMode="false" versionUsed="v2">
  <themes>
    <theme name="bootstrap3" templateGroupFile="UI/mvc/v2/bootstrap3.stg" templateName="main"/>
  </themes>
</mvc>

Bootcards

The bootcards theme is designed specifically for mobile applications, but it runs on desktops as well. More information on this theme can be found at bootcards.org. See also Blueriq Mobile for more information on how to model a Blueriq mobile application and use this theme.

Configuration

You have to add the theme to your configuration to enable it.

Add the following to application.properties. Note that mvc.themes can contain a list of comma separated themes.

mvc.developmentMode=false
mvc.versionUsed=v2
mvc.themes=bootcards

mvc.bootcards.templateGroupFile=UI/mvc/v2/bootcards.stg
mvc.bootcards.templateName=main

Add the following to

Unable to render {include} The included page could not be found.
.

<mvc developmentMode="false" versionUsed="v2">
  <themes>
    <theme name="bootcards" templateGroupFile="UI/mvc/v2/bootcards.stg" templateName="main"/>
  </themes>
</mvc>

 

 ---------------------

Dashboard

The Blueriq dashboard theme is built on top of the default forms components used in the forms theme. The difference with the forms theme is that the dashboard theme supports multiple sessions: it consists out of a main session (the actual dashboard) and a session per widget. A widget can be added by the use of the AQ_DashboardFlowWidget container.

For using this theme the Dashboard plugin is required.

Sessions

The dashboard session is the main session and is the session rendering the initial page. The main session creates a subscription to the SessionService, and for each of the widgets a new Blueriq session is created and registered to that same subscription. Whenever a page event is triggered on any of the sessions, all page events for all sessions will be returned to the client and distributed to the corresponding widget viewmodels. The widget models then process the page events and that causes the update to the widgets.

Widget Communication

Widgets can communicate with each other through the message bus. The message bus is available both server and client side: The server side message bus can be used for business logic while the client side message bus can be used for technical solutions (such as refreshing a widget on a particular event).

Enable

To enable this style, make sure the following lines are existing in your dashboard.properties (or in application.properties).

mvc.versionUsed=v1
mvc.themes=dashboard

mvc.dashboard.templateGroupFile=UI/mvc/v1/dashboard.stg
mvc.dashboard.templateName=main

 

--------------

Forms

The theme 'forms' had been the standard for MVC UI. This theme contains all default Blueriq UI components and standard functionality for e.g. flowing and refreshes. Note that this theme does not support dashboard styling.

Enable

To enable this style, make sure the following lines are existing in your application.properties.

mvc.versionUsed=v1
mvc.themes=forms

mvc.forms.templateGroupFile=UI/mvc/v1/forms.stg
mvc.forms.templateName=main

 

The theme 'forms' had been the standard for MVC UI. This theme contains all default Blueriq UI components and standard functionality for e.g. flowing and refreshes. Note that this theme does not support dashboard styling.

Enable

To enable this style, make sure the following lines are existing in your application.properties.

mvc.versionUsed=v1
mvc.themes=forms

mvc.forms.templateGroupFile=UI/mvc/v1/forms.stg
mvc.forms.templateName=main

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  • No labels