|Re: Application-defined themes [message #1791726 is a reply to message #1791672]
||Wed, 04 July 2018 13:34
| Gunnar Adams
Registered: May 2016
thanks for your response.
You raise a good question, which I will try to answer:
I know about entrypoints and different theme files for each one of them and we are already using this to support the different products my company offers to different target audiences (e.g. corporates and banks). Each of those products has a slightly different look & feel and we have used the theme.css files with different entry points to cater for all products with a single client.
So, we have an exact idea how our application should look like by default.
But what, if a customer wants to have a special look because of some corporate identity guidelines. For instance, a company wants to use their own fonts in the user interface (input fields and such). For those kinds of customization it would be nice to define them in our backend application server once (valid for a customer on all client platforms) and not to have to manage a larger number of theme.css files (one for each customer). A larger number of theme.css files would also mean, that we have to package a slightly different client WAR for each customer, which we don't want to do.
Some of the customers want to do those kinds of adjustments on their own. Thus, it should be easier than editing a theme.css, where, if you make a mistake, the whole application may not work. On top of that, not all of our customer's IT departments are fit to integrate a modified theme.css file into the standard package which we deliver.
I am thinking about some kind of manipulation to the ThemeManager which allows to
modify (some) properties from the css file (after it has been read). Usually this would only have be done for the first application session established on a newly deployed application or after a restart of the web application container. The problem is, that the client application connects to the backend application server only AFTER the theme has been fully initialized.
modify the theme.css file before it is loaded by the ThemeManager. The data for the modification should come from some external resource.
load the theme.css from an external resource entirely. The fact that it currently is an essential part of the WAR file we deploy is part of the problem. If it could be read from, e.g. , a web service, located with the backend server, which generates a theme.css from easier to maintain style data, then that would be a solution.
Any further ideas?
Powered by FUDForum
. Page generated in 0.02281 seconds