Page History

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.

...

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

• Bootstrap3 (default)
• Bootcards
• Dashboard (deprecated)
• Forms (deprecated)

...

This is the default theme for all (desktop) projects. Bootstrap3 is part of version 2 of the MVC UI styling.

Description

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 the  AQ_Dashboard_FlowWidget container 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

blueriq.mvc.development-mode=false
blueriq.mvc.themes.bootstrap3.template-group-file=UI/mvc/v2/bootstrap3.stg
blueriq.mvc.themes.bootstrap3.template-name=main
blueriq.mvc.active-themes=bootstrap3
 

...

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

Bootcards

This is the theme for mobile applications. Bootcards is part of version 2 of the MVC UI styling.

...

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 at bootcards.org. See also also Blueriq App Builder for  for more information on how to model a Blueriq mobile application and use this theme.

...

blueriq.mvc.development-mode=false
blueriq.mvc.themes.bootcards.template-group-file=UI/mvc/v2/bootcards.stg
blueriq.mvc.themes.bootcards.template-name=main
blueriq.mvc.active-themes=bootcards

...

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

Dashboard (deprecated)

The dashboard is the former default theme. It is part of version 1 of the MVC UI styling.

...

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 the AQ_Dashboard_FlowWidget container container.

...

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. Widgets  Widgets can communicate with each other through the message bus.

...

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

...