This enables running the same server-side code in environments using frontend code from a CDN/another domain and for example local dev environment: The domain (/cdn where static code is hosted) for client code can be configured using oskari-ext.properties.
GITHUB REPROJECTING TO MAPUBLISHER UPDATE
This could be used to provide more flexible update schedule for RPC-based applications. This allows the maintainer of an Oskari instance to provide parallel frontend code support on an Oskari instance that can be toggled with url-parameter.
The main audience for this are maintainers of RPC-based applications, but it can be used on geoportal as well. Previously markers were duplicated on the server code for frontend and printouts and service logo was also usually duplicated in frontend code as well.Īdded a new action route Logo that is used by frontend to get the service logo from server so customizing it doesn't require frontend modifications and CSS overrides.Īdded initial implementation for frontend code versioning.
The logo can be customized for Oskari instance using oskari-ext.properties and we could enable overriding the markers in a similar way in the future. See migration notes for more information about theming changes.Ī centralized helper class was added for getting markers and service logo and make customization easier. The theme can now be provided as part of an initial appsetup JSON when initializing an Oskari-based application programmatically: #909 On the same note, the map tools no longer have "toolStyle" or "font" config and the previous selections made in publisher for embedded maps have been migrated to theme JSON in the database. This enables embedded maps with user defined theme and it can also be used to customize the geoportal views.
GITHUB REPROJECTING TO MAPUBLISHER FULL
Updated java-vector-tile 1.3.16 -> 1.3.22įor a full list of changes see: Service customizationĪppsetups can now have a theme JSON in the database table oskari_tadata under the key theme.Updated commons-fileupload dependency 1.4 -> 1.5.An issue with caching in clustered environment was fixed.
0 kommentar(er)
