Mission-DMX / Mission-DMX/Project-Editor
Rework node editor to use imgui based renderer
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 1
- Avg merge
- 27m
- Merged PRs (30d)
- 1
Description
The rendering of the node editor is slow and could benefit from being ported to imgui. We shouldn't exchange the model, just the renderer. This would also enable us to implement the following features:
- Dropping filters on edges in order to put it in between adjacent nodes
- have nicer paths representing the edges
- Implement type hints for the input and output ports as well as an indication whether or not the connection of an input node is mandatory
- Implement better UI controls for the nodes
A viable starting point would be this repo.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the existing node editor renderer and reviewing the linked imgui-node-editor repository. Keep the existing model unchanged while assessing the renderer migration and the requested edge, path, port-hint, and node-control improvements; done means the node editor uses the imgui-based renderer with these capabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100