Idea for "Always" registries #24
Conversation
|
Wow, thank you for the experiment! Let me look into your code. |
|
I have actually been thinking about a similar idea. I think it's basically the same as the "Search the web in Firefox" entry in PowerToys Run. However, I personally feel that this suggestion entry is not so intuitive. I would prefer typing "winget" to pick "Winget (PSRun)" entry for example when I want to install something, and then inside the Winget item I would want to filter the packages. So typing what I want to do is clearer to me. Does it make sense? Probably I would like to keep the simple filtering behavior until we find some other use cases. Your Winget registry is pretty useful though. |
Same, I tried it out this way because it was easy to get it running 😆
Yep. It would be cool to keep the realtime search feel but it would require some debouncing to make sure it's not spamming a slow resource lookup with every keystroke. Otherwise a "search on enter" experience would be fine to keep it simpler. I haven't looked properly yet but I suspect that with a slower async preview it's actually firing off every time the item changes even when you scroll past the items which could benefit from debouncing too. Thanks for the module I learned a lot just digging around. |
|
I'm really happy to hear that you like the module 😄! As for the realtime search, even if we support it in the PowerShellRun's search bar, what gives us the search functionality here is the winget module. We can't get both winget filter and PowerShellRun's filter at the same time. So "search on enter" might be better in this case. Just like the example #25, you can ask for an input first and then open the TUI. It doesn't look cool though. |
|
@ShaunLawrie Are you still interested in continuing this PR? It might not be the case if the main point was the 'Always' part. In either case I might create Winget Utility entry combining this Install feature and my Upgrade example in the future. |
|
I’m interested but it would be better if you flesh out the utility entry
style in the way that makes sense to you. The “always” thing is a bit of a
dead end because the UX is confusing.
I’m preparing for a talk so I’m tied up the next couple of weeks and
shouldn’t be procrastinating with this so I won’t have any time to work on
it 😂
…On Sat, 30 Mar 2024 at 1:38 PM, mdgrs ***@***.***> wrote:
@ShaunLawrie <https://github.com/ShaunLawrie> Are you still interested in
continuing this PR? It might not be the case if the main point was the
'Always' part. In either case I might create Winget Utility entry combining
this Install feature and my Upgrade example in the future.
—
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADEMYIUXZLY7FHEIYIRZRCLY2YCP7AVCNFSM6AAAAABFKTBWTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXHA2DMNZQGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Ok no problem! Thank you again for the PR. It was inspiring. Good luck for the talk! |
The UI for this thing is awesome. I have had an idea for integrating registries which are valid for when there are no results in PSRun for example searching for an app which isn't installed could suggest looking for it in winget/scoop/choco/brew/apt.
There are potentially other situations but my main use-case would be winget.
I've hacked together this proof of concept to see if you think it could work. It's a bit sketchy 😆 I just copied your file registry and hacked it until it worked. I'm also not sure if "Always" is the right term, maybe "Search" registries.
GlobalStore at the moment is hard coded to the built-in registries, so I've just added it to the list to get it to work.
psrun.mp4