About plugin ids
-
The classic IDs are for the classic API as stated in your link.
You use the new Module ID for MAXON_API plugins to register them properly.But even for legacy plugins, you are forced to use the new module id in your projectdefinition.txt. Just stick to the guidelines and you're good to go.
-
@mp5gosu said in About plugin ids:
The classic IDs are for the classic API as stated in your link.
So if I need a new plugin id, but I'm using the classic API, do I create it on the old forums?
-
Hi rsodre, thanks for pointing it out!
Whatever an plugin ID needs to be generated you have to do it on this forum at this link
Please do NOT generate plugin IDs on the old forum.
Best, Riccardo
-
@rsodre : Your old list of plugin IDs is not lost. You can contact us via mail (please include your user name in the old Plugin Café forum and one plugin ID) and we can send it to you.
-
And what is about the missing dots?
-
@Klaus I guess you are referring to something on the plugin ID page? I'm not sure, there are actually dots missing. But before we now get into a discussion, please give us some time. We will add information to the Plugin ID page some time after
DevKitchen[URL-REMOVED] (which is beginning of November) and if then there are still open questions, we will be glad to pick up discussions again.
[URL-REMOVED] @maxon: This section contained a non-resolving link which has been removed.
-
is it possible to change the listed name somehow? i accidentally typed a wrong number in the label
-
Hi ello, it's not possible to modify an entered label.
Simply create a new one with the correct label leaving the wrong one to seat in the DB with the others.
Best, Riccardo
-
@r_gigante I understand that removing or editing a plugin id could potentially bring some problems, but having them all together like this (used, not used, discarded, different products) can make a mess of a page.
Could you consider as a feature request to at least to let us group them to make our plugin ids page more organized? In my case, I would like to have one group for each product and another for discarded ids. Later on when you import the classic plugin ids from the old forums to the new interface, they could be all in one new (immutable?) group.
-
Hi Roger, thanks for your insights! Definitively a valid feature request for a future update of the plugin IDs generation page together with the option to edit the label (not the ID provided).
For the time being, the plugin responsible for generating the pluginIDs is as much simple as it was on the previous www.plugincafe.com discussion board. As first implementation we just wanted to grant the same functionality leaving for the future potential improvements.
Last but not least two notes:
- the plugin ID, as we know them, are going to be slowly replaced by reverse-domain assembled ID and in the future they will be become completely useless
- the plugin IDs stored on the previous platform will never be ported on this discussion board because users had to re-register on this platform (they where not ported due to GDPR regulation) and associating old plugin IDs to new users would have been impossible (or at least highly error-prone). You can ask, privately, to be provided with the list of the IDs associated to your old account on www.plugincafe.com by providing your old username, at least one pluginID and the associated label of it.
Best, Riccardo
-
Seems this was changed a while ago… I only had an account (and registered IDs) on the old site. Had to reregister (why?)
Anyway… this "new" plugin ID request page seems to be rather confusing. It tells me to utilize a "domain space" ("The suggested MAXON API domain space, based on your profile, is: use.yourdomain.tokai."*). OK, so I enter my label as "org.binaryriot.foo.bar" (because org.binaryriot.* would be my domain space) and I'll end up with "orgbinaryriotfoobar". Why?
Is that just a visual problem with the site (skipping dots) or did I actually just registered something I would need to use like "org.binaryriot.orgbinaryriotfoobar" now?
Couldn't it just bring an error when I enter unwanted dots into the input field rather than wildly filtering them out?
I'm usually not easily confused, but this is rather confusing.
(Note: I have no idea about that new MAXON API; I'm doing stuff with an old version of C4D and only need the numeric ID actually, so I guess I can live with a wrong label that can't be fixed in this case.)
-
All this stuff was changed with R20.
You only have to care about domain spaces if you want to register MAXON API stuff.
For old plugin IDs, you don't have to care about anything. You can enter any label you like. This is just for you.
-
Hi @tokai , nice to see you on the "new" PluginCafé
With regard to your first question:
Had to reregister (why?)
We simply could not take the credentials straight from the old forum to the new one: to say one to dismiss all the sleeping accounts that grew up over the years but also to be sure that our new users were accepting the GDPR.
With regard to your second question:
OK, so I enter my label as "org.binaryriot.foo.bar" (because org.binaryriot.* would be my domain space) and I'll end up with "orgbinaryriotfoobar". Why?
You don't have to enter it in the Label field of the Plugin ID Generation page.
As you can see there are two sections:- MAXON API suggested domain space: this is a suggested reverse-domain string that should be used by developers to be sure that the strings used for anything connected to MAXON API developement and for the
ModuleIdused in the projectdefinition.txt of their plugin is UNIQUE to them.
This string is created by looking at the Plugincafé member's information and by default it's created by assembling use.yourdomain.<username> to invite members to use non-conflicting names. But if you go into your profile settings and change the website to www.binaryriot.org you'll see that getting back to the Plugin ID generation page the suggested domain will exactly be org.binaryriot.* - Plugin ID generation: this is were you're supposed to enter, as in the old plugincafe, an arbitrary label for the plugin your creating - e.g. My Awesome Object Generator* that on pressing the "Get Plugin ID" will provide you with
Best and, once more, welcome back.
- MAXON API suggested domain space: this is a suggested reverse-domain string that should be used by developers to be sure that the strings used for anything connected to MAXON API developement and for the
