Skip to content
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

BassBooster Redesign #2988

Merged
merged 1 commit into from
Aug 21, 2016
Merged

BassBooster Redesign #2988

merged 1 commit into from
Aug 21, 2016

Conversation

Umcaruje
Copy link
Member

Per #2978 and #2831

Screenshot:
screenshot from 2016-08-20 15 10 26

@RebeccaDeField

@RebeccaDeField RebeccaDeField mentioned this pull request Aug 20, 2016
14 tasks
@Umcaruje Umcaruje merged commit 6e1e632 into LMMS:master Aug 21, 2016
@tresf
Copy link
Member

tresf commented Aug 21, 2016

This is already merged but may also be a good time to standardize the way these are displayed, e.g Stereo<space>Matrix vs. Bass<no space>Booster

@grejppi
Copy link
Contributor

grejppi commented Aug 21, 2016

👍 for Bass Booster

@Umcaruje
Copy link
Member Author

Sorry if I merged too quickly, it was a pretty straightforward design change, and Rebecca +1'd it.

I agree on standardizing the plugin names, and Give my vote to Bass Booster.

We also ought to consider standardising the plugin folder names. e.g. CamelCase vs snake_case: LadspaEffect vs ladspa_browser

I'd vote for CamelCase, to be consistent with the rest of the software.

@simonvanderveldt
Copy link
Contributor

@Umcaruje is the plugin name standardisation still something you/LMMS wants to do?

Because that should be a relatively straightforward change that I could create a PR for to get my feet wet with the code :)

@Umcaruje
Copy link
Member Author

Umcaruje commented Sep 27, 2016

@Umcaruje is the plugin name standardisation still something you/LMMS wants to do?

Because that should be a relatively straightforward change that I could create a PR for to get my feet wet with the code :)

@simonvanderveldt Yeah, its something desirable, so if you're up to it, that would be helpful. Note that if you also want to standardize the folder names too, you'll need to write a project upgrade procedure, which should probably be straightforward.

That, said, welcome aboard, all help is really appreciated, also if you have some problems, don't be afraid to ask 😄

@simonvanderveldt simonvanderveldt mentioned this pull request Sep 27, 2016
14 tasks
@simonvanderveldt
Copy link
Contributor

@simonvanderveldt Yeah, its something desirable, so if you're up to it, that would be helpful. Note that if you also want to standardize the folder names too, you'll need to write a project upgrade procedure, which should probably be straightforward.

Perfect, I've created #3055 to track this.
I'll have to see about the folder names and migration, not sure if I'm up for that already ;)

That, said, welcome aboard, all help is really appreciated, also if you have some problems, don't be afraid to ask 😄

Thanks! Happy to help! :)
I'll probably drop by on IRC with some questions.

@Umcaruje
Copy link
Member Author

Thanks! Happy to help! :)
I'll probably drop by on IRC with some questions.

Well, I mostly hang out on our discord server, which I find more usable than IRC because you can share images and have code snippets: https://discord.gg/5kSc32Z

sdasda7777 pushed a commit to sdasda7777/lmms that referenced this pull request Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants