-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Rename TCO and related to Clip #6226
Conversation
🤖 Hey, I'm @LmmsBot from github.com/lmms/bot and I made downloads for this pull request, click me to make them magically appear! 🎩
Windows
🤖{"platform_name_to_artifacts": {"Windows": [{"artifact": {"title": {"title": "32-bit", "platform_name": "Windows"}, "link": {"link": "https://ci.appveyor.com/api/buildjobs/360d3o9twib9n5n3/artifacts/build/lmms-1.3.0-alpha-msvc2017-win32.exe"}}, "build_link": "https://ci.appveyor.com/project/Lukas-W/lmms/builds/42135894"}, {"artifact": {"title": {"title": "64-bit", "platform_name": "Windows"}, "link": {"link": "https://ci.appveyor.com/api/buildjobs/ao20uxtxxaah3mo0/artifacts/build/lmms-1.3.0-alpha-msvc2017-win64.exe"}}, "build_link": "https://ci.appveyor.com/project/Lukas-W/lmms/builds/42135894"}]}, "commit_sha": "dd2e4ea60d9abc5da96e020a5911729f156d1158"} |
Thanks for your contribution. Is this ready to review? |
It is mostly ready for review, except that the locales are pending. Should we leave the locales for another PR? |
I don't know what you mean by locales. Will changing those locales cause many conflicts for other PRs? |
I asked in our Discord, but got no answer. I'm not sure if this can/must be done here or in Transifex. I wish anyone could help here... |
Since we've now got an answer...
... this PR can either be merged, or updated to upgrade the locales as well, correct? |
I'd say let's upgrade this PR (if @M374LX has time). And then, a review will be required. |
@Spekular It is possibly not appropriate to replace every single occurrence of "pattern" with "clip" on the locales, which means that simply running I plan to check this in the next days. |
I think the task of updating the locales should be left for someone with more experience on Transifex. Update: I am going to update the locales directly just in case (done on fffa09b). |
OK, but what is left to do on Transifex then? |
Possibly just update the line numbers on the locale files in case Transifex has this ability. |
Update which line numbers? You didn't change line number in fffa09b, did you? |
No line numbers have been changed by fffa09b, but some line number references on the locale files are outdated due to previous changes (not necessarily from this PR) that caused |
Somehow, |
|
I'll review this. What's the intended scope? I guess it's point 1-3 from the reorg point, so:
And renaming BB to Pattern is not done yet because the PR blocks itself (i.e. there will be a following PR). Is this all correct? |
That is all correct, @JohannesLorenz. |
I just see that the locales still contain Edit: Now I see that the code contains them, too. Wanted? |
TrackContentWidget has not been renamed. It refers to the area on which clips (previously track content objects) are shown. Unless someone suggests a better name, I would say it is wanted. c5f17bf fixes two small oversights in comments. |
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.
Review finished. I added comments to the code. Despite from those comments:
- Some remaining "Pattern" are left. They are shown using
git grep -i pattern
. I see that in at least in 3 Plugins. Not all might be pattern in sense of "clip", but at least, in "plugins/MidiExport/MidiExport.h", I guesswriteBBPattern
should be changed. - The Wiki should be checked for TCO and others, too (submodule in doc/wiki).
@M374LX Looks like you resolved all my comments. Should I re-review already, or still wait? |
No problem in reviewing the code again, but I have not yet reviewed the remaining occurrences of "pattern" with |
Oh, OK. I'll wait. Let me know when you're through with everything. |
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 your time! Only 4 quick points:
- I think you forgot to revert those occurrences of "clips" strings:
src/gui/ClipView.cpp: QDomElement clips = dataFile.content().firstChildElement( "clips" );
src/gui/widgets/TrackContentWidget.cpp: QDomElement clipParent = dataFile.content().firstChildElement( "clips" );
src/gui/widgets/TrackContentWidget.cpp: QDomElement clipParent = dataFile.content().firstChildElement( "clips" );
-
Fix pattern in HydrogenImport and MidiExport plugins? At least, plugins/HydrogenImport/HydrogenImport.cpp has it partially changed, but partially not. Is that really wanted? And plugins/MidiExport/MidiExport.h should probably treated in the same way as HydrogenImport (they are both very similar).
-
Change pattern here?
src/gui/ClipView.cpp: "elidedPatternName"?
src/gui/editors/PianoRoll.cpp: "detuningPattern"? -
Wiki: Can you please edit the files directly or push them into the submodule and submit them there?
I suggest keeping "pattern" in HydrogenImport because this is the term used by Hydrogen project files (example: https://github.com/hydrogen-music/hydrogen/blob/master/data/demo_songs/TR808kit-demo.h2song). |
Before I can review, there is still a build error. I copied this from the "appveyor" build:
Did you forget to push your wiki submodule? |
This is the message when trying to push the wiki submodule:
|
@M374LX Could you try |
@PhysSong The message disappeared after trying the suggested command. @JohannesLorenz Did it solve the problem? |
@M374LX I think you pushed to the wiki on your fork. I pushed your changes to LMMS/lmms. |
Works here. Will review it in the next days. |
Perfect. Now, we need a good commit message, so we can squash all commits into one. Proposal:
@M374LX Feel free to modify and tell me when we can squash-merge it. |
@JohannesLorenz The suggested commit message is fine. The PR is ready for merge. |
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.
This breaks two old upgrades, and lacks its own upgrade routine.
@Spekular I am going to open a new PR to fix the breakage soon. As for the lack of its own upgrade routine, it is because this PR is not intended to touch the data files (the breakage you pinpointed is a slip). |
I think this is a mistake, unless there's some benefit that I'm not seeing. IMHO data file upgrades should come with the PRs that need them, because otherwise we get commits (which are basically versions) with broken backwards compatibility.
|
Oh no, how could we oversee this! Sorry. Should we force-push-remove the merge commit in this case? It's a bit late, but seems the most clean to me. Alternatively, we should push a fix really fast. Though that does not help with your bisecting argument. |
As it is easy to fix, I see no reason for a force-push-remove. I can do the fix later today. |
Thanks. I should be able to review and merge your fixes today, too. We can still force-push later if that should ever be wanted. |
src/gui/ClipView.cpp
Outdated
m_tco->movePosition( pos ); | ||
AutomationPattern::resolveAllIDs(); | ||
TimePos pos = m_clip->startPosition(); | ||
QDomElement clips = dataFile.content().firstChildElement( "tcos" ); //TODO: rename "tcos" to "clips" |
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.
Any reason tcos
was kept here?
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.
Because the PR intends to not change anything in the Datafile?
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.
This is just a dummy datafile tho, for clipboard and drag-n-drop, should be safe... here's a better link
Line 57 in 55d361f
This breaks loading of old project bundles with sample tracks |
Or in this case, it apparently would have worked fine if the existing upgrade routines hadn't been affected: #5592 (comment) Apologies for the untested (incorrect) claims, it never occurred to me that LMMS would ignore the tag names on load. While we're on the topic, I saw a lot of lines with "tco" and one with "pattern" reintroduced in #6279, these will be changed back to "clip" in a later PR, right? (e.g. the data file upgrade PR?) |
Yes, that's the plan. |
Rebasing #6044.
Renaming "pattern" to something else on the data file is a task for another PR. Thus, this one does not touch the data file.
As in #6044, this PR does not include renaming BB to Pattern.