pipeline
Basic avalon integration
FusionEventHandler
Bases: QObject
Emits AYON events based on Fusion events captured in a QThread.
This will emit the following AYON events based on Fusion actions
save: Comp_Save, Comp_SaveAs open: Comp_Opened new: Comp_New
To use this you can attach it to you Qt UI so it runs in the background. E.g. >>> handler = FusionEventHandler(parent=window) >>> handler.start()
Source code in client/ayon_fusion/api/pipeline.py
376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 |
|
FusionEventThread
Bases: QThread
QThread which will periodically ping Fusion app for any events. The fusion.UIManager must be set up to be notified of events before they'll be reported by this thread, for example: fusion.UIManager.AddNotify("Comp_Save", None)
Source code in client/ayon_fusion/api/pipeline.py
338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 |
|
FusionHost
Bases: HostBase
, IWorkfileHost
, ILoadHost
, IPublishHost
Source code in client/ayon_fusion/api/pipeline.py
73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 |
|
install()
Install fusion-specific functionality of AYON.
This is where you install menus and register families, data and loaders into fusion.
It is called automatically when installing via ayon_core.pipeline.install_host(ayon_fusion.api)
See the Maya equivalent for inspiration on how to implement this.
Source code in client/ayon_fusion/api/pipeline.py
76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 |
|
imprint_container(tool, name, namespace, context, loader=None)
Imprint a Loader with metadata
Containerisation enables a tracking of version, author and origin for loaded assets.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
tool | object | The node in Fusion to imprint as container, usually a Loader. | required |
name | str | Name of resulting assembly | required |
namespace | str | Namespace under which to host container | required |
context | dict | Asset information | required |
loader | str | Name of loader used to produce this container. | None |
Returns:
Type | Description |
---|---|
None |
Source code in client/ayon_fusion/api/pipeline.py
267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 |
|
ls()
List containers from active Fusion scene
This is the host-equivalent of api.ls(), but instead of listing assets on disk, it lists assets already loaded in Fusion; once loaded they are called 'containers'
Yields:
Name | Type | Description |
---|---|---|
dict | container |
Source code in client/ayon_fusion/api/pipeline.py
246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 |
|
parse_container(tool)
Returns imprinted container data of a tool
This reads the imprinted data from imprint_container
.
Source code in client/ayon_fusion/api/pipeline.py
304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 |
|