You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
Framework
At the core of each Blueriq theme you find the @blueriq/angular
framework. A detailed guide on what the framework offers and how you may use it is published in the user documentation, of which you can find the latest version from the API documentation page.
Theming
Out of the box, a default theme is distributed with the Blueriq Runtime for showcase purposes. This theme is built-in and can neither be modified nor extended, which ensures that any custom front-end components do not depend on the specific theme version that is supplied with a Blueriq Runtime version. This approach allows for smaller migrations of the Blueriq Runtime, as any theming related changes do not directly affect your custom theme or components.
For you to get started using theme-development, the default theme's source code is available on Github such that you may fork it and modify/extend it to suit your needs. while being able to keep up-to-date with upstream activity. This theme uses the Angular CLI for development, testing and building your application.
Angular in Production
For bringing your custom Angular theme into production, please refer to the Angular CLI documentation on building an application into a small set of Javascript bundles for production usage. We recommend serving these files from a different server than the Runtime environment itself, for example a CDN environment specifically for hosting all static assets.
In order to adhere to the same-origin security policy without needing to configure additional CORS headers to allow certain cross-origin requests, we recommend that you either 1) configure a reverse proxy server or 2) configure a subdomain with custom DNS bindings.
DNS Routing
As an alternative to setting up a reverse proxy server, you may choose to create a subdomain for CDN purposes. In the DNS configuration of your host, you may configure a different IP address for this subdomain, such that asset requests are directly routed to the CDN and API requests arrive at the Runtime instance.
Reverse proxy server
In a reverse proxy server, you may configure redirects based on incoming request paths such that Runtime API requests are redirected to the Runtime backend(s) and static resources are downloaded from the CDN server.
If you are using a clustered Runtime setup, you may choose to implement these redirects in your load balancer layer.
Note that Blueriq ships a prepackaged Material Theme with the Runtime. This theme is only meant to run applications from the development dashboard. Running this theme (or any custom theme that is added as a jar to the Runtime) in production is not supported. For production, you should deploy the theme as described above.
Custom themes from development dashboard
Starting Blueriq 14.6 it is possible to start applications using an non prepackaged theme from the development dashboard, more information can be found here.
3 Comments
Jack
Hi all,
Will Blueriq v12 still support the the 'old' frontend (Knockout) theme?
Joost Koehoorn could you answer this please?
Frank van der Vaart
I added this to my application.properties file to get the old Knockout theme (as a second choice besides Angular Material):
# mvc
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
Joost Koehoorn
Hi Jack,
As it currently stands, no new features will be added to Knockout anymore but existing usages are still supported. The Knockout theme is expected to be removed in R13 next year, at which point its source code will have been open sourced on GitHub.