This website requires JavaScript.
Explore
Help
Sign In
dan
/
Hyperbar
Watch
1
Star
0
Fork
0
You've already forked Hyperbar
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
Wiki
Activity
Files
a2a5591502405c06c1c4023fc83bcef993a5fffa
Hyperbar
/
Hyperbar.Windows
T
History
TheXamlGuy
858a23c28d
A widget should have only one IWidgetViewModel by default... wondering whether if we should go for the first served, or throw if multiple detected, or ignore the widget
2024-01-30 22:30:08 +00:00
..
Assets
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
Lifecycles
A widget should have only one IWidgetViewModel by default... wondering whether if we should go for the first served, or throw if multiple detected, or ignore the widget
2024-01-30 22:30:08 +00:00
Properties
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
app.manifest
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
App.xaml
restructure project for part 2
2024-01-27 10:55:53 +00:00
App.xaml.cs
too many to add
2024-01-29 22:03:36 +00:00
Hyperbar.Windows.csproj
add uid loading support
2024-01-27 20:28:40 +00:00
Package.appxmanifest
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