v0.10 Planning

[U-C-S]

Now that Most of big fishes are fried, v0.10 will focus on polishing Browser detection, opening, profiles...

---

Original 0.10 plan (see new plan here)

• Improved Browser Management and Auto-discovery #150
  • Show browser's profiles in BrowserSelector MainWindow #32
• Hurl Settings (post-release planning) #149
• Move to WinAppSDK v1.6
  • Fix 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 build
  • Adopt AoT compilation

Possibly 0.9.x

• Detect Arc Browser Automatically #100
• Option to disable Minimize on focus loss
• Explore auto-updater
• Add a method to keep the window inside desktop boundaries on opening #162

[Jay-o-Way]

May I suggest:

• include the BrowserSelector page in the main window (for quick access to settings, remove wpfui, theme adapting)
  • Brush up the XAML for that page (let me know if you want me to pick up something here)
• use a (compact) NavigationView control
• use as native as possible solution for TitleBar

[U-C-S]

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)

[Jay-o-Way]

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.

[U-C-S]

I personally prefer to keep Hurl Settings and Selector separately.

[Jay-o-Way]

📰 WASDK 1.6.0 is out 😄

[Jay-o-Way]

Any specific areas / issue you want help with?

[U-C-S]

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.

[Jay-o-Way]

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 :)

[uqiu]

too many thanks for your amazing work.

[U-C-S]

v0.10 Scope Revaluation

• Move Hurl.Settings to possible upcoming winappsdk 1.7 (for now, will move it 1.6)
• Update to .NET 9
• Use learnings from Migrate Hurl.BrowserSelector to WinUI3 #174 to refactor Hurl.Settings app
• ..... (TODO: add more to the list)

All of the features originally planned will now move for a next release instead. Why? The way the current code is written, I feel doesn't support adding new features without a significant refactor yet again as I learnt from while developing #174.
Additionally I am trying to write a new library for Glob patterns for URLs with some ideas I had (see the project here, it's still a WIP).

[Jay-o-Way]

Yeah, at some point (if it were me) I would start thinking about starting over from (almost) scratch, using the latest. That needs a huge amount of time and effort, but does mean a fresh clean code, and being able to include/solve many ideas and issues.

P.S. To me, Regular Expressions are familiar, but Glob patterns are not. To me, they seem like the same thing. What is your experience with Glob and is it worth supporting both?

Also, 1.7 Preview 1 is out 🚀 https://github.com/microsoft/windowsappsdk/releases