Some minor ideas and suggestions#12
Conversation
| ``` | ||
|
|
||
| The value is stored as a string on the form "#RRGGBB", eg `"#61138e"`. | ||
| The value is stored as a string on the form "#RRGGBB", eg `"#61138e"`. An optional alpha part could be added, like #AARRGGBB. This is seldom used, but make sense to be supported. |
There was a problem hiding this comment.
Having the option to pick color+alpha would be good 👍 , but because it changes the underlying data type, it should be a separate gddType. I suggest we create a separate PR for this.
| "commands": ["play", "next", "stop", "update", "(custom invokes)"] | ||
| /** A template should support "play" and "stop" as a minimum. Some templates are not meant to be updated when already */ | ||
| /** played, so they shall not support "update". Some templates support invoke comands like "show", "hide", "showOvertime" */ | ||
| /** or anything else. These commands can be used to render (or enable/disable) buttons in the UI. */ |
There was a problem hiding this comment.
I don't think we should be aiming to support existing templates in this specification, so I don't think this is the way to go.
A larger question though is: "how the templates should work"?
The play(), next(), stop(), update() pattern is a CasparCG one.
Is that something we should add to the specification in general? Or should that be added to the specification, but under for CasparCG-templates only?
|
I opened another PR for the color-suggestion, and the |
2 participants
No description provided.