init

enriched-partialglm/DTS Viewer/DTS.Viewer/View.md

@@ -0,0 +1,82 @@
+---
+source_files:
+  - DTS Viewer/DTS.Viewer/View/TabView.xaml.cs
+  - DTS Viewer/DTS.Viewer/View/MenuView.xaml.cs
+  - DTS Viewer/DTS.Viewer/View/MainView.xaml.cs
+  - DTS Viewer/DTS.Viewer/View/ShellView.xaml.cs
+  - DTS Viewer/DTS.Viewer/View/ViewerShellView.xaml.cs
+  - DTS Viewer/DTS.Viewer/View/NavigationView.xaml.cs
+generated_at: "2026-04-16T11:23:56.516498+00:00"
+model: "zai-org/GLM-5-FP8"
+schema_version: 1
+sha256: "c4a45b12e62dbb35"
+---
+
+# Documentation: DTS.Viewer Views
+
+## 1. Purpose
+
+This module contains the code-behind files for WPF views in the DTS Viewer application. It defines six view components (`TabView`, `MenuView`, `MainView`, `ShellView`, `ViewerShellView`, `NavigationView`) that serve as the visual layer of the application. Each view implements a corresponding interface from `DTS.Common.Interface`, enabling view abstraction—likely to support MVVM architecture, dependency injection, or unit testing. The views are thin wrappers around XAML definitions, with all interaction logic delegated to the XAML layer.
+
+---
+
+## 2. Public Interface
+
+### `TabView`
+- **Namespace:** `DTS.Viewer`
+- **Implements:** `ITabView`
+- **Constructor:** `public TabView()` — Initializes the component via `InitializeComponent()`.
+
+### `MenuView`
+- **Namespace:** `DTS.Viewer`
+- **Implements:** `IMenuView`
+- **Constructor:** `public MenuView()` — Initializes the component via `InitializeComponent()`.
+
+### `MainView`
+- **Namespace:** `DTS.Viewer`
+- **Implements:** `IMainView`
+- **Constructor:** `public MainView()` — Initializes the component via `InitializeComponent()`.
+
+### `ShellView`
+- **Namespace:** `DTS.Viewer.View`
+- **Implements:** `IViewerShellView`
+- **Constructor:** `public ShellView()` — Initializes the component via `InitializeComponent()`.
+
+### `ViewerShellView`
+- **Namespace:** `DTS.Viewer`
+- **Implements:** `IViewerShellView`
+- **Constructor:** `public ViewerShellView()` — Initializes the component via `InitializeComponent()`.
+
+### `NavigationView`
+- **Namespace:** `DTS.Viewer`
+- **Implements:** `INavigationView`
+- **Constructor:** `public NavigationView()` — Initializes the component via `InitializeComponent()`.
+
+---
+
+## 3. Invariants
+
+- Each view class is declared `partial`, indicating the existence of a corresponding XAML file that completes the class definition at compile time.
+- Each view implements exactly one interface from `DTS.Common.Interface`.
+- The constructor for each view must call `InitializeComponent()` to load the associated XAML resources and UI definition.
+- `ShellView` and `ViewerShellView` both implement the same interface (`IViewerShellView`), but reside in different namespaces.
+
+---
+
+## 4. Dependencies
+
+### This module depends on:
+- `DTS.Common.Interface` — Provides the interfaces (`ITabView`, `IMenuView`, `IMainView`, `IViewerShellView`, `INavigationView`) that each view implements.
+
+### What depends on this module:
+- **Unclear from source alone.** Consumers would typically include view composition logic, MVVM view models, or dependency injection containers that resolve these view types. The associated XAML files (not provided) would also define the visual structure and bindings.
+
+---
+
+## 5. Gotchas
+
+1. **Duplicate interface implementation:** Both `ShellView` (in namespace `DTS.Viewer.View`) and `ViewerShellView` (in namespace `DTS.Viewer`) implement `IViewerShellView`. The reason for this duplication is unclear from source alone—it may indicate a refactoring in progress, a legacy artifact, or intentional separation for different contexts.
+
+2. **Namespace inconsistency:** `ShellView` resides in `DTS.Viewer.View` while all other views reside directly in `DTS.Viewer`. This may cause confusion when resolving types or configuring dependency injection.
+
+3. **No explicit behavior in code-behind:** All views contain only the constructor with `InitializeComponent()`. Any event handlers, commands, or UI logic must be defined in the XAML files (not provided) or handled via MVVM bindings.