Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Where do we go with the standalone GUI? #156

Open
etj opened this issue Oct 20, 2020 · 2 comments
Open

Where do we go with the standalone GUI? #156

etj opened this issue Oct 20, 2020 · 2 comments
Labels

Comments

@etj
Copy link
Member

etj commented Oct 20, 2020

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.

etj added a commit that referenced this issue Oct 20, 2020
@simboss simboss changed the title GUI issues Where do we go with the standalone GUI? Oct 20, 2020
@simboss
Copy link
Member

simboss commented Oct 20, 2020

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
Copy link
Member Author

etj commented Mar 3, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants