Project

General

Profile

Actions

feature request #7518

closed

remaining issues for usage of NatTable for bulkeditor

Added by Katja Luther over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Priority14
Assignee:
Patrick Plitzner
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
normal

Description

  • editable cell content/possibility to copy from a cell content
  • size of the columns should not be 50/50, but depending on the content length (percentage not absolute values)
  • better symbols for target/candidates of deduplication. Additionally offering tooltips saying that a row is target or candidate for deduplication.

Related issues

Copied from EDIT - feature request #7439: Use NatTable for BulkEditorClosedPatrick Plitzner

Actions
Copied to EDIT - feature request #7659: Implement algorithm to optimize initial column size in NAT tablesNewKatja Luther

Actions
Copied to EDIT - feature request #7660: Indicate the row state in a NAT table via symbolsClosedPatrick Plitzner

Actions
Actions #1

Updated by Katja Luther over 5 years ago

Actions #2

Updated by Patrick Plitzner over 5 years ago

  • Description updated (diff)
Actions #3

Updated by Patrick Plitzner over 5 years ago

  • Status changed from New to In Progress
Actions #4

Updated by Patrick Plitzner over 5 years ago

  • Description updated (diff)
  • Status changed from In Progress to Resolved
  • Assignee changed from Patrick Plitzner to Andreas Müller
  • % Done changed from 0 to 50
Actions #5

Updated by Andreas Müller over 5 years ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Patrick Plitzner
  • possibility to copy from a cell content

    • this works now except for the fact that in editing mode the right click menu does not look very nice. But this is a general issue for such fields. A user defined menu would be better
  • size of the rows should not be 50/50, but depending on the content length (percentage not absolute values)

    • now percentage is used and the chosen percentage is reasonable for many use cases. However, the percentage does not yet depend on real content length which might become an important issue once multiple columns are shown. So we should try to implement this.
    • minor issue: the number column is too large now, it takes at least 20% of the size but usually needs only very little space if search result is <1000 records
  • better symbols for target/candidates of deduplication:

    • coloring of the rows works generally fine, the only open issue is that if a row is selected the the row is blue (color for selection), this makes it impossible to see what the deduplication state is. This is an issue because usually when you change the state of a row it is selected, so you can not see immediately if your action was successful. You have to change selection first which is annoying. Don't know what the best solution is. We could either try to additionally add a symbol row or have additional colors for selected targets and selected candidates
    • minor issue: colors look like in the 90th, can we use more modern colors?
Actions #6

Updated by Andreas Müller over 5 years ago

By the way, once we have >3 columns we will need horizontal scrolling anyway. So maybe this can already be implemented and the algorithm could include a decision when to make the scrollbar available.

Actions #7

Updated by Andreas Müller over 5 years ago

Actions #8

Updated by Andreas Müller over 5 years ago

Actions #9

Updated by Andreas Müller over 5 years ago

  • Description updated (diff)

The following comment was missing when the ticket was copied from #7439: "Additionally offering tooltips saying that a row is target or candidate for deduplication."

I added it to the ticket description. Still needs to be implemented if possible.

Actions #10

Updated by Andreas Müller over 5 years ago

  • Description updated (diff)
Actions #11

Updated by Patrick Plitzner over 5 years ago

Andreas Müller wrote:

The following comment was missing when the ticket was copied from #7439: "Additionally offering tooltips saying that a row is target or candidate for deduplication."

I added it to the ticket description. Still needs to be implemented if possible.

The tooltips are already implemented and should work

Actions #12

Updated by Patrick Plitzner over 5 years ago

possibility to copy from a cell content: On linux the context menu does not exist at all but CTRL+C works. I think that this is enough. Do you think it is necessary to add a user defined menu? I would guess that it will conflict with the OS context menu for text fields so this would not be easily fixed.

size of the rows should not be 50/50, but depending on the content length (percentage not absolute values): I don't understand what you mean with 50/50. Do you want different row size so that we can show line breaks?

