-
-
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 BB to Pattern #6284
Rename BB to Pattern #6284
Conversation
Beat+Bassline Editor -> Pattern Editor BB* -> Pattern* BeatClip -> PatternClip Does not touch DataFile
🤖 Hey, I'm @LmmsBot from github.com/lmms/bot and I made downloads for this pull request, click me to make them magically appear! 🎩
Linux
Windows
macOS🤖{"platform_name_to_artifacts": {"Linux": [{"artifact": {"title": {"title": "(AppImage)", "platform_name": "Linux"}, "link": {"link": "https://15698-15778896-gh.circle-artifacts.com/0/lmms-1.3.0-alpha.1.179%2Bg20ec55ad0-linux-x86_64.AppImage"}}, "build_link": "https://circleci.com/gh/LMMS/lmms/15698?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link"}], "Windows": [{"artifact": {"title": {"title": "32-bit", "platform_name": "Windows"}, "link": {"link": "https://15699-15778896-gh.circle-artifacts.com/0/lmms-1.3.0-alpha.1.179%2Bg20ec55ad0-mingw-win32.exe"}}, "build_link": "https://circleci.com/gh/LMMS/lmms/15699?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link"}, {"artifact": {"title": {"title": "64-bit", "platform_name": "Windows"}, "link": {"link": "https://15702-15778896-gh.circle-artifacts.com/0/lmms-1.3.0-alpha.1.179%2Bg20ec55ad0-mingw-win64.exe"}}, "build_link": "https://circleci.com/gh/LMMS/lmms/15702?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link"}, {"artifact": {"title": {"title": "32-bit", "platform_name": "Windows"}, "link": {"link": "https://ci.appveyor.com/api/buildjobs/7ppgsh4ioa39hoh6/artifacts/build/lmms-1.3.0-alpha-msvc2017-win32.exe"}}, "build_link": "https://ci.appveyor.com/project/Lukas-W/lmms/builds/42550563"}, {"artifact": {"title": {"title": "64-bit", "platform_name": "Windows"}, "link": {"link": "https://ci.appveyor.com/api/buildjobs/qci0abddwjrhfawj/artifacts/build/lmms-1.3.0-alpha-msvc2017-win64.exe"}}, "build_link": "https://ci.appveyor.com/project/Lukas-W/lmms/builds/42550563"}], "macOS": [{"artifact": {"title": {"title": "", "platform_name": "macOS"}, "link": {"link": "https://15701-15778896-gh.circle-artifacts.com/0/lmms-1.3.0-alpha.1.179%2Bg20ec55ad0-mac10.14.dmg"}}, "build_link": "https://circleci.com/gh/LMMS/lmms/15701?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link"}]}, "commit_sha": "7864f9a22cf1597c05b2efd47057e80194ad67e2"} |
Is there a better name we could give to It's confusing since it can never contain a If possible the name should indicate that there is only one
|
@allejok96 Why not |
Or just |
I find But I think, to make the inheritation more clear, it should still be named Btw, can you please draw that image as ASCII art into the header of the track container? |
Looks like a table to me, maybe |
We are removing the term Song Editor edits the Or |
Forgive my endless naming issue. I think I have made up my mind now. Let's hear what you say. I loved So what about
For reasons why this is a issue in the first place, see this terrible infographic: Why not make inheritance more clear in the name?Well, since we are thinking in terms of "patterns" and pattern isn't even an object, I think putting the focus on tracks makes it more confusing. Makes you wonder: where is the Pattern? With a nice fuzzy name it looks good in the code and then we put that ASCII art in there so when you look it up you'll get a better grip. Besides, |
I, personally, agree to all you said in the last post. One minor question: If there would be a second PatternTrack in the Song (left side in your image), it would link to the same PatternCollection, correct? |
Another possibility is |
I like |
Yes, same PatternCollection, different index/pattern/column. |
Did a super rudimentary review (only cpp, h, and txt files; only side-by-side comparisons). Haven't reviewed BBTrackContainer changes yet since GitHub's diff failed to show them side to side, but didn't find anything obviously wrong elsewhere (aside from the TODO'd data file upgrade). |
Co-authored-by: Spekular <[email protected]>
Co-authored-by: Spekular <[email protected]>
Thanks for the fixup. How should we advance? 2nd review? Merge? Extend? |
At least someone should glance over the changes of |
@allejok96 |
Another thing I'm just noticing: If "pattern" == "bb track", then "pattern tracks" means "bb track tracks", right? So "pattern track" should nowhere be used? |
I don't think pattern = bb track though. Aren't the contents of the BB editor a pattern, and then pattern clips are placed on pattern tracks in order to loop that pattern as part of the song? |
This is the correct understanding. @JohannesLorenz I may have created confusing with the drawings in this discussion, but I hope there is no misleading comments in the code? |
Oh, right, there are patterns and pattern tracks...
Thanks for your explanations. Will continue to review. |
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.
Just a few minor/easy comments. Aside from that, very clear PR 👍
|
@allejok96 You describe |
@JohannesLorenz yes. The "reference" is returned by (renamed) Afaik it comes from a map of |
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.
Rework is OK.
The only thing that might (optionally) be worth adding in PatternStore.h is what you mean with columns. I didn't understand that you can select the column by using that combo box from the editor.
Next step is testing before we merge.
Thinking about what needs to be tested...
Is that everything? @allejok96 Also, in case you don't have merge access rights, feel free to formulate a commit message that I can put into the squash-merge. |
That's about it. DnD untouched. Test usability of pattern-things. Check that no icons are missing or that anything looks weird (CSS). |
Oh man I just realized something
They should be PatternEditorWindow and PatternEditor |
Agreeing. Shouldn't be too difficult to just rename two classes. @Spekular , any objections? |
|
I'd say yes (and in |
No objection! |
Three new commits:
|
I think it's ready, finally.
|
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.
LGTM
Branch is opened for testing. The following should be tested:
|
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.
Tested a few time and it seems to work great on my windows64 build, patterns save and load, extend, everything functions and looks good as far as I can tell 🎉
Here goes nothing (updated Jan 22)
BB*
->Pattern*
BBTrackContainer
->PatternStore
PatternStore
is with some ASCII artNotable other changes:
static_cast
PatternEditor.cpp
line 89: I took the liberty of changing the tooltip "Add Beat/Bassline" to "New pattern".PatternEditor::removePatternView()
.PatternStoreView::removePatternView()
->removeViewsForPattern()
TODO:
DataFile.cpp
;)For an easier view of the diff:
git diff -M40 --color-words='\w'