Here is review261011002. I added two screenshots to show how it looks like.
So mainly I added a button under the save which allows to copy (or open) the URL.
I also added an option to allow to export all the listed records instead of just the selected (as usual).
On 2020-02-26 10:25, José Salvador wrote:
> What do you think about to show in the UI the 'URL export' as option instead of a button?
>
> I mean, for example, before 'CSV Parameters', something like that:
>
> X URL export if_activated_this_will_represent_a_read_only_field_with_the_URL
>
> I hope you understand what I'm trying to mean...
You want an option button to show the URL button. I do not see the point.
Also this has no relation with the CSV parameters.
> You want an option button to show the URL button. I do not see the point.
> Also this has no relation with the CSV parameters.
Nope. I propose a check box to activate or not the 'URL export' as an option of the export process not as an option of CSV parameters.
Once the user choose (activating the checkbox) that export should be 'URL exportable' a read only field will appear to show the URL.
This way there is no need to show another button for the URL export. The 'URL exportable' feature is just an option for the general CSV export process.
PS -> I didn't see you posted the screenshots in the discuss thread so I tried in first attempt to help here instead of discuss. If you consider that this comments should be published in discuss thread (I guess yes) let me know to follow the discussion there.
On 2020-02-26 11:02, José Salvador wrote:
> > You want an option button to show the URL button. I do not see the point.
> > Also this has no relation with the CSV parameters.
>
> Nope. I propose a check box to activate or not the 'URL export' as an option of the export process not as an option of CSV parameters.
Why would you want to make it an option?
> Once the user choose (activating the checkbox) that export should be 'URL exportable' a read only field will appear to show the URL.
Why this behavior instead of reusing the same design for resource URL?
> Why would you want to make it an option?
> y this behavior instead of reusing the same design for resource URL?
I think it is more user-friendly because the user has a unique export with the capacity to become it 'URL exportable'.
For me, showing another button can lead to confusion. It's like the user would have two exports instead of one when really there is only one export process (that can be saved) and this one is the CSV export that the user can become it as a 'URL exportable' too.
On 2020-02-26 11:44, José Salvador wrote:
> > Why would you want to make it an option?
> > y this behavior instead of reusing the same design for resource URL?
>
> I think it is more user-friendly because the user has a unique export with the capacity to become it 'URL exportable'.
>
> For me, showing another button can lead to confusion. It's like the user would have two exports instead of one when really there is only one export process (that can be saved) and this one is the CSV export that the user can become it as a 'URL exportable' too.
I placed with the Save and Delete button because it is a management
action (not the principal action). That's why clicking on it does not
close the dialog (but open on a new tab). But the main goal is to allow
to copy it with the right-click.
For me, your proposal will be confusing because what will happen if I
select the checkbox for exportable URL and than I click on OK? I think
some user will think it should give the URL and other would think it
should close the dialog (but then what is the point of the cancel
button).
I guess I am understanding the problem better thanks to your explanations.
Anyway it still sounds strange to me to place a button to get a data (the URL) with apparently the same importance that save and delete export actions.
I'm gonna to give you another idea to show the URL without a button.
It would consist in a run time URL building while user is configuring the export. (if this solution is good performant and does not require round trips to the server, of course).
It will be showed in a read only field with the ability to be copied to clipboard (if Tryton is able to do that) like github does.
I attach an image prototype with this proposal.
Excuse me in advance for my poor abilities managing GIMP. :-(
I just found that IMPORTDATA from Google spreadsheet does not support authentication on the URL. I'm wondering if we should support alternative authentication via arguments? Of course it should not contain user/password but some sharing key.