New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pave way for table revamping, binding the table to single container #2422
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't test the design with less number of rows, indeed it was my lack of testing for the PR. I will make the changes required. |
@wetneb Fixed the design, Combining them to one container made some other function useless which were just there to adjust there orientation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be able to revamp this architecture without making any significant changes to the appearance. Can you notice the changes?
- missing grey background on odd rows
- missing cell borders in table header
- incorrect color for cell borders in table body
I might have missed others! This needs to be thoroughly tested.
Before
After
@wetneb I will fix all the design issues. With this commit I have just fixed the orientationa and alignment issues which were more observing. |
@kushthedude you are doing great! I see the simplification coming through now, and understand your strategy here. Your right that styling and alignment can be fixed. Essentially this is really a Draft Pull Request in the making :) I think a few more hours or day and you'll conquer it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for tackling this! I'd like to see the variable/class naming updated to reflect the current structure to make it less confusing for future developers. I also think more of the previous machinery can be removed.
A couple of small stylistics things which will make it easier for reviewers:
- try to resist the temptation to make non-essential changes like adding/removing blank lines. They just add noise to the diff.
- a meaningful branch name like
1312-table-refactor
, or something similar, will make it easier for developers with lots of branches to find yours
main/webapp/modules/core/scripts/views/data-table/data-table-view.js
Outdated
Show resolved
Hide resolved
main/webapp/modules/core/scripts/views/data-table/data-table-view.js
Outdated
Show resolved
Hide resolved
main/webapp/modules/core/scripts/views/data-table/data-table-view.js
Outdated
Show resolved
Hide resolved
I actually preferred UI as the main aim for this branch was to completely refactor the table section but then I came to know that current table is too loosely bounded and we have an explicit function for simple tasks like aligning header with the body etc. Hence had to refactor the method of the rendering of the table before introducing more feature in data-grid. |
@wetneb @thadguidry @tfmorris Sorry for the delay, I was having hard luck finding a nice internet but it's solved now. @wetneb Restored the styling, I can't find any change now b/w old & new table. After this, I think the next step would be to design the re-sizer which I will do in the meantime and make a PR. I will add the resizer to the table and make draggable columns later as I have mentioned it in my GSoC Timeline. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can notice the following changes:
- The font size of all text in the table has increased;
- Borders in column headers are missing (as I already mentioned in the previous review). With Chromium, there is still a vertical border between column headers, but with Firefox even those have disappeared.
If you find it hard to compare both versions, you can do this:
- run OpenRefine from the master branch and load a sample project in your browser
- stop OpenRefine and keep your project open in your browser
- start OpenRefine from your branch and load the same project in a new tab
You can now switch back and forth between the two tabs.
With this technique, differences such as the font size of table elements should be really obvious.
Before
After (Chromium)
After (Firefox)
@wetneb Done the changes : Before this (On chromium & safari)After this (On chromium & safari)I mimic firefox using safari user-agent and it was working well. Please let me know if it is still broke on firefox because I dont cant see any particular reason why the styling won't apply on firefox. |
Hi @kushthedude, I tested it out and it still does not seem to work on firefox. Before:After:Plus on chrome, its a minute detail, but the top border of the table header is not present anymore. Before:After: |
Top border is present in chrome, I think you missed seeing it. |
@kushthedude, Looking at your screenshots, this does not seem to appear in your chrome for some reason? Although, when I checked @wetneb's screenshots, it seems to persist. |
Did you mind to try out in your local ? |
@kushthedude this was unnecessary for such a very minor visual difference, but glad to see that you went the extra mile to make it exact as before. |
I am not sure what you mean by that… By this token, we don't "use" most borders. |
@wetneb UI is consistent and borders are intact in chromium and firefox too. |
There are number of commits after the @wetneb 's screenshots. There will be change, all I told you to check the PR locally and show me the css details from the console if you think there is difference of border size after this PR and before. |
@kushthedude : wow, what you are doing is impressive. Regards, Antoine. |
Thanks, @antoine2711, Once this gets merged. I will be making a PR for migration of a dialogue or a dropdown service to Vue.js to see how it actually goes. |
@wetneb Is there anything more remaining in this PR? |
@wetneb Fixed the issue with XML/JSON importers. |
main/webapp/modules/core/scripts/views/data-table/data-table-view.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The column groups are still not correctly rendered. See my latest screenshots again: you have fixed the background, but that was not the only difference! Have a good look at the orange bars. Can you notice a difference?
If you could have the initiative to test things more thoroughly on your side it would be great - it is quite time consuming to review changes like this. Thanks!
Hi Kush! |
Will wrap this up by tonight, thanks for your concern!
…On Tue, 19 May, 2020, 19:32 Lisa Chandra, ***@***.***> wrote:
Hi Kush!
Are you still working on this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2422 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKQMTLVTKPNDPEKMJ235GJTRSKGNXANCNFSM4LNFTG5A>
.
|
Hey Kush, this PR is important in order to start with the infinite scrolling project. If you don't mind, can you wrap this up faster? If you're busy, I can help as well. |
@wetneb I am currently occupied with my academic activities which may take another week to wrap up, hence closing this PR. |
That is alright, thanks a lot for all the work done so far! This PR was almost in a mergeable state so it will already help Lisa a lot :) |
@kushthedude Thank you Kush! |
Refers: #1312