-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Importer UI overhaul #1685
Importer UI overhaul #1685
Conversation
- Add ANSI styles, colors and background-colors - Modify colorize functions to adopt new colors - Modify default configuration to adopt new color scheme: - Define colors by arrays with their ANSI codes as strings - Deprecated DARK_COLORS and LIGHT_COLORS
for easy indentation and alignment
- when linebreaking, ANSI codes should end at word borders - this removes change markers for whitespace!
- colors arbitrary strings according to a distance - refactor dest_string
- more concise format
- reintroduce support for legacy colors - replace DARK_COLORS and LIGHT_COLORS with LEGACY_COLORS and map color names onto their counterpart in the new “advanced” color definition system - also continue to support new “advanced” colors - cleaner code (at least I think so)
Hi! This was looking pretty close to ready for beta-level publicity. Shall we regroup and finish it off? Maybe we should start by making a to-do list of outstanding changes. |
I’m very sorry for the long silence from my side – I had a busy November and December and am currently in my exam period… I hope to be able to help with this again in 1-2 weeks. From what I immediately remember, the dirty code I hastily hacked together worked okayish, but was severely lacking in quality, simplicity, documentation, and tests. And I am sure that the new UI is not showing changes for some tags, eg. track length, or when the chroma id didn’t match. |
Fantastic! And no problem whatsoever—open-source hacking necessarily has to take second place behind exams. Thanks for keeping it in mind, and no rush at all. I'll let you take the lead, but I'm happy to pitch in with code quality and such. |
And maybe I can help out with some testing. I have been using these modifications for a large tagging job, and it worked nicely. As it is now, it's already a huge improvement. |
Awesome! Yes, testing is great. Please do post if you run into any problems. Adjusting the unit tests for the new UI would be helpful too. |
I have a few new commits over at mxmerz/ui. The “old” color definitions with a single string should work again. I tried to refactor the In |
Great! This looks like solid progress. I sent you an invitation to join the @beetbox organization, which should let you merge your changes into the And while |
- move construction of lhs and rhs dicts to make_line - move make_track_titles, make_track_numbers, and make_track_lengths to make_line
- add 'changed' key to info dict to indicate whether rhs should be displayed at all
For the colorize problem, you could subclass or composite |
Create color mapper functions outside of the forloop.
Instead of sometimes moving the last word in the last line, just always add an empty line as the new last line.
The class should make it easier to handle state when showing a change. - Move show_match_header and show_match_details to the new class.
Anything else that needs to be done here? |
I think what this needs is some good old fashioned TLC—taking some time to review everything in detail and think carefully about the changes. I think the outcome (i.e., the resulting UI) already looks awesome. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is mxmerz/ui, pulled into the main tree. See screenshots and such at #1593.