[Feature Request] Enhance Tag System to Support Organic Graph Relationships #10
Description
Current Behavior
The current tag-based management system in dev-2.0 is primarily used for:
- Bookmarking graphs
- Marking graphs for batch processing
Tags are essentially flat labels without relationships between graphs.
Proposed Enhancement
Consider extending the tag system to enable organic relationships between graphs, not just flat categorization.
Potential Use Cases
- Dependency Tracking: Tag graphs that depend on each other (e.g., "calls EventGraph", "referenced by BP_Player")
- Semantic Grouping: Group related functionality across different Blueprints (e.g., all "Combat System" graphs)
- Translation Order: Automatically determine translation order based on graph dependencies
- Cross-Blueprint Analysis: When translating, provide context from related graphs to improve code quality
Benefits
- Better understanding of Blueprint architecture before translation
- More coherent C++ output when translating related graphs together
- Improved documentation generation with relationship context
Questions for Discussion
- Should relationships be auto-detected or manually defined?
- How to visualize graph relationships in the UI?
- Should this integrate with UE's existing reference viewer?
Contact: ocarina1024@gmail.com