 TheXamlGuy
|
9a669e695e
|
threading fixes
|
2024-01-07 22:37:54 +00:00 |
|
|
TheXamlGuy
|
2e8af23784
|
reduce mediator duffs
|
2024-01-07 18:02:04 +00:00 |
|
|
TheXamlGuy
|
05150c2c03
|
fixed startup
|
2024-01-07 13:28:21 +00:00 |
|
|
TheXamlGuy
|
d86c5da7a9
|
fixed fetching configuration from root
|
2024-01-07 13:18:38 +00:00 |
|
|
TheXamlGuy
|
28af62d72d
|
More configuration work
|
2024-01-06 21:33:53 +00:00 |
|
|
TheXamlGuy
|
9fdb125c13
|
restructure
|
2024-01-06 16:56:32 +00:00 |
|
|
TheXamlGuy
|
71881ad877
|
wired up key commands
|
2024-01-06 16:39:30 +00:00 |
|
|
TheXamlGuy
|
a77c356389
|
Added Handler registrations in IServiceCollectionExtensions
|
2024-01-06 15:09:11 +00:00 |
|
|
TheXamlGuy
|
e1c7846e45
|
Codemaid
|
2024-01-06 14:34:25 +00:00 |
|
|
TheXamlGuy
|
53537aa4c7
|
Added messaging pipeline
|
2024-01-06 13:57:18 +00:00 |
|
|
TheXamlGuy
|
4a27534e39
|
Make custom widgets independent of any WinUI framework concerns. Although one can add WinUI concerns to ther widget if they want to build a fully customized widget. In theory, it may also be possible to host a widget of WPF, Avalonia, or Blazor.
|
2024-01-06 09:57:23 +00:00 |
|
|
TheXamlGuy
|
3e88950669
|
Rename projects to better structure it. The aim is to try and keep it not dependant on the type of UI framework it uses thus allowing us to switch to another UI framework if we need later...
|
2024-01-06 08:49:12 +00:00 |
|