GeoServer

Provide a list of stores in the workspace editor

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: 2.0.x
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Should be part of a separate tab, and have pretty much the same functionality as the stores page, but pre-filtered on a single workspace

Issue Links

is depended upon by

Task - A task that needs to be done. GEOS-2705 Wicket UI styling and usability improvements

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.
is related to

Improvement - An improvement or enhancement to an existing feature or task. GEOS-3199 workspace view

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

So, we have this one open and actually the workspace view contains a list of stores, but as GEOS-3199 notices, it's less than ideal.
It would be a lot better, imho, if the workspaces list was in its own separate tab in the same page (just like the layer editor page structure).
Also, if we have the stores inside the workspace page, for consistency we should have also the layers in the store page.

Soo... what do we do? I'd say, we have either both or we remove the workspace list from the workspace page and then resolve this one by 2.1?

Show
Andrea Aime added a comment - So, we have this one open and actually the workspace view contains a list of stores, but as GEOS-3199 notices, it's less than ideal. It would be a lot better, imho, if the workspaces list was in its own separate tab in the same page (just like the layer editor page structure). Also, if we have the stores inside the workspace page, for consistency we should have also the layers in the store page. Soo... what do we do? I'd say, we have either both or we remove the workspace list from the workspace page and then resolve this one by 2.1?
Hide
Permalink
Andrea Aime added a comment -

Justin, sorry I missed your comments this morning. Anyways, for consistency imho we should have the list of "child" objects in all pages, or in none. If the line is to delay further UI improvements then imho the store list showing in the workspace editor should be commented out for the moment.

Show
Andrea Aime added a comment - Justin, sorry I missed your comments this morning. Anyways, for consistency imho we should have the list of "child" objects in all pages, or in none. If the line is to delay further UI improvements then imho the store list showing in the workspace editor should be commented out for the moment.
Hide
Permalink
Justin Deoliveira added a comment -

Agreed about consistency. So sure for this cut why don't we just comment it out. And then we can come up with a plan to globally display "child" objects on a page, be it on a tab or wherever. Unless someone wants to tackle that issue now.

Show
Justin Deoliveira added a comment - Agreed about consistency. So sure for this cut why don't we just comment it out. And then we can come up with a plan to globally display "child" objects on a page, be it on a tab or wherever. Unless someone wants to tackle that issue now.
Hide
Permalink
Andrea Aime added a comment -

Commented out the store list and moved the issue to 2.0.x

Show
Andrea Aime added a comment - Commented out the store list and moved the issue to 2.0.x

People

  • Assignee:
    Andrea Aime
    Reporter:
    Andrea Aime
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:

Time Tracking

Estimated:
1d
Original Estimate - 1 day
Remaining:
1d
Remaining Estimate - 1 day
Logged:
Not Specified
Time Spent - Not Specified