Re: winemenubuilder - MIME type handling GSoC - bad idea
On Sun, 15 Mar 2015 16:03:21 +0100 Michael Müller <michael(a)fds-team.de> wrote:
Maybe Rosanne can share her opinion on this topic, since she has more contact with users complaining about this "feature".
I'm not the least bit qualified to say what would or wouldn't be a good GSoC project, but if you're asking whether I think users would benefit from adding elaborate controls to winecfg that duplicate functions already provided by the desktop environment's tools, the answer is no. I agree with Damjan that those settings should be controlled through the host system, not Wine, and users need to learn how to use the configuration tools provided by their DE. I also see a significant downside to trying to control mimetype associations in winecfg: configuring would have to be done individually for each and every wineprefix. That's more work, not less, and speaking as a user with multiple wineprefixes, a headache I'd rather not have. As for bug 19182, the OR never asked for the complicated controls people have been proposing lately; all he wanted was a user-friendly way to completely disable mimetype associations and menu entries. A simple checkbox on the desktop integration tab to disable winemenubuilder would accomplish that.
On Tue, Mar 17, 2015 at 1:04 AM, Rosanne DiMesio <dimesio(a)earthlink.net> wrote:
On Sun, 15 Mar 2015 16:03:21 +0100 Michael Müller <michael(a)fds-team.de> wrote:
Maybe Rosanne can share her opinion on this topic, since she has more contact with users complaining about this "feature".
I'm not the least bit qualified to say what would or wouldn't be a good GSoC project, but if you're asking whether I think users would benefit from adding elaborate controls to winecfg that duplicate functions already provided by the desktop environment's tools, the answer is no. I agree with Damjan that those settings should be controlled through the host system, not Wine, and users need to learn how to use the configuration tools provided by their DE. I also see a significant downside to trying to control mimetype associations in winecfg: configuring would have to be done individually for each and every wineprefix. That's more work, not less, and speaking as a user with multiple wineprefixes, a headache I'd rather not have.
As for bug 19182, the OR never asked for the complicated controls people have been proposing lately; all he wanted was a user-friendly way to completely disable mimetype associations and menu entries. A simple checkbox on the desktop integration tab to disable winemenubuilder would accomplish that.
I'll have to check to make sure, but I suspect disabling associations is harder than that, as associations for programs internal to Wine (eg. notepad) get created during the initial wineprefix creation or (at the latest) the first time any application (even winecfg) is run, meaning it would be too late to uncheck a checkbox in winecfg afterwards. Instead, it might be possible to ask the user the same way we ask for Gecko and Mono - that hopefully happens early enough. Regards Damjan
Hi, On Tue, Mar 17, 2015 at 9:20 AM, Damjan Jovanovic <damjan.jov(a)gmail.com> wrote:
I'll have to check to make sure, but I suspect disabling associations is harder than that, as associations for programs internal to Wine (eg. notepad) get created during the initial wineprefix creation or (at the latest) the first time any application (even winecfg) is run, meaning it would be too late to uncheck a checkbox in winecfg afterwards. Instead, it might be possible to ask the user the same way we ask for Gecko and Mono - that hopefully happens early enough. I woudn't like wine to ask me after each `make install` whether I want to enable this for each prefix I try to use — in addition to already annoying (but simple to avoid) Mono and Gecko dialogs.
Regards Damjan
Regards, Ruslan
On Tue, Mar 17, 2015 at 1:04 PM, Ruslan Kabatsayev <b7.10110111(a)gmail.com> wrote:
Hi,
On Tue, Mar 17, 2015 at 9:20 AM, Damjan Jovanovic <damjan.jov(a)gmail.com> wrote:
I'll have to check to make sure, but I suspect disabling associations is harder than that, as associations for programs internal to Wine (eg. notepad) get created during the initial wineprefix creation or (at the latest) the first time any application (even winecfg) is run, meaning it would be too late to uncheck a checkbox in winecfg afterwards. Instead, it might be possible to ask the user the same way we ask for Gecko and Mono - that hopefully happens early enough. I woudn't like wine to ask me after each `make install` whether I want to enable this for each prefix I try to use — in addition to already annoying (but simple to avoid) Mono and Gecko dialogs.
Yes I've already realized that. The idea would be a single dialog for Mono, Gecko, menus, associations, etc. Damjan
On 17.03.2015 14:04, Ruslan Kabatsayev wrote:
Hi,
On Tue, Mar 17, 2015 at 9:20 AM, Damjan Jovanovic <damjan.jov(a)gmail.com> wrote:
I'll have to check to make sure, but I suspect disabling associations is harder than that, as associations for programs internal to Wine (eg. notepad) get created during the initial wineprefix creation or (at the latest) the first time any application (even winecfg) is run, meaning it would be too late to uncheck a checkbox in winecfg afterwards. Instead, it might be possible to ask the user the same way we ask for Gecko and Mono - that hopefully happens early enough. I woudn't like wine to ask me after each `make install` whether I want to enable this for each prefix I try to use — in addition to already annoying (but simple to avoid) Mono and Gecko dialogs. Mono/Gecko dialogs should only appear on package change, otherwise cached package should be used. I don't see how it's annoying considering that mono/gecko don't update too often. Associations are completely different business, I can see why user might want to disable them, but regular user should not disable gecko/mono installation - it's implementation detail that user is not supposed to care about. So gecko/mono vs associations are things of different levels completely, and I don't think that we should a) allow to easy disable those additional packages and b) if it's decided to do so, it makes no sense to put this option any closer to associations.
Regards Damjan
Regards, Ruslan
I'll have to check to make sure, but I suspect disabling associations is harder than that, as associations for programs internal to Wine (eg. notepad) get created during the initial wineprefix creation or (at the latest) the first time any application (even winecfg) is run, meaning it would be too late to uncheck a checkbox in winecfg afterwards. Instead, it might be possible to ask the user the same way we ask for Gecko and Mono - that hopefully happens early enough.
I would much prefer that we have sane defaults, i.e. don't export Wine's default associations for file formats that aren't Windows-specific (.txt files). For Windows-specific formats, it's probably better to put those in wine.desktop as well, which simplifies the rule.
On Tue, 17 Mar 2015 11:02:28 -0500 Vincent Povirk <madewokherd(a)gmail.com> wrote:
I would much prefer that we have sane defaults, i.e. don't export Wine's default associations for file formats that aren't Windows-specific (.txt files).
I agree.
participants (5)
-
Damjan Jovanovic -
Nikolay Sivov -
Rosanne DiMesio -
Ruslan Kabatsayev -
Vincent Povirk