Store Copied text to a ClipBoard

[Nishthajain7]

Terms

• [x] I have searched open and closed feature requests
• [x] I agree to follow Scribe-Android's Code of Conduct

Description

It would be useful to have a feature that tracks and stores the text copied by the user into a clipboard history. Now when text is copied using the system clipboard, it is lost as soon as something else is copied. Having a clipboard log in the app can enable retrieving previously copied text and displaying a history of the same. This could help users recall previous clipboard items within the app.

Proposed Solution

Provide a UI to show and reuse copied content Store copied text in a local database or in-memory list (limited to last N items)

[andrewtavis]

Thanks so much for the issue, @Nishthajain7! :)

[shrimpnaur]

is anyone working on this? if not then I would like to give it a try

[andrewtavis]

I don't think anyone has picked this up, so by all means, @shrimpnaur! Please let us know if you need any support :)

[shrimpnaur]

Hello @andrewtavis , sorry for the delay. I had a few doubts regarding the approach for this functionality. So I need to detect when users copy text, so should I use Android's ClipboardManager.OnPrimaryClipChangedListener in the GeneralKeyboardIME service? Is this the right approach, or is there a better approach for this

[andrewtavis]

@angrezichatterbox would be able to confirm better than I can, but using a default Android method within the GeneralKeyboardIME sounds appropriate to me. I don't think we should need a third party dependency to achieve the initial results for this issue. If we would need a dependency, then I'd assume that that would be for functionality that's not within the scope of this issue 😊

Thanks for checking in, @shrimpnaur! Looking forward to your work!

[angrezichatterbox]

Yeah that would be the best approach to do it. We would then have to store it somewhere and have a time period for it to be a stored. For Gboard it's a hour of storage from the minute the text is copied.

[shrimpnaur]

Hi! @angrezichatterbox @andrewtavis I'm planning to split this into multiple PRs: (1) data storage layer, (2) clipboard monitoring, (3) UI components, and (4) keyboard integration. Is this breakdown fine or is there a better split for this?

[andrewtavis]

From my end it makes sense :) Thanks for the thought your putting into this, @shrimpnaur!

[andrewtavis]

Hey @shrimpnaur 👋 @angrezichatterbox and I are discussing this in the sync now :) The idea we have so far would look like this:

[shrimpnaur]

Hey @andrewtavis @angrezichatterbox 👋 Sorry for the delay in following up, I had some exams recently and couldn’t continue earlier. I’ve started working on the clipboard history feature now that will let the app store and remember copied text instead of losing it each time something new is copied. This will create the base system that saves and manages past clipboard entries for later use. I’ll share progress updates as I go along. Thanks again for the design reference!

[andrewtavis]

Thanks for the update, @shrimpnaur! Appreciate you keeping us in the loop, and hope the exams went well! Please let us know if you need some support 😊