What's Changed

What's Changed

What's changed from Toolkit classic to the new Zero Configuration integrations.

With the new Shotgun Integrations, we've introduced a concept called zero-config. Without having to set up any configuration files, you'll have access to the Shotgun Panel, Publisher, and Loader apps in commonly used software packages. And if you want to go deeper, all the existing Toolkit configuration functionality is still available.

In addition to this simpler setup, we've done a lot of cleaning up and revamping throughout the Toolkit codebase. Here are some of the things that have changed:

  • Every project will have a default set of integrations – both via Desktop and in Shotgun context menus – available off the bat, with no extra setup.
  • With the zero-config setup, Shotgun Integrations no longer deal with folder structure and filenaming for your work files and publishes. There are no templates to maintain, and there is no filesystem schema.
  • Instead: For work files, zero-config uses your host app’s native Project setup. For example, if you set up a Maya Project, you’ll just use Maya’s File Open/File Save commands, and your files will be saved according to your Project settings. Publishes can be discovered in Project locations, or dragged in from arbitrary locations. You can also write Collector functions, where you dictate the logic for finding things to publish.
  • There is no more Workfiles app. You just use your host application’s native File Open/File Save commands for file management. (Note again, that this is if you go with the zero-config setup. You can choose to bring the Workfiles app, and templates and schemas, back into your workflow.)
  • Set work area in the Shotgun Panel: In the absence of Workfiles, there's no way for Shotgun to know what entity to associate Publishes and Loads with, unless you've launched from an entity's context menu in Shotgun. We've added a button within the Panel where you can set your work area.
  • The Software entity: With no Pipeline Configuration, there’s no paths.yml or app_launchers.yml (imagine!). With the new Software entity, you can manage paths to software packages, restrict visibility to specific users, groups, or projects, manage versions, and group applications within the Desktop app, all from within Shotgun itself.
  • We’ve added a descriptor field to our Pipeline Configurations entity. So if you are using full Toolkit integration, you can manage Pipeline Configurations right in Shotgun, even for remote workers. (do i need to mention cloud-held configs?)
  • A new and improved Publisher! We’ve redesigned the Publisher from the ground up. In addition to running it from host apps, you can now run it standalone, straight from Desktop, and drag in arbitrary files to publish.
  • We’ve revamped Desktop’s websockets setup, which means lots of improvements for browser integration. We've got better menu organization in the web app, general speed enhancements due to a more robust caching mechanism, and we've added a browser_integration core hook, which allows for customization of some portions of the workflow. Note that as a byproduct of this revamp, you will need to be logged into a site in Desktop in order for browser integration to work.

Tell the doc gen system that we don't want a table of contents by adding this special markup: TANK_NO_TOC



Article is closed for comments.