Library does not appear in Contributions Manager

[alexdmiller]

Describe the bug

After running deployToProcessingSketchbook and confirming that the library has been added to Processing/libraries, the new library does not appear in the Contributions Manager. However, it does appear in the Sketch > Import Library... menu:

Steps to reproduce

1. Run deployToProcessingSketchbook
2. Go to Sketch > Import Library... > Manage Libraries
3. Search for "A Template Example Library"

Expected behavior

It should appear in the list

Actual behavior

It does not appear

[SableRaf]

Hi @alexdmiller, thanks for your question!

The deployToProcessingSketchbook script adds your library locally but doesn’t list it in the Contribution Manager. The Contributions Manager only includes libraries that have been officially submitted and approved.

To have your library appear there, email contributions@processing.org with the URL to your GitHub releases page (e.g., https://github.com/{{username}}/{{repository}}/releases/).

You can find more instructions on releasing libraries here.

Let me know if you have any questions about the process! 😊

[alexdmiller]

That makes sense. I believe the documentation is wrong then. The section titled "Testing the Library Template" in the Getting Started guide says:

5. Check if the library appears in the Contribution Manager:
6. Open Processing, and click on Sketch > Import Library ... > Manage Libraries .... This opens the Contribution Manager.
7. You should see an entry named "A Template Example Library" with a check mark next to it. This is the sample library you just installed using the template.
8. If it does not appear, please check the troubleshooting guide.

If you agree, would you like me to open a PR to correct the documentation?

[SableRaf]

Hmm maybe I misspoke then 🤔 Let's see what @mingness has to say about this.

[mingness]

Looks like there is a dependence on OS on how the new library appears. Let me research this further. Thanks again for bringing this to our attention.

[mingness]

Hello @alexdmiller , thanks for your offer to provide a fix. Looking into the situation, it seems the current text of the documentation is only valid for Linux. Both Windows and Mac behave the way you've observed. Would you be willing to edit the documentation to reflect this situation? Apologies for the slow response - I hope you still have time for this.