[PoC] Usage of Parametric STC UI component(s) for parameter/criteria configuration

[rfahlberg]

📝 Description of the feature

Feature Description

Create a PoC to demonstrate and verify the ability of embedding/usage of the Parametric STC UI component(s) for parameter/criteria configuration as provided by oSL Dev Team into a basic dash-based client App intended for editing the parametric of a (parametric) workflow component.

As basis for a suitable workflow used in the PoC, one of the existing workflow building examples or the Design Study Convenience Module can/should be used. It should be demonstrated, that the UI components are suitable to conveniently edit the "design study" parametric.

Prerequisites

During development, the dependent packages are provided by the oSL Dev team, to be used locally. Finally, those packages are intended to be shipped with the optiSLang installer (either as wheel files, or already installed in the optiSLang Python environment) and should be fetched from there.

Acceptance Criteria

• Parametric STC UI component(s) for parameter/criteria configuration embedded in a basic dash-based client App
• UI component(s) are populated with the input parametric on init (as obtained from a design study)
• Modified parametric is obtained from the UI and written back to the design study

💡 Steps for implementing the feature

• Implementation of conversion between parametric definitions on PyOptiSLang side (https://optislang.docs.pyansys.com/version/stable/api/parameters.html, https://optislang.docs.pyansys.com/version/stable/api/criteria.html) to parametric definition on Parametric STC UI component(s) side
• Implementation of dash-based App skeleton
• Embedding of Parametric STC UI component(s) into the dash-based App skeleton
• Provisioning of a Jupyter notebook demonstrating the client App

🔗 Useful links and references

No response