1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
/// Document Model Architecture
///
/// This module provides a clean abstraction layer between the editor's rendering/editing
/// operations and the underlying text buffer implementation. It supports both small files
/// with precise line indexing and huge files with lazy loading and byte-based positioning.
///
/// # Overview
///
/// The document model is inspired by VSCode's architecture but enhanced to support huge files
/// (multi-GB) with lazy loading. It provides a three-layer architecture:
///
/// ```text
/// ┌─────────────────────────────────────┐
/// │ View/Editor Layer │
/// │ (rendering, user interaction) │
/// └────────────┬────────────────────────┘
/// │ Uses DocumentModel trait
/// ▼
/// ┌─────────────────────────────────────┐
/// │ DocumentModel (this module) │
/// │ - get_viewport_content() │
/// │ - get_range(), insert(), delete() │
/// │ - Dual coordinate systems │
/// └────────────┬────────────────────────┘
/// │ Implemented by EditorState
/// ▼
/// ┌─────────────────────────────────────┐
/// │ TextBuffer (implementation) │
/// │ - Piece tree operations │
/// │ - Lazy loading for large files │
/// │ - Line indexing for small files │
/// └─────────────────────────────────────┘
/// ```
///
/// # Key Concepts
///
/// ## Dual Position System
///
/// Documents support two coordinate systems:
/// - **Line/Column**: For small files with precise line indexing (like VSCode)
/// - **Byte Offset**: For huge files where line indexing may be unavailable or approximate
///
/// ## Transparent Lazy Loading
///
/// For huge files, the document model uses a two-phase rendering approach:
/// 1. **Prepare Phase** (`prepare_for_render()`): Pre-loads viewport data with `&mut` access
/// 2. **Render Phase** (`get_viewport_content()`): Accesses pre-loaded data with `&self`
///
/// This avoids RefCell complexity while supporting lazy loading.
///
/// ## Explicit Error Handling
///
/// Unlike TextBuffer's `slice()` which returns empty strings on error, DocumentModel methods
/// return `Result<T>` or `Option<T>` to make failures explicit and allow proper error messages.
///
/// # Usage Example
///
/// ```rust,ignore
/// use fresh::document_model::{DocumentModel, DocumentPosition};
///
/// // Query document capabilities
/// let caps = state.capabilities();
/// if caps.has_line_index {
/// // Use line/column positioning
/// let pos = DocumentPosition::line_col(10, 5);
/// } else {
/// // Use byte offset positioning
/// let pos = DocumentPosition::byte(1024);
/// }
///
/// // Prepare viewport before rendering
/// state.prepare_for_render()?;
///
/// // Get viewport content for rendering
/// let viewport = state.get_viewport_content(
/// DocumentPosition::byte(0),
/// 24 // lines
/// )?;
///
/// for line in viewport.lines {
/// println!("{}: {}", line.byte_offset, line.content);
/// }
/// ```
///
/// # Design Benefits
///
/// 1. **Clean Abstraction**: Rendering never touches TextBuffer directly
/// 2. **Better Than VSCode**: Supports multi-GB files (VSCode has 20MB limit)
/// 3. **Type Safety**: Explicit Optional/Result types prevent silent failures
/// 4. **Extensibility**: Easy to add RemoteDocument, VirtualDocument, etc.
///
/// See also: `docs/DOCUMENT_MODEL.md` for detailed architecture documentation.
use Result;
/// Position in a document - can be line-based or byte-based
///
/// For small files with line indexing enabled, LineColumn provides precise positioning.
/// For huge files without line indexing, ByteOffset provides always-available positioning.
/// Information about a document's capabilities
///
/// This helps callers understand what operations are available and how to
/// interact with the document efficiently.
/// A single line in the viewport
/// Content for rendering a viewport
/// High-level document interface supporting both line and byte operations
///
/// This trait provides a clean abstraction for all editor operations, whether
/// rendering, editing, or searching. It works transparently with both small
/// files (with line indexing) and huge files (with lazy loading).