manifest.xml categories

I’m sure I’ve seen this come up somewhere before but I couldn’t find it through a search of the forum so sorry if this is a duplicate discussion.

Within the manifest.xml you are to set a Category for the Tool. Is there is a fixed list of categories we should chose from? Or at least a list of suggested ones to try and find a match (before creating your own if you truly feel none are suitable)? If not maybe it could be an idea to include one somewhere obvious.

On that note I feel an addition to the API documentation on what has to go into the manifest.xml would be a good idea.

Line 253-255 of !Introduction.txt file in the docs:
For a detailed description of the bundle layout and the main.lua,
manifest.lua specifications, have a look at the “com.renoise.Example.xrnx”
tool please.

Note the manifest.lua typo.

It also doesn’t state that this is not included as default but you have to download the Starter Pack. And I didn’t know until just now you can drag and drop a folder onto Renoise if it has the full tool name (IE ends in .xrnx like a tool does) so was a little surprised to see the packaged tools as folders. It works though :)

So from the Example Tool:

<!-- Separate multiple categories with commas. Never knew you could include multiple entries, so that's good to know. But still some commonly used entries would be nice. Are these used by the Tools site for putting different Tools in the right Categories for easy finding? In short: I think the details within the mainifest.xml of the ExampleTool should be included as a standard API document. Some basic Categories for people to chose from would be good to help people use the same categories as each other.
  • thousand

On a related note (well to do with manifest.xml)…

Is there a length limit for the Description field? Having this in the field causes it to throw an error (and it’s really not long!)

Wasn’t size. Must have been some invisible character somewhere near the beginning. I deleted sections of the text until it would work and ended up rephrasing it…

the & is my guess…

I have to admit I do not use this tool, hence some recommended (not a definitive list obviously) within the example manifest.xml could be useful to some.

Plus I still do think it should be included with the Documentation, rather than only as part of the Example Tool, which is a separate download.