bridge-plugins v1.0.0

How plugins are deployed

plugin_versions.json is the main config file that is downloaded by bridge first. This file has all the relevant information about each plugin for each platform.

The file contains following values shared by all plugins:

helpGuide : Path to the pdf help doc helpDoc : The link to the main help docs api : Bridge API link (to be removed, the helpdoc itself should have this info nnow) scriptingReference : Bridge API reference (to be removed, the helpdoc itself should have this info nnow) resourceFiles : Link to the downloaded-able resource files (to be removed, all plugins will be downloaded/updated from the export dialog) privacyPolicy : Link to policy file pluginsPath : Path to the folder to download plugins (should be removed)

For each plugin, The file contains

name : Name of the plugin displayName : Display name as displayed to the user in dropdown helpDoc : The link to the plugin help docs win-version : Version for the plugin for windows mac-version : Version for the plugin for mac linux-version : Version for the plugin for linux pluginDirectory : The directory where the compiled plugin files are stored, and uploaded. This is also used in Bridge dev mode. defaultPort : The default port value portEditable : Can the user change/specify the port copyMapsEditable : Can the user choose to copy map files when exporting showCopyMaps : Is the copy maps option visible to user showExportFolder : Is the export to a folder on machine option visible to user exportFolderEditable: Can the user change the folder value to which assets are exported externalDownload : Are the plugin files downloaded from server (will remove this) requiresDownload : Are the plugin files downloaded from server requiresInstall : Does Bridge automatically copy or install plugin files to a place on user machine supportedversions : The versions of the tool that are supported