Hello Andrea,
Thanks for your review! Responses are inline.
On 16-03-16 19:46, Andrea Aime wrote:
At the same time, it means that the GUI needs to work fine with the
file system... like, what if
there is a very large number of files (styles, layers, whatever), is
the UI going to scale up enough
to handle them, or may it lock up?
Even if it's painful, there are deploys with thousands of layers
around, and if one needs to modify
say a FTL template, there is an actual need to scan in the workspaces
directory to place it in the
right spot, e.g. next to the target layer (oh fun, and if it's
JDBCConfig, you have to create by hand
all the intermediate folders that would be missing because those
config objects are in the jdbconfig?)
If you are using JDBCConfig, there is no support for direct file editing
of the catalogue. All manipulations should already be supported by the
catalogue UI pages. This GUI is _only_ for JDBCStore resources.
Looking at the upload dialog, if one can select the target in the tree
and then have that
bit pre-populated in the upload GUI, is there actually a need to allow
choosing on yet another browser
a different location? Just exit the dialog and choose a different
target instead?
This is necessary, because the user might want to upload a file to a not
yet existing directory. Mind that resourcestores don't support the
creation of empty directories, directories can only be created on the fly.
Which is btw what you are doing in the rename/move case no?
With the destination, it is the same deal.
Merging toghether rename and move seems a lot like a unix approach,
but I guess the common user
would be more comfortable having two simpler dialogs "rename" and
"move" instead, where
rename just has the new name, and move just the target location,
instead of both. Not a strong
opinion on this one, but I'm figuring the classic windows user be a
bit confused by it.
Perhaps, but the benefit is that you can move dir and name at the same
time and do what would otherwise need two operations in one.
I would in any case keep the button saying "move/rename" (and not just
move) so that people know what to click on when they need to rename.
Once they open the dialog, the rest should be trivial. They only need to
change the dir/name if they want to. I am a linux person though.
Same goes for copy.... trying to imagine what one might want to
copy... maybe ftl templates?
Those are normally not renamed, but... they are normally transferred
in triplets.
Have you considered a clipboard like approach instead, accumulate more
than one file in it,
and the allow pasting/moving to a target location? Not sure how much
harder it would be,
just wondering, it would make some interaction more natural (like
trying to copy/move FTL files
around).
This is an interesting idea, I would definitely consider as an
alternative. Interested to hear what others think.
Regards
Niels
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
