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

Added "My Clippings Path" preference to avoid having to find it manually each time #154

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fbmcipher
Copy link

Simple patch for #150

This patch adds a new preference to the plugin allowing the user to enter the path to their Kindle's My Clippings.txt file:

Screen Shot 2022-05-20 at 6 03 32 pm

The user initiates a sync like usual and chooses the "Upload My Clippings File" option. The plugin checks to see if the "My Clippings.txt" path is set in its settings and — if it is, the plugin continues using this file. If it isn't, or the plugin is unable to find a file at the specified path, a file open dialog is displayed as usual.

@hadynz
Copy link
Owner

hadynz commented May 23, 2022

Thanks for making this change.

My original preference for solving this was not exposing the new "file location path" as a preference so users are not given too much complexity to configure and look for a pure UX solution. However, I think this is a good step to solving this problem in the immediate term.

If you can just fix the linting issue, I'll happily merge.


private async myClippingsFileLocation(): void {
new Setting(this.containerEl)
.setName('My Clippings file location')
Copy link
Owner

Choose a reason for hiding this comment

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

Would this preference make more sense if it was called "Default My Clippings file location"?

@hadynz
Copy link
Owner

hadynz commented May 23, 2022

You will also need to manually bump the plugin version in order for it to be published as a new version. This needs to be done in manifest.json and package.json.

@smarquez1
Copy link

@fkyuga I know you must be busy but do you plan on updating this PR? If not, I'd like to tackle this feature sometime

@hadynz
Copy link
Owner

hadynz commented Nov 18, 2022

@smarquez1 I originally wanted to give the PR's author the opportunity to contribute a change to the plugin so I haven't implemented this myself. I will likely fix this myself once I am done with a new major feature that I am working on. In the meantime, if you would like to have a go yourself, by all means go for it. It would be a positive change for the plugin

@Warden20
Copy link

This feature would be awesome. do you plan on updating this PR?

@toropanov
Copy link

Yeah I also wait for that feature, any updates?

@Warden20
Copy link

Agree, it would be a good feature.

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.

5 participants