cables DocumentationHow To UseWorking with filesKeyboard ShortcutsUser Interface WalkthroughBeginner TutorialBeginner 1: Drawing A CircleBeginner 2: TransformationsBeginner 3: ColorMore TransformationsIntermediateImage CompositionsPost-Processing 3D ScenesEditor ToolsTimeline Keyframe AnimationExporting And EmbeddingHow to serve files externally and fix CORS headersExporting PatchesExport using the cables command line interfaceExport via IframeExport creating a standalone executableExport to github (pages)Export to run headless patchesExport and deploy to netlifyExport full PatchHTML ExportExternal triggers / functionsUsing variablesPreviewing / uploading exported cables patchesExamples for EmbeddingImporting patchesBackupsPermissionsUsersPatchesTeamsOpsMultiplayerPatchlistsCoding OpsUsing Op AttachmentsGeneral op/Port CallbacksPortsMultiPortsArray PortsBoolean portsInteger Number PortsObject PortsString portsTrigger PortsFloating Point Number PortsGUI/UI attributesHello Op - Part 1LibrariesDeveloping OpsRenaming / Creating a new versionCreating Viz OpsGuidelinesObject PortsPatching Ops / SubPatchOpsWriting ShadersWeb Audio Op DevelopmentDeveloping CablesRepositoriesSet up local environmentScriptsHow to work with forksGenerated DocumentationUsing standalone to develop cablesCables StandaloneGeneralCoding OpsSharing opsUsing NPMImport/ExportFAQStandalone - Commandline OptionsCommandline / CLIcables-cliHeadless patchesLightingLightsShadowsWorking With AudioBasic Audio SetupWorking with EffectsReal-Time Audio Analysis & Audio VisualizationOffline Audio Visualization & AnalysisCommunicationCables APIOptimizing Performance In PatchesTools for debugging your patchHow to optimize cables patches with the Performance opHow to optimize cables patches with the ProfilerCommon pitfalls with the "usual suspects"Optimizing arraysDebugging Shaders with ShaderInfoFAQAudio in web browsersHow to make demoscene demos with cables.glEmbeddingHow to integrate my cables patch into my CMS (webflow/wix/squarespace/...)?How to remove grey rectangles on touch (mobile)?Why doesn't the DownloadTexture op work on iOS?How to disable page scrolling on mobile?Mobile tipsHow to use my patch in React / VueHow to run exported patches on your local machineTransparent CanvasHow to integrate a patch into WordpressFeatures and SupportHow to contribute code to cablesWill there be support for (animated) GIFs?Can i use a website as a texture?Screenshots and Video recordingHow to report a bug in cablesHow can I share a patch to get help?How can I support cables?Video playback in cablesGeneral questionsWhat is dev.cables.glHTML And CSS In CablesJavascript Frameworkscordova / phonegapelectronreactvuejsLicenses and paymentWhat license do i need to use cables?Will I have to pay for it in the future?How is my work licensed when using cables?Does cables support midi and OSC?Patch PermissionsMy User Profile & Social MediaShadertoyCables at schools and universitiesTechnical questionsWebGL1 and WebGL2

Coding Ops

Cables standalone comes with all the ops on cables.gl, all the extensions and a few more special ops that only work when using the standalone version.

You can use cables standalone to code your own ops. A few concepts are slightly different from how things work in the browser and on the web. Here is what's different:

Op directories

One big difference to how things work on cables.gl is, that you can have ops from different sources on your hard disk.

You can individually pick different directories, collections of ops and their code, cables will then load the relevant ops for your.

Op directories, once added, are shared between all projects on your machine. Every patch also has an individual op directory (./ops) which is located next to the project file.

op dir

All the ops in the directories are sorted into a hierarchy, should they have the same name or id, the op in the "topmost" directory wins.

This way you can easily override (for example) core-ops with your own implementation, swap out collections of ops with the ones from your colleagues or try out new operators real quick.

You can re-order the hierarchy in the "Manage Op Directories"-tab:

manage_dirs

Newly created ops will always land in the "topmost" directory in that list. You can pick a different destination folder while creating a new op.

Using an external editor

Every op that you use in a standalone project registers a listener in the file system to listen for changes. If you open the op's JavaScript file in any external editor you can edit the code and see the changes reflect immediately. To get to the op's directory quickly, click on the folder-icon in the "Manage Op"-tab.

op dir


Found a problem? Edit this file on github and contribute to cables!