-
Notifications
You must be signed in to change notification settings - Fork 12
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
File association should be performed during installation #126
Comments
Just add a "use gtorrent by default" button in the settings, and make sure the .desktop files are registered with the package manager so they are uninstalled properly. |
The "use gtorrent by default" should be handled by the operating system or whatever file manager you use. e.g: in linux, I forgot to mention, we should have these files should be generated and placed during I'll see how it's done in other software, but I can't imagine it'd be much different. |
as a user i don't want to deal with mime types and whatever |
Ah, I should elaborate. What I meant though is that most xdg-compliant software will present you with a 'use as default' equivalent option whenever you are asked what program you want to open a filetype with. This achieves to the same effect as what You don't have to fuck around with mime types associations yourself, it should be arranged by the program that deals with the 'open with' part of the flow. gtorrent won't have to make itself a default for the bittorrent, that's up to the end user and how the operating system goes around with it. All that will happen is that gtorrent associates itself with the right filetype during install. Requests to make an application a default handler may be subject to system policy or approval by the end-user. |
Currently association is done in
gt::Platform::associate
where the files
~/.local/share/applications/gtorrentt.desktop
and~/.local/share/applications/gtorrentm.desktop
are created, generated and written.After gtorrent gets typically uninstalled by the casual user, these desktop entries remain behind, like unpleasant love marks.
The text was updated successfully, but these errors were encountered: