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
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
//! # Tessera Runtime System
//!
//! This module provides the global runtime state management for the Tessera UI framework.
//! The runtime system maintains essential application state including the component tree,
//! window properties, and user interface state that needs to be shared across the entire
//! application lifecycle.
//!
//! ## Overview
//!
//! The [`TesseraRuntime`] serves as the central hub for all runtime data and side effects
//! in a Tessera application. It uses a thread-safe singleton pattern to ensure consistent
//! access to shared state from any part of the application, including from multiple threads
//! during parallel component processing.
//!
//! ## Thread Safety
//!
//! The runtime is designed with parallelization in mind. It uses [`parking_lot::RwLock`]
//! for efficient read-write synchronization, allowing multiple concurrent readers while
//! ensuring exclusive access for writers. This design supports Tessera's parallel
//! component tree processing capabilities.
//!
//! ## Usage
//!
//! Access the runtime through the static methods:
//!
//! ```
//! use tessera_ui::{TesseraRuntime, winit};
//!
//! // Read-only access (multiple threads can read simultaneously)
//! {
//! let window_size = TesseraRuntime::with(|rt| rt.window_size());
//! println!("Window size: {}x{}", window_size[0], window_size[1]);
//! }
//!
//! // Write access (exclusive access required)
//! TesseraRuntime::with_mut(|rt| {
//! rt.cursor_icon_request = Some(winit::window::CursorIcon::Pointer);
//! });
//! ```
//!
//! ## Performance Considerations
//!
//! - Prefer read locks when only accessing data
//! - Keep lock scopes as narrow as possible to minimize contention
//! - The runtime is optimized for frequent reads and occasional writes
//! - Component tree operations may involve parallel processing under read locks
use OnceLock;
use ;
use crateComponentTree;
/// Global singleton instance of the Tessera runtime.
///
/// This static variable ensures that there is exactly one runtime instance per application,
/// initialized lazily on first access. The [`OnceLock`] provides thread-safe initialization
/// without the overhead of synchronization after the first initialization.
static TESSERA_RUNTIME: = new;
/// Central runtime state container for the Tessera UI framework.
///
/// The `TesseraRuntime` holds all global state and side effects that need to be shared
/// across the entire application. This includes the component tree structure, window
/// properties, and user interface state that persists across frame updates.
///
/// ## Design Philosophy
///
/// The runtime follows these key principles:
/// - **Single Source of Truth**: All shared state is centralized in one location
/// - **Thread Safety**: Safe concurrent access through read-write locks
/// - **Lazy Initialization**: Runtime is created only when first accessed
/// - **Minimal Overhead**: Optimized for frequent reads and occasional writes
///
/// ## Lifecycle
///
/// The runtime is automatically initialized on first access and persists for the
/// entire application lifetime. It cannot be manually destroyed or recreated.
///
/// ## Fields
///
/// All fields are public to allow direct access after acquiring the appropriate lock.
/// However, consider using higher-level APIs when available to maintain consistency.