[Kexi-devel] Proposed message for the query export when its design is "dirty"

Robert Leleu robert.jean.leleu at wanadoo.fr
Thu Feb 12 15:48:39 UTC 2015


I think this proposal is interesting

Je la 12/02/2015 14:35, Jaroslaw Staniek skribis :
> On 12 February 2015 at 14:15, Jaroslaw Staniek <staniek at kde.org> wrote:
>
>> "Design of query <resource>%1</resource> that you want to export data
>> from is changed and has not yet been saved. Do you want save it prior
>> to exporting or use the original query for exporting?"
>>
>> Buttons: [Save and Export] [Export From the Original] [Cancel](default)
>
> Now the question remains for this function http://i.imgur.com/E82URWs.png.
> It's exactly the same as the "export to file" here
> https://i.imgur.com/HjF2xoQ.png.
>
> After a minute I am not sure requiring Save before I can export the
> function is natural.
> I can imagine user quickly altering the query design without saving
> and exporting the data results to CSV.
> Or copying to the clipboard. Quite handy. Then she can close the
> design without saving if she wants.
>
> So how about this rephrased message:
>
> "Design of query <resource>%1</resource> that you want to export data
> from is changed and has not yet been saved. Do you want to use data
> from the changed query for exporting or from its original (saved)
> version?"
>
> Buttons: [Use the Changed Query] [Use the Original Query] [Cancel](default)
>
> PS: Extra requirement proposed: to show users more context, before
> asking the user, switch the tab to the opened window containing  the
> query (without changing its view mode).
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kexi-devel/attachments/20150212/df07d466/attachment.html>


More information about the Kexi-devel mailing list