TheXamlGuy
|
640b3292b2
|
inject the widget assembly into the IoC as we are going to need it further in
|
2024-01-27 16:21:53 +00:00 |
|
TheXamlGuy
|
48925b89ff
|
restructure project for part 2
|
2024-01-27 10:55:53 +00:00 |
|
TheXamlGuy
|
5e26e97f6b
|
break widget related stuff into its own project as the main HB project was just becoming too bloated
|
2024-01-24 20:50:59 +00:00 |
|
TheXamlGuy
|
d7d90b3d54
|
wrapped custom widget items in containers so we have more control of the surrounding, i.e. divider
|
2024-01-10 19:25:16 +00:00 |
|
TheXamlGuy
|
66f65185c8
|
Fixed
|
2024-01-06 18:15:20 +00:00 |
|
TheXamlGuy
|
9fdb125c13
|
restructure
|
2024-01-06 16:56:32 +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 |
|
TheXamlGuy
|
b380f06fbf
|
Add per plugin json configuration support from a single file
|
2024-01-05 21:54:48 +00:00 |
|
TheXamlGuy
|
d94add17f9
|
Added primaey commands extenion/plugin
|
2024-01-04 23:02:51 +00:00 |
|
TheXamlGuy
|
d45076f2a9
|
get plugin system working
|
2024-01-04 20:53:49 +00:00 |
|
dan_c
|
da8af59391
|
Add project files.
|
2024-01-04 17:32:36 +00:00 |
|