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

Feature Request: User Defined Location for ThunderLink Settings #8

Open
EnigmaSolved opened this issue Oct 2, 2013 · 2 comments
Open

Comments

@EnigmaSolved
Copy link
Contributor

(This is continuing a dialog begun via email.)

Basically I would like the same functionality as the Clippings extension for storing the ThunderLink settings in a custom file that I can then sync between machines.
Clippings Example
Also relevant:
http://clippings.mozdev.org/faq.html

@poohsen
Copy link
Owner

poohsen commented Oct 15, 2013

I looked at the Clippings extension. That filepath dialog really isn't a big deal. The problem lies in the data storage. Clippings stores it's clippings in RDF files so they can be saved in different locations easily.
Currently, all ThunderLink data is persisted via preferences. And that subsystem doesn't lend itself to changing of locations, afaict.

@EnigmaSolved
Copy link
Contributor Author

Clippings stores it's clippings in RDF files so they can be saved in different locations easily.
Currently, all ThunderLink data is persisted via preferences. And that subsystem doesn't lend itself to changing of locations, afaict.

Yeah, I would guess that RDF is the way to go if possible. But I have no idea if that involves a bunch more work for you though.

Also, I realized that I may not have been clear in my overall suggestion/recommendation about using/reusing as much of the Clippings GUI as possible. It is simple while being very functional, and does much of what some of my feature requests are wanting. I added an image for reference in another thread: #3 (comment)

You're doing all the work though, so I totally understand you'll need to prioritize. :)

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

2 participants