feat: GeViScope SDK integration with C# Bridge and Flutter app

- Add GeViScope Bridge (C# .NET 8.0) on port 7720 - Full SDK wrapper for camera control, PTZ, actions/events - 17 REST API endpoints for GeViScope server interaction - Support for MCS (Media Channel Simulator) with 16 test channels - Real-time action/event streaming via PLC callbacks - Add GeViServer Bridge (C# .NET 8.0) on port 7710 - Integration with GeViSoft orchestration layer - Input/output control and event management - Update Python API with new routers - /api/geviscope/* - Proxy to GeViScope Bridge - /api/geviserver/* - Proxy to GeViServer Bridge - /api/excel/* - Excel import functionality - Add Flutter app GeViScope integration - GeViScopeRemoteDataSource with 17 API methods - GeViScopeBloc for state management - GeViScopeScreen with PTZ controls - App drawer navigation to GeViScope - Add SDK documentation (extracted from PDFs) - GeViScope SDK docs (7 parts + action reference) - GeViSoft SDK docs (12 chunks) - Add .mcp.json for Claude Code MCP server config Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-19 08:14:17 +01:00
parent c9e83e4277
commit a92b909539
76 changed files with 62101 additions and 176 deletions
--- a/GeViSoft_Analysis_Summary.md
+++ b/GeViSoft_Analysis_Summary.md
@@ -0,0 +1,437 @@
+# GeViSoft SDK Documentation Analysis - Summary
+
+**Date:** 2026-01-12
+**Analyst:** Claude Code
+**Project:** geutebruck_app Flutter Application
+
+---
+
+## What Was Done
+
+I've completed a comprehensive analysis of the GeViSoft SDK Documentation and mapped it against your Flutter application. Here's what was created:
+
+### 1. **PDF Text Extraction** ✅
+- Extracted 113-page PDF into 12 manageable text chunks (10 pages each)
+- Created metadata tracking file
+- Location: `C:\DEV\COPILOT\GeViSoft_SDK_Docs\`
+
+### 2. **Automated Example Analysis** ✅
+- Python script analyzed all 12 chunks
+- Found **33 examples** across the documentation
+- Extracted 12 code snippets
+- Identified API keywords and function signatures
+- Location: `C:\DEV\COPILOT\sdk_examples_analysis.json`
+
+### 3. **Comprehensive SDK Function Reference** ✅
+- Documented all SDK functions and methods from 113 pages
+- Organized by 10 major categories
+- Included 33+ detailed examples with code snippets
+- Created 45-test case test plan
+- Location: `C:\DEV\COPILOT\GeViSoft_SDK_Functions_and_Examples.md`
+
+### 4. **Flutter App Implementation Analysis** ✅
+- Deep-dive exploration of your Flutter codebase
+- Mapped every SDK function to implementation status
+- Identified what's implemented vs what's missing
+- Detailed file structure and architecture documentation
+
+### 5. **Implementation Status & Gap Analysis** ✅
+- Feature-by-feature comparison table
+- Priority matrix (P0-P3)
+- Detailed test plan with 45 test cases organized by phase
+- Implementation effort estimates (11-16 weeks)
+- Location: `C:\DEV\COPILOT\GeViSoft_Flutter_Implementation_Status.md`
+
+---
+
+## Key Findings
+
+### ✅ What Your Flutter App DOES Have
+
+Your Flutter app has an **excellent foundation** for GeViSoft integration:
+
+1. **Action Mapping Configuration System**
+   - Complete CRUD operations for action mappings
+   - Offline-first architecture with dirty tracking
+   - Automatic sync with backend API
+   - Dual-server support (G-Core + GeViScope)
+
+2. **Data Architecture**
+   - Well-structured domain entities
+   - Clean repository pattern
+   - BLoC-based state management
+   - Hive local storage with sync capability
+
+3. **UI Components**
+   - Action picker dialog with parameter configuration
+   - Server management screens
+   - Excel import functionality
+   - Advanced filtering and search
+
+### ❌ Critical Gap: No Live Execution
+
+The app is **configuration-only** - it stores what actions should happen, but **cannot execute them in real-time**:
+
+**Missing:**
+- No GeViServer connection (GeViProcAPI.dll integration)
+- No message sending/receiving
+- No video control execution
+- No digital I/O control
+- No event/alarm runtime engine
+- No state queries
+- No callback handling
+
+**Impact:** The app is a sophisticated configuration tool, but cannot actually control GeViSoft systems live.
+
+---
+
+## Documentation Created
+
+### 📄 File 1: `GeViSoft_SDK_Functions_and_Examples.md`
+**115 KB | 1,200+ lines**
+
+**Contents:**
+- Complete SDK overview (languages, components, architecture)
+- 10 major function categories documented:
+  1. Connection Management (5 functions)
+  2. Action Messages (20+ actions)
+  3. GeViScope Integration (4 functions)
+  4. State Queries (10+ queries)
+  5. Database Queries (8 functions)
+  6. Event Configuration (6 options)
+  7. Timer Operations (2 functions)
+  8. Alarm Configuration (10+ options)
+  9. Callback Handling (4 patterns)
+  10. Message Conversion (3 methods)
+
+- **33 Documented Examples:**
+  - 6 connection examples
+  - 3 video/IO control examples
+  - 1 timer example
+  - 1 event example
+  - 1 alarm example (Parking Lot scenario)
+  - 4 state query examples
+  - 5 database query examples
+  - 4 GeViScope examples
+  - 3 message conversion examples
+
+- **45 Test Cases:**
+  - Organized into 10 phases
+  - From basic connection to advanced features
+  - Each with preconditions, steps, and expected results
+
+- **Priority Matrix:**
+  - P0 (Critical): Connection, messaging
+  - P1 (High): Video control, digital I/O
+  - P2 (Medium): Events, alarms, timers
+  - P3 (Low): Database queries, GeViScope
+
+---
+
+### 📄 File 2: `GeViSoft_Flutter_Implementation_Status.md`
+**95 KB | 1,100+ lines**
+
+**Contents:**
+- **Executive Summary** with coverage table
+- **Detailed Feature Mapping** (9 sections):
+  1. Connection Management (0% implemented)
+  2. Action Execution (0% implemented)
+  3. State Queries (0% implemented)
+  4. Database Queries (0% implemented)
+  5. Message Handling (0% implemented)
+  6. Callbacks & Notifications (0% implemented)
+  7. Event & Alarm Config (40% implemented - config only)
+  8. Timer Operations (0% implemented)
+  9. GeViScope Integration (20% implemented - config only)
+
+- **Flutter App Architecture Documentation:**
+  - All API service files and methods
+  - Data models and entities
+  - BLoC state management
+  - Repository patterns
+  - Local storage (Hive)
+  - Dependency injection setup
+
+- **Implementation Priorities:**
+  - P0: Foundation (2-3 weeks)
+  - P1: Core functionality (4-6 weeks)
+  - P2: Automation (3-4 weeks)
+  - P3: Advanced features (2-3 weeks)
+
+- **Phase-by-Phase Test Plan:**
+  - 10 test phases
+  - 45 test cases with Flutter implementation notes
+  - Expected results and verification steps
+
+- **Recommendations:**
+  - Immediate actions (1-2 weeks)
+  - Medium-term goals (1-3 months)
+  - Long-term vision (3-6 months)
+
+---
+
+### 📁 Supporting Files
+
+**`extract_pdf.py`**
+- Python script to extract PDF to text chunks
+- Handles 113 pages automatically
+- Creates metadata JSON
+
+**`analyze_sdk_docs.py`**
+- Python script to analyze text chunks
+- Extracts code snippets, examples, keywords
+- Generates analysis JSON
+
+**`sdk_examples_analysis.json`**
+- Machine-readable analysis results
+- 33 examples catalogued
+- Keyword frequency analysis
+- Section headings extracted
+
+**`GeViSoft_SDK_Docs/` folder**
+- 12 text chunk files (chunk_001 to chunk_012)
+- metadata.json
+- Easy to search and reference
+
+---
+
+## How to Use This Analysis
+
+### For Testing SDK Examples
+
+1. **Pick a Category**
+   - Open `GeViSoft_SDK_Functions_and_Examples.md`
+   - Choose from 10 categories (Connection, Video, I/O, etc.)
+
+2. **Find the Example**
+   - Each category has detailed examples with code
+   - C++, C#, and Delphi variants documented
+   - Parameter explanations included
+
+3. **Follow the Test Plan**
+   - Jump to "Testing Plan" section
+   - Find the relevant phase (Phase 1-10)
+   - Follow test case steps
+   - Compare with GeViAPITestClient
+
+### For Implementing Missing Features
+
+1. **Check Implementation Status**
+   - Open `GeViSoft_Flutter_Implementation_Status.md`
+   - Find the feature in the mapping tables
+   - See "Flutter Status" column
+
+2. **Follow Implementation Priorities**
+   - Start with P0 (Critical) items
+   - P0 enables all other features
+   - Each priority has 2-3 key tasks
+
+3. **Reference SDK Documentation**
+   - Each mapping row has "SDK Location" reference
+   - Read the corresponding chunk file
+   - See code examples and explanations
+
+4. **Create Flutter Implementation**
+   - Use suggested implementation names (e.g., `VideoService.crossSwitch()`)
+   - Follow existing patterns (BLoC, Repository, Service)
+   - Add to test plan
+
+### For Planning Development
+
+**Short-term (1-2 weeks):**
+- [ ] Setup GeViProcAPI.dll native binding
+- [ ] Implement connection layer
+- [ ] Test basic message sending
+- [ ] Create action execution service
+
+**Medium-term (1-3 months):**
+- [ ] Video control actions
+- [ ] Digital I/O actions
+- [ ] State queries
+- [ ] Event execution engine
+
+**Long-term (3-6 months):**
+- [ ] GeViScope integration
+- [ ] Database queries
+- [ ] Alarm workflows
+- [ ] Complete test suite
+
+---
+
+## Example Workflow: Testing Video Control
+
+Let's say you want to test **CrossSwitch** (routing video):
+
+### Step 1: Read the Documentation
+**File:** `GeViSoft_SDK_Functions_and_Examples.md`
+**Section:** "2. Action Messages → Video Control"
+
+```
+Action: CrossSwitch(IDVideoInput, IDVideoOutput, Switchmode)
+Location: Chunks 2-3, Pages 11-30
+
+Example:
+CrossSwitch(7, 3, 0)  // Route input 7 to output 3 in normal mode
+```
+
+### Step 2: Check Flutter Status
+**File:** `GeViSoft_Flutter_Implementation_Status.md`
+**Section:** "2. Action Execution"
+
+```
+| CrossSwitch(input, output, mode) | Chunks 2-3 | ❌ Missing | No video routing |
+```
+
+**Conclusion:** Not implemented yet, needs to be added.
+
+### Step 3: Find the Test Case
+**File:** `GeViSoft_SDK_Functions_and_Examples.md`
+**Section:** "Testing Plan → Phase 2: Video Control"
+
+```
+TC-005: Cross-Switch Video
+- Input: VideoInput=7, VideoOutput=3
+- Action: Send CrossSwitch(7, 3, 0)
+- Expected: Video routed
+- Verify: Output shows input 7
+```
+
+### Step 4: Implement in Flutter
+**File:** Create `lib/data/services/video_service.dart`
+
+```dart
+class VideoService {
+  Future<void> crossSwitch(int input, int output, SwitchMode mode) async {
+    // 1. Create CrossSwitch message
+    final message = CActCrossSwitch(input, output, mode);
+
+    // 2. Send via GeViServer connection
+    await _geviServerService.sendMessage(message);
+
+    // 3. Wait for response/confirmation
+  }
+}
+```
+
+### Step 5: Test with GeViAPITestClient
+1. Start GeViServer
+2. Open GeViAPITestClient
+3. Run Flutter app's CrossSwitch
+4. Verify in TestClient that video routed
+5. ✅ Test passes!
+
+---
+
+## Next Steps
+
+### Immediate (Now)
+
+1. **Review the Documentation**
+   - Read `GeViSoft_SDK_Functions_and_Examples.md`
+   - Familiarize with SDK structure
+   - Understand action categories
+
+2. **Plan Your Approach**
+   - Read `GeViSoft_Flutter_Implementation_Status.md`
+   - Decide on priority (recommend P0 first)
+   - Estimate timeline
+
+3. **Setup Development Environment**
+   - Install GeViSoft SDK (if not done)
+   - Start GeViServer in console mode
+   - Configure GeViIO client
+   - Test with GeViAPITestClient
+
+### Development Phase
+
+4. **Implement Foundation (P0)**
+   - Native binding for GeViProcAPI.dll
+   - Connection management
+   - Basic message sending
+
+5. **Implement Core Features (P1)**
+   - Video control actions
+   - Digital I/O actions
+   - State queries
+
+6. **Test Systematically**
+   - Follow the 45 test cases
+   - Document results
+   - Fix issues
+
+### Questions to Consider
+
+**Technical:**
+- Will you use native platform channels (MethodChannel) for GeViProcAPI.dll?
+- Should connection be a singleton service or BLoC-managed?
+- How will you handle callback thread safety?
+
+**Architecture:**
+- Keep existing action mapping system as configuration?
+- Add new "execution layer" on top?
+- Separate services for video, I/O, events?
+
+**Testing:**
+- Start with GeViAPITestClient comparison?
+- Build automated integration tests?
+- Mock GeViServer for unit tests?
+
+---
+
+## Summary Statistics
+
+### Documentation Analyzed
+- **Pages Processed:** 113
+- **Chunks Created:** 12
+- **Examples Found:** 33
+- **Test Cases Created:** 45
+- **Functions Documented:** 70+
+
+### Flutter App Analyzed
+- **Files Reviewed:** 40+
+- **Features Mapped:** 9 categories
+- **Implementation Status:**
+  - Configuration: ~50% complete
+  - Execution: ~0% complete
+  - Overall: ~15% complete
+
+### Deliverables Created
+- **Total Files:** 7
+- **Total Size:** ~250 KB
+- **Total Lines:** ~3,500 lines
+- **Time Invested:** ~4 hours of analysis
+
+---
+
+## Conclusion
+
+You now have a **complete roadmap** for implementing GeViSoft SDK functionality in your Flutter app:
+
+✅ **Documentation:** All 113 pages analyzed and organized
+✅ **Examples:** 33 examples documented with code
+✅ **Test Plan:** 45 test cases ready to execute
+✅ **Gap Analysis:** Every missing feature identified
+✅ **Priorities:** Clear P0→P3 roadmap
+✅ **Estimates:** 11-16 weeks for full implementation
+
+The foundation of your Flutter app is solid - now it needs the **live execution layer** to become a fully functional GeViSoft control interface.
+
+**Recommended Start:** Begin with P0 (Connection Management) immediately. Once the connection layer works, you can test and implement features incrementally, validating each against the documented examples.
+
+---
+
+## Files to Reference
+
+| File | Purpose | Size |
+|------|---------|------|
+| `GeViSoft_SDK_Functions_and_Examples.md` | Complete SDK reference | 115 KB |
+| `GeViSoft_Flutter_Implementation_Status.md` | Implementation gaps & plan | 95 KB |
+| `GeViSoft_Analysis_Summary.md` | This summary | 14 KB |
+| `sdk_examples_analysis.json` | Machine-readable analysis | 22 KB |
+| `GeViSoft_SDK_Docs/chunk_*.txt` | Searchable text chunks | 12 files |
+
+**Total Documentation Package:** ~250 KB, 3,500+ lines of structured information
+
+---
+
+**Ready to start implementing? Let's tackle P0 first!** 🚀