Where do we go with the standalone GUI?

geoserver / geofence

Advanced Authorization Manager for GeoServer

GNU General Public License v2.0

99 stars 55 forks source link

Where do we go with the standalone GUI? #156

Open etj opened 4 years ago

etj commented 4 years ago

The GUI is currently implemented using GWT, with some additional obsolete dependencies which are no longer available in the various maven repos. This implementation is hardly maintanable, so the idea is to move the whole GUI using a newer JS framework. As part of this process for the moment we are disabling the UI in the build.

simboss commented 4 years ago

We have implemented a gui as part of the MapStore project.

This might be a decent way forward but some work might be required both on MapStore as well as on GeoFence.

A quick spike might be needed to assess feasibility and effort.

etj commented 1 year ago

Some options here:

replace the current GUI with an adapted version of the mapstore GUI for editing GeoFence rules;
remove the GUI, and make GeoFence standalone available via REST calls only;
remove the GUI and the REST API modules, and make it a library to only be used inside GeoServer