Flow.Launcher
Flow.Launcher copied to clipboard
Implement PluginSearch TextBox & ContentControl Lazy Load
looks like it's still WIP? i will mark it as draft
search is not working, tried pressing enter too.
search is not working, tried pressing enter too.
works for me. What's your behavior?
Tried it again and still the Plugin Store's search is not working. I removed entire flow user data then rebuilt and ran. Went into plugin store tab and clicked on the search text, put in a search term 'colors' and pressed enter. Nothing happens.
Search is however working for me in the plugins tab.
Also:
- can we add Ctrl + F focus to the Plugin Store search text box please
- add a tooltip to both tabs so when hovering over the search text box it displays something like 'Ctrl + F to search plugins'
Tried it again and still the Plugin Store's search is not working. I removed entire flow user data then rebuilt and ran. Went into plugin store tab and clicked on the search text, put in a search term 'colors' and pressed enter. Nothing happens.
Search is however working for me in the plugins tab.
Also:
* can we add Ctrl + F focus to the Plugin Store search text box please * add a tooltip to both tabs so when hovering over the search text box it displays something like 'Ctrl + F to search plugins'
Ah I get your idea🤣I haven't implemented the plugin store search. I will fix that later.
-
Plugin Store works. Plugin list doesn't works.
-
It is good to be searched when entering the enter key, but if the search box is empty, it is necessary to initialize it.
-
Can we add label in this PR? (installed, update, etc...) if so, we need more works with install button. (update, disabled...)
-
other topic. we need something to message when no result / no connection.
It is good to be searched when entering the enter key, but if the search box is empty, it is necessary to initialize it.
That's pretty slow though, because empty means there are most plugins that needs to be rendered. Though it makes sense. We can add a LostFocus event for that.
Oh we already have the lostfocus event. I don't want to filter while user typing because that will create unhappy typing experience. If later we find ways to optimize the render, we can revise the behavior.
this is ready for review?
this is ready for review?
yep. There are 'installed' labels or a few more features I want to add, but I think it would be better to do it in another pr. The search itself works well.