Search the Community
Showing results for tags 'widgets'.
Found 2 results
-
Hey, We're looking to get some better integrations with ftrack into our own offline interfaces of our pipeline. At this moment we're working off of a great foundation in the studio with an explorer (browser), asset loader, app launcher and lots of other tools. The intentions now are to mix these up with ftrack, like pull thumbnails from ftrack and push information to ftrack upon publishes, etc. As such I'm wondering what way we should go about this. Widgets Would we be designing our own Widgets using the API completely from scratch? Or can we use widgets from connect in our own interfaces? Are the widgets in connect intended to be used that way? Things that would potentially make it easy to display thumbnails of an asset (or other information)? Connect Would the integrations require a running connect? Or when would we use it specifically? Integrating ftrack into our tools What's the best way to go about this? Any tips from the community are also very welcome! It would be great to have informational up-to-date widgets that are all built to be smoothly cached internally. Yet at this stage it's hard to see if I'm building from the ground up or if there are elements I can connect together to get up and running faster (and even share back?)
-
I've created about 10 sub widgets within the "Insights Top" widget and I need to reformat my dashboard from three column to two. Being able to save those somehow to then easily load them again would be nice. Having to rebuild them all is a pain. Thanks.
