Closed AScustomWorks closed 1 year ago
It's recommended to use the CompanyName-PluginName
pattern for slugs. https://vcvrack.com/manual/PluginDevelopmentTutorial.html under Naming.
I don't know if I'd call more plugins "clutter", it's just what happens with a popular platform, along with a database that attempts to collect every plugin.
I have no idea what you're talking about with changing the "name of the dist folder"
Also, who is using an ampersand in their slug?
1.- Right about the "clutter", I guess I need to get rid of MY clutter hehe
3.- Nobody yet I hope hehe, it was just for the example.
make clean
, make dist
-_
are allowed in slugs. They will begin to be hard requirements later.Hi Jon, and yes, that's what I was aiming for but didn't explain correctly, thanks a lot!.
I'll leave an example as a guide, please correct me if something is wrong with this approach (tested already and is working as expected):
Same dev slugs: SLUG = XYZ (first module set ) SLUG = XYZ-SET-2 (second module set) That's for each module set, and it gives 2 separate plugins to install.
Then, to keep both module sets under the same top level heading ("XYZ" in this case): On the first module set(XYZ), manufacturer name is XYZ:
p->addModel(createModel
On the second module set (XYZ-SET-2) manufacturer name is again XYZ:
p->addModel(createModel
The top level heading ends up like this: XYZ: -My Module -Set 2 Module
Now I wonder if users could be confused by not seeing "XYZ-SET-2" at the top level heading, can't win every time hehe.
I'd consider putting the set name in the model createModel call: "XYZ", "[SET-2] FunkyVCO".
Closing since the issue has been resolved by https://github.com/VCVRack/library/issues/257#issuecomment-364781142
As far as I understand the quick way is to just use a different slug for every set, for example:
But this approach is cluttering the module developers list menu already, not important when typing a search but a bit annoying when looking into developers list.
I noticed if we keep the same name slug at compile time, then manually change the name of the dist folder(to avoid replacing the first module set), any extra module set will appear under the same developer name (first set, second set, etc.). Version info may be confusing for users though.
Would this be the proper approach or there's another method contemplated?
Thanks!