However, the percentage does not yet depend on real content length: I tried auto adjusting the column size depending on the content but if you have one very large entity name the column would be extended to that which may lead to a lot of white space for the rest of the entries. Also, double-clicking on the column will auto adjust the size of the column. I think we can leave it like this and think about it when we add more columns in #7502

the number column is too large now: this is fixed

better symbols for target/candidates of deduplication: this could either be solved by an extra column which has an icon or (as it was earlier) we add a tag to the label ([Target], [Candidate])
colors look like in the 90th: I used a little less neon colors but this is very subjective. If you have two colors in mind I can add the RGB values

once we have >3 columns we will need horizontal scrolling anyway: horizontal scrolling should now happen when resizing the first/entity column

Actions #13

Updated by Patrick Plitzner over 5 years ago

  • Status changed from Feedback to Resolved
  • Assignee changed from Patrick Plitzner to Andreas Müller
Actions #14

Updated by Andreas Müller over 5 years ago

  • Description updated (diff)
Actions #15

Updated by Andreas Müller over 5 years ago

Patrick Plitzner wrote:

size of the rows should not be 50/50, but depending on the content length (percentage not absolute values): I don't understand what you mean with 50/50. Do you want different row size so that we can show line breaks?

This was an incorrect copy when the ticket was created. Of course we talk about columns here, not rows. I changed it in the description.

Actions #16

Updated by Andreas Müller over 5 years ago

Patrick Plitzner wrote:

once we have >3 columns we will need horizontal scrolling anyway: horizontal scrolling should now happen when resizing the first/entity column

Great! Works fine.

Actions #17

Updated by Andreas Müller over 5 years ago

Patrick Plitzner wrote:

colors look like in the 90th: I used a little less neon colors but this is very subjective. If you have two colors in mind I can add the RGB values

Looks better now though the yellow is a bit dirty. But don't have time to check for even better colors now.

Actions #18

Updated by Andreas Müller over 5 years ago

Patrick Plitzner wrote:

possibility to copy from a cell content: On linux the context menu does not exist at all but CTRL+C works. I think that this is enough. Do you think it is necessary to add a user defined menu? I would guess that it will conflict with the OS context menu for text fields so this would not be easily fixed.

OK, we keept it as it is for now.

Actions #19

Updated by Andreas Müller over 5 years ago

Patrick Plitzner wrote:

However, the percentage does not yet depend on real content length: I tried auto adjusting the column size depending on the content but if you have one very large entity name the column would be extended to that which may lead to a lot of white space for the rest of the entries. Also, double-clicking on the column will auto adjust the size of the column. I think we can leave it like this and think about it when we add more columns in #7502

Auto adjust is probably not the solution, but we need an algorithm to compute the first percentages. Created new ticket: #7659

Actions #20

Updated by Andreas Müller over 5 years ago

  • Description updated (diff)
Actions #21

Updated by Andreas Müller over 5 years ago

  • Copied to feature request #7659: Implement algorithm to optimize initial column size in NAT tables added
Actions #22

Updated by Andreas Müller over 5 years ago

Actions #23

Updated by Andreas Müller over 5 years ago

Patrick Plitzner wrote:

better symbols for target/candidates of deduplication: this could either be solved by an extra column which has an icon or (as it was earlier) we add a tag to the label ([Target], [Candidate])

We should check, if the extra column works. Created new ticket for this #7660. Adding tag to label is not a solution I think as we soon want to start to allow editing the cells. Also this requires that the order of the columns is fixed (starting with label).

Actions #24

Updated by Andreas Müller over 5 years ago

  • Status changed from Resolved to Closed
  • Assignee changed from Andreas Müller to Patrick Plitzner
  • % Done changed from 50 to 100

All issues are either fixed or moved to new ticket so we can close this one.

Actions

Also available in: Atom PDF