Cloud Palette presents a collection of components and examples that you can pull to integrate into your project without needing to host them locally. The view of available components here is a representation of assets that are available from the cloud. Rather than storing elements locally on your machine, Cloud Palette's idea is that you want the ease of use to pull components from the cloud. No component represented in the tree view of Cloud Palette is local, instead, pulling a comp loads it dynamically from the web - making this ideal for quickly loading elements from the web without needing a complete store locally.
Organizing TOX files is something we've long fought with - keep them in your base repo and they get out of date. Organize them in a submodule and then you need a git strategy to keep the synced. Put them in dropbox and then you need dropbox installed on every machine. It's never been the kind of workflow we've wanted. Invio stands on a git automation that builds out TOXs to file and generates an inventory. You create a Cloud Palette Inventory with Invio which then allows you to pull TOX files directly from the cloud - always the latest, no other apps needed. Invio allows for simple structuring on your collections which generates a json file that's consumed by the Cloud Palette Component. We use Invio to create a collection that we want to use with Cloud Palette.
If you are using the TouchDesigner Dependency Manager you can add this component to your local project with a add package command.
tdm add package github.com/SudoMagicCode/td-cloud-paletteThere are several repos available on github that contain collections that can be easily added to Cloud Palette. Below is a collection of the resources that you can add easily to Cloud Palette.
| Name | Access | Description |
|---|---|---|
| SM TD Templates | 🌎 Public | A collection of starting points for networks |
| SM TD Tools | 🌎 Public | A collection of drop in tools |
| SM POP Tools | 🌎 Public | A collection of POP helpers |