Skip to content

Add engine version requirements to renderRequirements (Issue#25)#58

Open
Richardpwe wants to merge 1 commit intoebu:mainfrom
Richardpwe:feature/issue-25
Open

Add engine version requirements to renderRequirements (Issue#25)#58
Richardpwe wants to merge 1 commit intoebu:mainfrom
Richardpwe:feature/issue-25

Conversation

@Richardpwe
Copy link

Adds an optional engine property to renderRequirements: a list of requirements for the rendering engine (e.g. CEF, Gecko) with a minimum required version (version.min). min is intentionally defined as a string so different version formats (CEF, Chromium, WebKit, etc.) are supported.

@dvdeurse
Copy link
Collaborator

This looks ok to me, but we probably need something similar in the Server API so that Renderers can expose their supported engines.

@Richardpwe
Copy link
Author

That makes sense, I didn't thought about that.
In the current Server API we already have RenderCharacteristics on RendererInfo, which is meant to correspond to the renderRequirements field in the graphic manifest.

To mirror the new renderRequirements.engine[] in the graphics spec, I’d add an
engine?: { type: string; version: { min: string } }[] field to RenderCharacteristics,
so the structure stays 1:1 between manifest and Server API. That would allow control systems to match a graphic’s engine requirements against what a renderer actually supports.

@nytamin nytamin linked an issue Mar 15, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rendering engine version

2 participants