Open U-C-S opened 3 months ago
May I suggest:
wpfui
, theme adapting)
include the BrowserSelector page in the main window
Not sure what you mean by this.
use a (compact) NavigationView control
I don't prefer the compact one, but something like MS Store or Windows Settings is preferable. (the current implementation in Hurl Settings doesn't clean up memory, so memory usage rises up in 1 MBs as it's navigated, even to the same page)
include the BrowserSelector page in the main window
My idea would be to combine this page with the rest
Then the Nav button/menu can be compact or hidden to keep UI clean.
I personally prefer to keep Hurl Settings and Selector separately.
📰 WASDK 1.6.0 is out 😄
Any specific areas / issue you want help with?
Any specific areas / issue you want help
Guess so, one thing I want to experiment is migrate Hurl.BrowserSelector
(maybe should be renamed to Hurl.Selector
) to WinAppSDK. so only thing I am not sure there is how minimizing to Tray works there.
So, If you are interested, A minimal PR that only does migration to WinAppSdk and WinUi components without much UI or functional changes or you can choose to help with anything else, but focused PRs haha.
I want to experiment migrate
Hurl.BrowserSelector
to WinAppSDK
Hah, that's a big issue and not easy. I think you have more experience with this than I do, because you already worked on the Settings project. I think I'll try to convert the ListViews to Navigation control first :)
Now that Most of big fishes are fried,
v0.10
will focus on polishing Browser detection, opening, profiles...specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds
warning during release buildPossibly 0.9.x