8000 Filter by app names by caetano-dev · Pull Request #56 · jasonjmcghee/rem · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Filter by app names #56

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

Merged
merged 6 commits into from
Jan 5, 2024
Merged

Filter by app names #56

merged 6 commits into from
Jan 5, 2024

Conversation

caetano-dev
Copy link
Contributor

This pull request adds a feature that lets the user choose a given app to search by adding a !<name> prefix.

Copy link
Owner
@jasonjmcghee jasonjmcghee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if the app name has a space like "App Store"- can you do !"App Store"?

@caetano-dev
Copy link
Contributor Author
caetano-dev commented Jan 3, 2024

Damn, I had not thought about that!
It will search only for the first word after the !

Maybe letting the user search for !app-store or !"App Store" could be a fix? Or maybe rethink the way we make this filtering.

Capture d’écran 2024-01-02 à 21 27 06

@jasonjmcghee
Copy link
Owner

I bet !"two words" is fine for now, but ideally we'd have a separate sql table of unique application names that we could retrieve from and have a dropdown filter

@caetano-dev
Copy link
Contributor Author

I added a dropdown filter next to the search bar and reverted the changes to search with !.

The apps shown in the menu are updated according to the user's data, meaning that if the user opens a new app, it will be added to the menu, and if the user deletes all their data, the menu will only show "All apps".

rem.picker.demo.mov

Copy link
Owner
@jasonjmcghee jasonjmcghee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll approve as this is great and immediately useful, but I would use the suggested approach of a table for unique application names. The current approach needs to do a full scan and that will get slower and slower as users record more and more.

You'd want the code you have anyway as there will need to be a check, "if unique application names table doesn't exist seed it with distinct application names".

The other question I'd ask is how much effort a searchable drop-down would be? Users could easily have hundreds of apps.

Regardless both can be future work.

@jasonjmcghee
Copy link
Owner

On second pass, when does getAppFilterData get called? Only on initial creation? If I close search and use a new app and reopen it, will it show up?

@caetano-dev
Copy link
Contributor Author

Yes. If you close search, open a new app and search for it again, it will show up.

I am working on the new database table for unique app names. I am testing it and will push the code soon. I hope it addresses the possible performance issues.

@jasonjmcghee
Copy link
Owner

Awesome - happy to merge this as is, and you can open a second pr!

@caetano-dev
Copy link
Contributor Author
caetano-dev commented Jan 3, 2024

Before you merge: I noticed that after stopping the first screen recording and starting a new one, the new frames only show up after searching for something. Do you know if this is something that had already been happening before?

@jasonjmcghee
Copy link
Owner

When you open search / timeline it pauses the recording and processes what it's seen so far. It might be the case that we aren't calling the retrieve results again automatically when new frames come in and/or not showing frames that don't yet have a thumbnail.

Either case I don't think you introduced the behavior. But if you want to confirm, you can try on main branch!

@jasonjmcghee
Copy link
Owner

@caetano-dev want me to merge this first, then #62 ? Both are looking good!

@caetano-dev
Copy link
Contributor Author

Sure, you can do that!

@caetano-dev
Copy link
Contributor Author
caetano-dev commented Jan 4, 2024

Please, also try to test the changes in your machine before merging with the main branch.

It is working for me, but the more people test it, the better.

When testing #62, maybe you will need to purge the data to ensure the new table is created.

@jasonjmcghee
Copy link
Owner
jasonjmcghee commented Jan 5, 2024

Couple of small tweaks to make proper spacing for the search, and added a border for better visibility.

I'll add them after merging!

image

@jasonjmcghee jasonjmcghee merged commit 2eae791 into jasonjmcghee:main Jan 5, 2024
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

Successfully merging this pull request may close these issues.

2 participants
0