Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow caching on a per-app basis #29

Open
eugenesvk opened this issue Jul 8, 2023 · 0 comments
Open

Allow caching on a per-app basis #29

eugenesvk opened this issue Jul 8, 2023 · 0 comments

Comments

@eugenesvk
Copy link

Let's say there are two types of apps:

  • One with a huge a complicated menu, traversing of which on every launch would show a visible lag. It might be better to always use the cached version (with maybe manual reset on rare app updates) to get no lag (even though you might miss some dynamic menu items)
  • One with a small menu, where the lag is smaller than typing the menu item. In this case there is no point in using cache since it's imperceptible

Would it be possible to add a config that for some selected apps in the first category would allow setting custom cache option (always use if exists) with custom menu/sub-menu depth (you'd basically set each to ∞ since it's only used once per app and then cached)?
(maybe cache could be auto-invalidated when app version changes, but that might be an unnecessary overcomplication)

Another potential improvement to get the best of both worlds (caching and dynamic items): is it possible to parse the whole menu only once, but also store specific paths that are dynamic and on each launch only update those paths while reading everything else from cache?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant