[Kmymoney] Request Feedback - CSV Plugin UI

[Jack]

On 2014.10.25 08:38, Allan wrote:
> On 22/10/14 11:53, Thomas Baumgart wrote:
>> On Wednesday 22 October 2014 11:47:11 Allan wrote:
>>> On 22/10/14 07:25, Thomas Baumgart wrote:
>>>> On Tuesday 21 October 2014 10:06:59 Jack wrote:
>>>>> On 2014.10.21 06:35, Allan wrote:
>>>>>> I've been doing some work with the CSV Exporter plugin, and  
>>>>>> using the Importer plugin to visualize the results.
>>>>>> 
>>>>>> While doing this, I realised that there is no way to import the  
>>>>>> transaction status - Cleared, Reconciled, etc.  If I were to  
>>>>>> implement this field in the importer, it would exacerbate the  
>>>>>> present very busy appearance of the Banking wizard UI.
>>>>>> 
>>>>>> So, I came back to wondering if a new approach might be better,  
>>>>>> so I'm attaching a screen-shot of the possible new layout.  It's  
>>>>>> very much simplified, which is good, but might it be less  
>>>>>> helpful?
>>>>>> 
>>>>>> The idea is that, instead of having a combo-box for each field,  
>>>>>> there are just two combos, one containing the field types, and  
>>>>>> another for the user to assign the column of that field.
>>>>>> 
>>>>>> I'd be interested to get your views, both for and against.  A  
>>>>>> similar arrangement would be needed for the Investment wizard.
>>>>>> 
>>>>>> Allan
>>>>> 
>>>>> As a way of selecting columns for fields, it may be fine  
>>>>> (although will it allow multiple selections where appropriate?)  
>>>>> but what about display?  It is important to be able to see all  
>>>>> the selections at once.  However, displaying them as text (or  
>>>>> label, since it would be read only) or series of text items may  
>>>>> well be more compact than having entry fields and dropdowns for  
>>>>> each.
>>>> 
>>>> How about a QListView with two columns showing the column and  
>>>> type. It should give you automatic scrolling and all that. Or am I  
>>>> missing something?
>>> Thanks Thomas
>>> 
>>> I'll look into that, too.  At the moment, I'm thinking of  
>>> QTableWidget, because height is restricted, in order to sit below  
>>> the tableWidget displaying the data, with possibly, two sets of  
>>> paired columns.
>> 
>> My bad, of course a QListView with two columns is a QTableView which  
>> is inherited by QTableWidget. So we're talking about the same thing  
>> here.
> 
> I think this version may be suitable.  Initially, column 1 will get  
> the first field type selected, and then each sequential column.  
> Alternatively, select a cell to use and then its field type.  It size  
> is 10K, as against 20K for the existing version.  Any thoughts?
> 
> At the moment, its a free-standing 160K compressed executable, if  
> anyone wishes to play.
> 
> If OK, I'll integrate it and put it to reviewboard
> 
> Allan
Looking good.

It would be great if these columns lined up with the columns in the  
data table, but I don't know if it's reasonable to program.  Or - will  
the Field Type row just be the first or last column in the table?

I assume memo can show up in more than one column?  Also, if I remember  
from the latest wizard, there is an issue with the order of assigning a  
column to more than one field - how is that handled in this version?

Jack