Export a bare-bone 3D viewer
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- html, python
- Domain
- computer-graphics, frontend, web-dev
Research direction
Begin with the client configuration and session API, then inspect how a loaded model reaches the renderer. Confirm the export entry point can produce a standalone HTML web component from a client session; done means it opens, embeds in arbitrary HTML, and retains no VISOR state or UI.
Written by the indexing model from the issue text.
Description
User Story Description
As a user, I want to be able to export a bare-bone 3D renderer that can be embedded into a stand-alone HTML file. This functionality needs to be available only from the client configuration of VISOR - if the remote rendering configuration does not make it possible, that is an acceptable limitation.
Acceptance Criteria
Start a client session of VISOR. Load a model. Use the API call to export a bare-bone 3D viewer that can be opened in an HTML file.
That viewer can be embedded as a web component into any HTML file.
The bare-bone viewer does not need to store any state information, nor does he need to share UI / features with VISOR.
Additional Links
No response
Requires new or update to third party ? If "yes" add the name(s) and the version(s) of the Third Party Software.
No
Name and Version for Third Parties
No response
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 47
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ansys/Visual-Interactive-Simulation-Object-Renderer
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Library updates Opentechnical
ansys/Visual-Interactive-Simulation-Object-Renderer#136 · 1 assignee ·
-
maintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#131 · 1 assignee ·
-
Release 1.0.2 Openmaintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#130 · 1 assignee ·
-
enhancement
ansys/Visual-Interactive-Simulation-Object-Renderer#126 · 1 assignee ·
All issues in ansys/Visual-Interactive-Simulation-Object-Renderer
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100