How moise7000/p-l-level-editor works
Project type and purpose
• This is a macOS desktop application built in Swift/SwiftUI (an Xcode project).
File structure
• Xcode scaffolding (P-L-Level-Editor.xcodeproj & workspace).
• P-L-Level-Editor/Assets.xcassets & Sound – app-bundled images and sounds.
• P-L-Level-Editor/Helpers
– FileMonitor.swift: watches the user-selected game folder for changes
– JSONFunction.swift, FileManager utilities, generic playground/tester views
• P-L-Level-Editor/Models
– AssetsModel, GridModel, GraphModel, LevelsGraphMonitor, DataController (persistence)
– Data folder: domain data types and SwiftData controller
• P-L-Level-Editor/Views
– SwiftUI screens: ContentView, LevelEditorView, EditLevelView, LevelsGraphView, SoundEditorView, etc.
• Entry point: P_L_Level_EditorApp.swift
README for insights
• User must select the game’s src/ folder so the editor can traverse
• PNG naming conventions (camelCase) feed into JSON generation
• Scene files in src/scenes drive the “Levels Architecture” graph
Defining components
a. Main components
– UI Layer (SwiftUI Views & View structs)
– ViewModels/Controllers (Models + DataController orchestrating data flow)
– File System & Asset Scanner (FileMonitor, FileManager, JSONFunction)
– Graph Engine (GraphModel, LevelsGraphMonitor)
– Local Storage (JSON files, SwiftData store)
– External “Game Project src folder” (assets & scenes)
b. Relationships & interactions
1. User opens app → Views rendered by SwiftUI
2. User selects “src” folder → FileMonitor begins scanning → JSONFunction parses asset files → AssetsModel & LevelsModel populated
3. Models publish changes → Views update (via @ObservedObject/@State)
4. On edit/save → Views invoke DataController → writes JSON or SwiftData → persisted to disk
5. GraphModel listens for scene file changes → updates LevelsGraphView
c. Architectural patterns
– MVVM: SwiftUI Views bind to Observable Models/ViewModels
– Observer/Publisher (Combine) in FileMonitor and DataController
– Singleton or shared DataController for centralized persistence
d. Key technologies & frameworks
– SwiftUI for UI
– Combine for reactive updates
– JSONEncoder/Decoder for metadata
– FileManager APIs for directory traversal
– SwiftData or custom JSON-backed persistence