[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval |needsDevEval CC|libreoffice-ux-advise@lists |tietze.he...@gmail.com |.freedesktop.org| --- Comment #31 from Heiko Tietze --- We discussed the topic in the design meeting with the following outcomes: * special uno:command(s) * checkbox in open dialog to bypass the import dialog (jay) * use or to bypass the dialog when it is intended to appear (jay) in the file dialog when pressing open button, clicked the file in start center, or drag and drop * introduce some kind of heuristics that detects the format and only asks if unsure (csongor) * simplest heuristic would be the URL and after first time reading file from this place the dialog doesnt pops-up again (jay) perhaps plus a filename comparison (./file1.csv=./file2.csv) * rather improve the import dialog with use of parser settings saved to profile (stuart) -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 --- Comment #30 from Gareth --- In reply to Comment #29 (from V Stuart Foote) re. whether a parallel task is needed for the HTML import. > Importing sheet data from HTML is very much a corner case, in fact a user > given a preference shuold be picking TSV or CSV to assure data quality > compared to a table pulled from HTML. Importing a table is one possibility, but you can simply save or generate a spreadsheet as HTML. It has some advantages over CSV, especially in formatting. Anyway, it doesn't really matter whether it's a corner case, or what some developer or discussion participant magisterially thinks users 'should' do. The fact is that it is an existing use case, in regular use in businesses I have come across. Calc currently handles it in the same way as importing a CSV (simplified, since importing HTML is simpler) and I merely point out that it would be good practice for it to continue to do so, if the way of importing CSVs changes. TSV may also be a corner case. I had to look it up. But if Calc currently handles it in the same way as CSV, yes, it would be good to continue to do so. > Having the minimally intrusive textimportoptions.ui dialog [1][2][3] appear > when opening a non-CSV document, including HTML, into Calc is not the issue > here. Rather improving work flows for parsing complex CSV The dialog is as intrusive as the CSV dialog, in the sense that it appears every time. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 --- Comment #29 from V Stuart Foote --- (In reply to Gareth from comment #28) > The same issue exists with HTML. (As mentioned above at Comment #10.) If > csongor's solution is chosen, then a separate task probably needs to be > raised for an HTML section in the new preference settings page. > An HTML import uses the generic textimportoptions.ui; CSV is textimportcsv.ui completely different GUI and data handling. > The HTML import dialog is simpler than the CSV one because the HTML format > contains more column format information, and the same will apply to its > preferences section. But there is an import dialog, so the basic issue is > the same. Hmm, not really. Importing sheet data from HTML is very much a corner case, in fact a user given a preference shuold be picking TSV or CSV to assure data quality compared to a table pulled from HTML. Having the minimally intrusive textimportoptions.ui dialog [1][2][3] appear when opening a non-CSV document, including HTML, into Calc is not the issue here. Rather improving work flows for parsing complex CSV =-ref-= [1] https://opengrok.libreoffice.org/xref/core/sc/uiconfig/scalc/ui/textimportoptions.ui [2] https://opengrok.libreoffice.org/xref/core/sc/source/ui/dbgui/textimportoptions.cxx [3] https://opengrok.libreoffice.org/xref/core/sc/source/ui/inc/textimportoptions.hxx -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 --- Comment #28 from Gareth --- In reply to cson...@halmai.hu (Comment #27) > currently only CSV would exist there The same issue exists with HTML. (As mentioned above at Comment #10.) If csongor's solution is chosen, then a separate task probably needs to be raised for an HTML section in the new preference settings page. The HTML import dialog is simpler than the CSV one because the HTML format contains more column format information, and the same will apply to its preferences section. But there is an import dialog, so the basic issue is the same. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 --- Comment #27 from cson...@halmai.hu --- (In reply to Knocks from comment #25) > And as others have mentioned above, Excel does this right. LibreOffice does > it wrong and is user-hostile. I have to contradict, sorry. :) Sometimes I work with CSV files from different sources. There is one thing that should be understood clearly. CSV is not a file format. It is an extension which people use for different formats. Literally it means _Comma_ Separated Values but the same extension is used for tab-separated, semicolon-separated and other file formats. Sometime windows-line-endings are used, sometimes not. You simply cannot rely solely on the extension to guess how you should interpret the content of a file. That's the reason why two technics can be used: 1. heuristics, that try to make smart guesses how to understand files. It mostly works but sometimes not. This is what Excel does and if it fails then you have no chance to convice it to think differently. (I hate it if this comes up. :)) 2. user interaction, when I can configure each nuances of the content interpretation. I think LO does the correct way: make a reasonable guess and then asks the user whether they confirm or not. This should not be changed. A small feature we could do is, however, to introduce a new setting under Preferences => LibreOffice Calc => Import (doesn't exist yet). On this page, each file extension could have a separate section, currently only CSV would exist there. The CSV section should have the following settings: ( ) Apply smart guess (O) Use the most recent settings [X] let the user to confirm/change the proposal With this, the use can toggle whether they want to confirm each dialog or just trust the system, plus could tell they want to use the heuristics or simply just use the latest one. It would be even better in the future if the heuristic would be pluginable: some users would write smart code that recognise which software created that particular CSV, and so on. It would go far beyond the topic of this ticket but the perspective is quite interesting, I think. At the moment, I would just stick with the two radio buttons and one checkbox I detailed above. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 --- Comment #26 from Cor Nouws --- Suggest discussing at UX-meeting. Just hitting "Enter" is enough. One might expect that the regular csv-openers will understand that soon enough. Also looking at Eike's advice, my suggestions is: Close as NOTABUG. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 --- Comment #25 from Knocks --- And as others have mentioned above, Excel does this right. LibreOffice does it wrong and is user-hostile. I opened this ticket 4 years ago and have since moved to a different industry that no longer requires opening lots of CSV files daily. But I do remember uninstalling LibreOffice and feeling great about it, because of how stubborn and unwilling to consider the user experience its developers are. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 --- Comment #24 from Eike Rathke --- As already mentioned in comment 1 the settings meanwhile are remembered and, except the column types, presented as pre-set for the next open. An extra "open bypassing the dialog" option IMHO just adds confusion when things go wrong, and the user will have to differentiate or select that somehow which is more work than just hitting Enter for OK. YMMV though and some may prefer an extra menu entry or some such, I don't know. For me it's unnecessary. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 V Stuart Foote changed: What|Removed |Added CC||er...@redhat.com, ||libreoff...@kohei.us, ||vstuart.fo...@utsa.edu --- Comment #23 from V Stuart Foote --- I'd like dev input, but believe a parsing filter set from the CSV input dialog will always be necessary to assure correct data type handling. End of story. However, the nuisance to users is that there is no means to capture/reapply the CSV filter, and they must repeatedly work through the dialog, even if defaults are correct. More so if they have a fairly complex CSV file that requires data type settings on multiple columns. Seems there should be a means to capture the parsing/formatting filter for reuse against _recurring_ CSV files, even in multiple LO sessions--so filter(s) would need to be held in user profile. Then adding an option to by-pass the dialog popup (for GUI use) when applying that filter from profile would be reasonable. And probably would want something for use with CLI conversions. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 74580] FILEOPEN: Add option to disable import dialog when opening a CSV file ( see comment #13)
https://bugs.documentfoundation.org/show_bug.cgi?id=74580 Cor Nouws changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org Whiteboard|BSA | -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise