McManning / McManning/BlueGraph
Custom GraphView hard to implement due to strong dependencies on CanvasView
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 256
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
The whole framework has a weakness in extensibility.
I tried to build upon the Execution Flow Example code to test how it would be possible to build an own visual scripting system on top of BlueGraph. This works ok for custom nodes and even custom node views.
However, when I wanted to extend on the possibilities of the CanvasView, it seems that the whole system relies on only using the CanvasView class and not allowing to, e.g., inherit from CanvasView or creating own GraphView classes.
Internally there are many dependencies on CanvasView.
I'd propose to re-arrange the system to allow for custom GraphView derived classes, probably allowing to extend CanvasView.
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 with the Execution Flow Example and trace the internal dependencies on CanvasView. Map which parts prevent custom GraphView-derived classes, then verify that an independently derived GraphView or extended CanvasView can be used throughout the visual scripting system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- game-dev, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100