HI,
I have made a proposal for the resource store GUI:
https://github.com/geoserver/geoserver/wiki/GSIP-139
Please let me know what you think.
Kind Regards
Niels
Looks good Niels, UI proposals are always tough (and change in the telling when you start implementing).
Not sure if you need a download button, often clicking on the file in the list should download it? Or if the idea is to check several things and download a zip …
what is the difference between “new” and “upload”? Reading more closely they are for text files … do you have any good way of telling what resources contain text?
Still I think this is an important step towards making JDBCConfig usable in production.
···
On 23 February 2016 at 01:23, Niels Charlier <niels@anonymised.com> wrote:
HI,
I have made a proposal for the resource store GUI:
https://github.com/geoserver/geoserver/wiki/GSIP-139
Please let me know what you think.
Kind Regards
Niels
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Jody Garnett
I untangled your bullet points, and seperate out the images so I could see what you intended for each button/dialog. This results in some duplication of text, but was easier (for me at least) to follow. Please review and let me know if I messed anything up?
Small feedback for discussion:
- Consider using “Path” rather than “Directory” (consistent path/resource terms rather that directory/file terms)
- Check for consistent use of “Name” and “New Name” (for example Create new Resource just has “Name” and not “New Name”)
- Consider “Rename/Move” → “Move”
- Consider changing “New directory”/“new name” combo to “Path”/“New Name” (ie is “New Path” required? (Yes I know moving a resource can result in a new path being “created”…)
···
On 23 February 2016 at 09:55, Jody Garnett <jody.garnett@anonymised.com> wrote:
Looks good Niels, UI proposals are always tough (and change in the telling when you start implementing).
Not sure if you need a download button, often clicking on the file in the list should download it? Or if the idea is to check several things and download a zip …
what is the difference between “new” and “upload”? Reading more closely they are for text files … do you have any good way of telling what resources contain text?
Still I think this is an important step towards making JDBCConfig usable in production.
–
Jody Garnett
–
Jody Garnett
On 23 February 2016 at 01:23, Niels Charlier <niels@anonymised.com> wrote:
HI,
I have made a proposal for the resource store GUI:
https://github.com/geoserver/geoserver/wiki/GSIP-139
Please let me know what you think.
Kind Regards
Niels
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Thanks, Jody. Comments inline.
On 23-02-16 20:01, Jody Garnett wrote:
I untangled your bullet points, and seperate out the images so I could see what you intended for each button/dialog. This results in some duplication of text, but was easier (for me at least) to follow. Please review and let me know if I messed anything up?
Small feedback for discussion:
- Consider using "Path" rather than "Directory" (consistent path/resource terms rather that directory/file terms)
Hmmm... But these all regards directories. The directory where the resource is to be placed in. Paths can be to the whole resource, that is not clear enough in this context.
- Check for consistent use of "Name" and "New Name" (for example Create new Resource just has "Name" and not "New Name")
Okay... the way I saw it, "new name" is when you are replacing an old name.
- Consider "Rename/Move" --> "Move"
Is it obvious to everyone (including people not familiar with linux shells) that moving is also for renaming?
- Consider changing "New directory"/"new name" combo to "Path"/"New Name" (ie is "New Path" required? (Yes I know moving a resource can result in a new path being "created"...)
New directory doesn't refer to directory creation here, similar to new name it means the new directory for the resource to be placed in as opposed to the old directory.
Regards
Niels
On 23-02-16 18:55, Jody Garnett wrote:
Looks good Niels, UI proposals are always tough (and change in the telling when you start implementing).
Not sure if you need a download button, often clicking on the file in the list should download it? Or if the idea is to check several things and download a zip ...
what is the difference between "new" and "upload"? Reading more closely they are for text files ... do you have any good way of telling what resources contain text?
Indeed, new is to create a text file with the inline plain text editor. For existing files, we can use the mime type. If there is no mime type, we could open it anyway (maybe only if < certain size) and display a warning.
Regards
Niels
Thanks for the discussion, have a look again at the bullet points (I am sure I missed something in refactoring your page).
···
On 24 February 2016 at 01:58, Niels Charlier <niels@anonymised.com> wrote:
Thanks, Jody. Comments inline.
On 23-02-16 20:01, Jody Garnett wrote:
I untangled your bullet points, and seperate out the images so I could see what you intended for each button/dialog. This results in some duplication of text, but was easier (for me at least) to follow. Please review and let me know if I messed anything up?
Small feedback for discussion:
- Consider using “Path” rather than “Directory” (consistent path/resource terms rather that directory/file terms)
Hmmm… But these all regards directories. The directory where the resource is to be placed in. Paths can be to the whole resource, that is not clear enough in this context.
- Check for consistent use of “Name” and “New Name” (for example Create new Resource just has “Name” and not “New Name”)
Okay… the way I saw it, “new name” is when you are replacing an old name.
- Consider “Rename/Move” → “Move”
Is it obvious to everyone (including people not familiar with linux shells) that moving is also for renaming?
- Consider changing “New directory”/“new name” combo to “Path”/“New Name” (ie is “New Path” required? (Yes I know moving a resource can result in a new path being “created”…)
New directory doesn’t refer to directory creation here, similar to new name it means the new directory for the resource to be placed in as opposed to the old directory.
Regards
Niels
–
Jody Garnett
Had to fix a few small mistakes, but looks fine otherwise. To be clear, “Directory” is part of the resource store terminology that was chosen before me. Each resource object has a type which is either UNDEFINED, DIRECTORY or RESOURCE. To be honest I never liked the double meaning of “resource” (it can either exclude directories or not). A path on the other hand can point towards any type of resource, it is not comparable to a directory. Regards Niels
···
On 24-02-16 11:07, Jody Garnett wrote:
Thanks for the discussion, have a look again at the bullet points (I am sure I missed something in refactoring your page).
- Consider using “Path” rather than “Directory” (consistent path/resource terms rather that directory/file terms)
Hmmm… But these all regards directories. The directory where the resource is to be placed in. Paths can be to the whole resource, that is not clear enough in this context.