Flow.Launcher
Flow.Launcher copied to clipboard
[Feature Request] Time in Query box
Problem
As a user who hides the Start menu I want quick and easy access to the time. I tend to use Flow to launch applications and shortcuts a lot, and it would be super convenient to have the time in the query box for quick, at a glance (essentially) access to the time.
Proposed Solution
Time tastefully embedded in the query box (configurable in Settings).
Alternatives
- Just hitting Windows to bring up Start -> even on relatively powerful device this is super slow
- Having some kind of dedicated app just for this -> see ms wasteful, also haven't been able to find a particularly good one
- Use the timestamp plugin (ts) -> Often I want to actually run a command at the same time as seeing the clock. So then I would have to type "ts" and then delete that and type the command I actually want
Performance Impact
There is no perceived performance impact for this feature - it changes the control structure of the query box slightly, adds a Label
and a single OneWay
binding and property update callback on invoke. The clock will not update while the query box is visible, only on invoke (to reduce the overhead of introducing a ticking timer).
Screenshots
time in the collapsed query box
time with results
toggle to enable / disable time in Settings
Actually I like it. I'd place the icon to the right though.
@onesounds I remember you have done some theming around this, can you PR it when you get some free time?
@Garulf I looked at placing the icon on the right but then the clock interferes visually with long commands since they run into it (even with padding it looks a bit weird).
I played with this a bit more, interested in hearing preferences:
time to the left of the text
time to the left of the clock, with longer text
Another addendum to the feature that I could see people asking for is date, akin to Windows allowing you to squeeze date into the clock:
time with date
At which point, though, Flow would definitely need to expose some kind of date formatter, though folks may want that anyway (12hr vs 24 hr clock).
I still wonder is it possible to make this extendable with plugins? Although i think it may be somewhat hard, but it's interesting to allow plugins to provide this kinds of information like time, whether, etc.
@Garulf I looked at placing the icon on the right but then the clock interferes visually with long commands since they run into it (even with padding it looks a bit weird).
Oh in my mind I assumed the clock would disappear once text was entered.
@Garulf I looked at placing the icon on the right but then the clock interferes visually with long commands since they run into it (even with padding it looks a bit weird).
Oh in my mind I assumed the clock would disappear once text was entered.
If that's the case, maybe we can display it in the results list panel when query is empty? So that we can reuse the current results system.
I quite like the simplicity of showing results in the list panel - it could basically be keyed off a parameter on plugins that users could select to say "show default value" and they get populated and then cleared when the user starts typing.
The downside is that this will not work with the current default setting of Select last Query
(for Last Query Style
).
The other alternative is a UX plugin model where XAML producing plugins can provide small XAML snippets that are embedded (serially?) into a specific portion of the launcher. They can disappear, or not, when typing.
The other alternative is a UX plugin model where XAML producing plugins can provide small XAML snippets that are embedded (serially?) into a specific portion of the launcher. They can disappear, or not, when typing.
Yeah that's cool, but the issue is how to arrange them.
https://github.com/Flow-Launcher/Flow.Launcher/discussions/717
This work was done once before and There is already a working version..
- Someone needs to check my code. (The clock eats up the process.)
- It has also been talked about plugins. (Example:Weather) but I think we would better make it without much consideration.
Anyway, I'll work on it.
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.