Custom Header

[mottosso]

Goal

Visualise additional information through customisable header.

• Source conversation

Implementation

Framework-style implementation, where QML exposes a function to be overridden that return data in JSON format that QML can then visualise, along with callbacks in the form of buttons.

For example, it could return..

{
  "icon": "https://some/icon.png",
  "label": "/some/relevant/path/",
  "context": {
    "show": "some project",
    "shot": "fr1050",
    "task": "compositing"
  },
  "buttons": [
    {
      "name": "Task Switcher",
      "icon": "https://some/other/icon.png",
      "script": "import pipeline;pipeline.task_switcher()"
    },
    {
      "name": "Other Button",
      "icon": "https://some/other/icon2.png",
      "script": "import pipeline;pipeline.other_thing()"
    }
  ]

Where each member is generalised enough to facilitate common information.

[tokejepsen]

Maybe we could make fully customize the header with a type of widget and a grid layout?

[mottosso]

That's a good idea. The widget (called Item in QML) could expose members via a model, like how it does things for the items in the overview and perspective (e.g. see Page item). It'd both simplify the implementation, and grant full flexibility to the user. Good call!

For example, notice how Page has access to item.* members? Those could be anything.

It could have a default header, for when you aren't interested or have time for design, which could be overridden by a completely custom QML file.