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

Persistent Catalog #22

Closed
egabrum opened this issue Mar 22, 2016 · 12 comments
Closed

Persistent Catalog #22

egabrum opened this issue Mar 22, 2016 · 12 comments

Comments

@egabrum
Copy link

@egabrum egabrum commented Mar 22, 2016

v2.3: When Keypirinha opens at start-up, completely rebuilds the catalog, ignoring the previous one.

My current catalog has about 6000 items. Currently, it takes about 3 minutes to rebuild the catalog. Applications and bookmarks are added quickly, but the rest is only available after those ~3 minutes.

This means that, for the first 3 minutes (the minutes that users normally use to open working documents), the vast majority of my catalog is not available and I have to open those files using other means, which beats the purpose of the launcher.

@polyvertex
Copy link
Member

@polyvertex polyvertex commented Mar 23, 2016

Do you need to have 6000 items in your Catalog?
EDIT: Also, if I take your other comments into account, should I assume that most of these items come from distant file system(s)?

@egabrum
Copy link
Author

@egabrum egabrum commented Mar 23, 2016

Let me explain my use case:
I very rarely browse/explore for files anymore. Not always, but in most scenarios I feel it's an outdated method to fetch and open files and folders.
I work with multiple shared (with many people) folders in different network drives. People store files in whatever structure they feel like, which depends on the person and even the mood of the same person in different days. Even I don't remember where I store some of my files. And I couldn't care less:

I have Launchy (progressively switching to KP, of course) cataloguing a wide range of folders with deep sub-folders. When I need something, I just query it. I don't need to bother to remember where it is or to create a link that breaks every time somebody moves or slightly renames a path. I often see people confusedly browsing for a file like an old lady looking for a candy at the bottom of her purse, while I open that file or folder in 2 seconds.

I use KP or Launchy instead of something like Everything because of the scoring system and other additional features, and because they allow me to limit the range of search. Everything is awesome, but for other purposes.

For example, in my current Launchy catalog, I have almost 35,000 items. Of course I only use a tiny fraction of them, but when I need something, it's there. Google indexes billions of pages. I'll only use a few hundred of them in my lifetime, but the beauty of Google is the range of search and the ease of access.

Of course, indexing 6,000 files takes some time. My issue is with not having the catalog available when I start the application.

#24 would help to alleviate things too.

I have spent time looking into the code, but it's well beyond my skill level. I don't want you to think that my attitude is: "Here, do this for me. For free". It's the prerogative of the developers to decide on the feature set.

@polyvertex
Copy link
Member

@polyvertex polyvertex commented Mar 23, 2016

Make sense. Well, considering Keypirinha's current design, implementing a persistent Catalog should not take too long... Granted for a future release!

@polyvertex polyvertex changed the title Previous catalog is scrapped at start-up Persistent Catalog Mar 23, 2016
@polyvertex polyvertex modified the milestone: catalog May 5, 2016
@polyvertex polyvertex modified the milestone: catalog May 5, 2016
@szaiser
Copy link

@szaiser szaiser commented May 10, 2016

I totally support this issue, my situation is exactly the same as that of @egabrum. Additionally, I have some kind of feature request, for which I also have to explain my usecase: I sync the portable installation of Launchy (and soon Keypirinha) across multiple computers via Dropbox. Of course, the catalogue (which is persistent in Launchy and soon will be persistent in Keypirinha) is different for every computer, as the files on it are not the same.

Would it be possible, to freely configure the location of the Keypirinha catalogue in the configuration file? This way, the configuration in the Keypirinha folder is synced and is identical on each computer, while the catalogue is not.

@polyvertex
Copy link
Member

@polyvertex polyvertex commented May 10, 2016

The persistent catalog will be machine-specific, which means a catalog file will be created for each machine somewhere under the portable/Local directory.

In other words, your request will be implicitly supported and all you'll have to do is to push-sync the whole portable directory to your DropBox (or the whole keypirinha install directory if you wish so), without having to filter out anything.

@szaiser
Copy link

@szaiser szaiser commented May 10, 2016

@polyvertex That sounds great!

@poisonborz
Copy link

@poisonborz poisonborz commented Jul 13, 2016

Any updates on this? This would be a much needed feature, and the primary reason I couldn't fully ditch Launchy yet :(
I have a number of network/container volumes that are loaded at will. Without enabling constant scanning, or manually reloading the catalog, items from App extra_paths are unavailable when those volumes are not mounted at the time of KP's startup. With a persistent catalog, KP could display those items too (maybe marking them with an "unavailable" icon on search) and launch them if the volumes are loaded.

@polyvertex
Copy link
Member

@polyvertex polyvertex commented Jul 14, 2016

Yep yep, it's on its way. No more pressure needed!
I can't say when, but you can already be sure it will be implemented so that's something :)

Meanwhile, I will value any technical input regarding any exotic use-case that is somehow related to this issue.

@polyvertex
Copy link
Member

@polyvertex polyvertex commented Jan 21, 2017

It's finally there, sorry for the long delay. It's implemented and will be available in the next release.
Also, just to confirm @szaiser's request will be supported because catalog files are created per-machine.
File format has been made as lightweight and optimized as possible.

@poisonborz
Copy link

@poisonborz poisonborz commented Jan 21, 2017

\o/

@szaiser
Copy link

@szaiser szaiser commented Jan 21, 2017

Thank you very much @polyvertex! You are doing a great job with Keypirinha, I love it.

@polyvertex
Copy link
Member

@polyvertex polyvertex commented Jan 26, 2017

Feature available in v2.10.

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

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.