| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow customizing the client via external properties and resources,
instead of just the built-in resources.
Built-in configuration takes highest priority, as usual, but built-in
resources (images, text) take lowest priority.
Any config file in the current working directory will be the first
fallback.
Finally, a system-wide path will be considered. On Windows, this is
%ProgramData%\bwlp\, on Linux /etc/bwlp/.
If a config was found in either of those places, the app will also try
to load any resources (images, text) from there, only falling back to
the resources withing the jar if they don't exist.
You can still use --dump and --pack with these changes, but --dump
will only ever dump the active configuration and the resources found
within the jar, not those from the file system.
|
|
|
Application name, service name, master server endpoints, documentation
websites needed to be configurable to allow for an easy rebranding of
the suite.
Two new options allow this: use '--dump <folder>' to dump the jar's
configurable files into that folder. Aside from text templates in 'txt',
logos and icons in 'img', the 'branding.properties' file contains:
* masterserver.address : self-explanatory
* application.name : name to be shown on graphical elements like the
main window
* service.name : name to be used as a prefix for formulation like
'bwLehrpool-Team' or 'bwLehrpool-System' etc
* service.faq.website : link to FAQ website
* service.email : support contact address
Once edited, the whole folder can be integrated into the Suite with
'--pack <folder> <new_jar>'. The path to the new jar is then the
rebranded version of the suite.
|
