You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move away from hardcoded apps when syncing projects from CGWire.
Implementation
When creating projects in CGWire, the project apps are hardcoded, which does not take advantage of the preexisting work done on application toml files.
On creating a project, reference the toml files in the bin folder and register those.
Expose metadata in CGWire
Sync metadata from CGWire to Avalon
The text was updated successfully, but these errors were encountered:
This isn't the right approach.
It's up to Avalon to provide applications available to a studio or machine, which is what the .toml files and associated .bat files do, but applications available to the user should be specified per project. This should come from CGWire, as metadata of some kind.
A discussion about metadata in CGWire has been started here
Goal
Move away from hardcoded apps when syncing projects from CGWire.
Implementation
When creating projects in CGWire, the project apps are hardcoded, which does not take advantage of the preexisting work done on application toml files.
On creating a project, reference the toml files in the
bin
folder and register those.The text was updated successfully, but these errors were encountered: