MusicBee plugins & extensions repository

[hiccup]

also, you group MB extensions by their "purpose" rather than by "the way of implementation".

What is your specific suggestion for improvement?

[boroda]

NO, i meant already existing neighborhood! do not move its description elsewhere!

P.S. i think it's worth to add these 2 links by sveakul to your description (because the visualizer add-on page (that you referred in the description) doesn't have links to the forum topic, and visualizer installation is not very obvious):

Visualizer thread

Installation instructions

[hiccup]

P.S. i think it's worth to add these 2 links by sveakul to your description (because the visualizer add-on page (that you referred in the description) doesn't have links to the forum topic, and visualizer installation is not very obvious):

In my opinion it is the responsibility of the creator of a plugin to provide clear instructions, explanations and links.
I don't want to clutter up the tables and/or put in more effort only because the creator of a plugin has been lackluster in providing adequate information.
So I think it's best to either come up with very specific suggestions to improve the link that is currently provided in the table, and/or provide very specific suggestions for the description of the plugin, or else post further opinions and suggestions in the forum thread of this plugin. (if it even exists)

[boroda]

leave description itself as is. just replace "extension link" by:

https://getmusicbee.com/forum/index.php?topic=23345.msg206731#msg206731

this post provides all required information and download link.

[hiccup]

leave description itself as is. just replace "extension link" by:
https://getmusicbee.com/forum/index.php?topic=23345.msg206731#msg206731
this post provides all required information and download link.

I would prefer to leave the link to lead to the official plugin page.

Perhaps a mod (or raul himself) can add the forum link that you are recommending to the plugins main page?
https://getmusicbee.com/addons/visualizer/368/classic-spectrum-analyzer/

[boroda]

i'm afraid he was absent om the forum for a long time. this is the only problem.

[boroda]

@hiccup, i've uploaded this plugin to add-on section of the site. please consider including it to your add-ons table. it seems very useful for filename encoding.

[hiccup]

@hiccup, i've uploaded this plugin to add-on section of the site.

Thanks boroda!
it's added

and click on the plugin creator's name, and 'like' what you see/hear?

[Mayibongwe]

When this repository was setup,
I thought about asking you to include a column that specified whether or not a plugin was open source, but had immediately decided that it wouldn't be a fair request.
So just now, I thought there might be an even easier way where plugin authors added a tag to their add-on to specify that it's open_source.

https://getmusicbee.com/addons/s/?q=open_source&type=2

But in any case, pretty much everything with a github link on this thread is open source if I'm not mistaken. So the above is probably not even worth the exercise for developers.

[hiccup]

When this repository was setup,
I thought about asking you to include a column that specified whether or not a plugin was open source, but had immediately decided that it wouldn't be a fair request.

It's not a bad idea, but it's not something I think important or relevant enough to add to this particular table.
It's already a challenge to present this kind of information nice and compact in a forum post, and I'm not really looking to add complications.
Also because (even though I have shared the login info for 'MusicBorg' with several other forum members) until now it's only me that is maintaining this table.
(not blaming others about that at all, since the BBCode stuff involved isn't very easy or much fun to edit at all)

As you suggested, perhaps it would be easier to implement something for it on MusicBee's plugin website page,
That may be have some sort of database like foundation that could be used for it.
But I have no idea (nor an opinion) on that.

I'm curious: What is the reason for you thinking about this, and what would be the benefit of having something like this?
 

[boroda]

agreed with hiccup that it's not something what should be added to the tables on this topic.

though, this tag can be really useful for beginners starting plugin development to look for some example code.

p.s. i've added this tag to AT&RT plugin, and will add it to my other plugins later (for the reason i described above).

[Mayibongwe]

#1   agreed with hiccup that it's not something what should be added to the tables on this topic.
#2   though, this tag can be really useful for beginners starting plugin development to look for some example code.

Yep, was about to reply with #2.
First time I thought about it was when this topic came up: https://getmusicbee.com/forum/index.php?topic=40359.msg218753#msg218753
Second and most-recent having been the edit section here: https://getmusicbee.com/forum/index.php?topic=41818.msg227903#msg227903

When I first started looking into the MB API, I managed to find my way around thanks to the AT&RT plugin.
It's the one plugin where anybody starting their quest on this will easily find posts mentioning that it's open source.
But with the complexity involved, years of development, and hundreds of code blocks behind it, it's not the easiest to navigate nowadays for somebody starting out.

Edit:
So I thought with one lookup location, other users may find alternative plugins with simple code to help them with the first steps.
I should mention that Steven's test_plugins that come bundled with the interface file already do an excellent job on this.
Having that one place with multiple examples of how to use the functions is just a bonus. But yes, I agree that it's overkill for this repository above.

[hiccup]

But with the complexity involved, years of development, and hundreds of code blocks behind it, it's not the easiest to navigate nowadays for somebody starting out.

A Tips & Tricks topic like 'how to start creating a MusicBee plugin' comes to mind for something like that?
It wouldn't need to be a 10.000 words tutorial, but it could contain some links and pointers on where to look and how to begin?

[Mayibongwe]

But with the complexity involved, years of development, and hundreds of code blocks behind it, it's not the easiest to navigate nowadays for somebody starting out.

A Tips & Tricks topic like 'how to start creating a MusicBee plugin' comes to mind for something like that?
It wouldn't need to be a 10.000 words tutorial, but it could contain some links and pointers on where to look and how to begin?

Yep, that ought to do it too - added to one of my future projects if no one gets to it before me.

[hiccup]

Yep, that ought to do it too - added to one of my future projects if no one gets to it before me.

If you get to that, I got you covered.