This article will guide you through the process of creating and publishing your own library.
Here’s a little secret: libraries and projects in XOD have no technical difference. The distinction is conventional. Your project becomes a library when you decide that it is.
To start a new library, hit “File → New Project.”
Make the nodes you want to be in the library like you would do for any project.
Documenting the nodes you’re going to share is extremely important for libraries. A lack of short descriptions for nodes and their pins will very likely ruin your effort and make the library unusable to others.
The obvious step is to test your nodes in action before sharing them. One of the possible ways to do so is by creating several example patches. They are regular patches with a conventional
-example suffix in their name like
On such patch, place the node to be tested and use the most basic input/output facilities: watches, constants, LEDs, pots, and buttons. Having done that, you focus on the node under the test. Upload the patch to verify that the node works as expected. Later, any xoder can view and upload the same example as well to learn how the node works.
To publish a library, you are required to set several project-level fields. All of them are accessible through the “Edit → Project Preferences” dialog.
The library will be available to others under the
The semver tag for
the upcoming publication. If you're about to publish a library for the
first time, as a rule of thumb, start with
|Description||One- or two-tweet-long description for your library. It is shown on https://xod.io/libs/ and inside XOD IDE.|
When ready, hit “File → Publish Library.” Review the proposed effects and click “Publish.”
To use a library you’ve published already in any other project, think of it as of a third-party library. That is, hit “File → Add Library” and install own library, just like anyone else would do.
If you have published a larger-than-trivial library, you will likely want to release an update for it sooner or later. To do so:
A special note on updating the version field: You are not allowed to re-publish the same version as any you have posted before. The version number must be bumped. The best practice is to follow the semver convention:
Once the new version is published, to make it visible to your other projects, update the local installation of your own library by hitting “File → Add Library” again.