From: Nick H. <nic...@ho...> - 2013-09-29 16:00:42
|
Tim, I understand what you are trying to achieve, but I don't like your proposed solution. There are some bugs already reported about the add-ons system. It could do with some enhancements, but they can be done later. We need to solve two immediate problems: 1. The warning messages when a dependency is not met are not clear at the moment. 2. Subsequent warning messages cannot be suppressed. Adding options to the preferences was not a neat solution. A simple warning dialog will solve the problem for 3.4 and 4.0 with very little change to the existing code. Nick. On 29/09/13 16:46, Tim Lyons wrote: > Sorry, Nick, I realise that I am just repeating myself, but you do ask 'why > not just...' and I do have a reason why not. > > > > Nick Hall-6 wrote >> Why not just display the warning in a dialog? We could have two buttons >> - one to cancel the message and another to hide the plugin. If the user >> decides to hide the plugin then they won't see the warning again. > The problem is that the user has to learn two different things: > (1) how to use the preferences 'Check Now' to load the plugin in the first > place. > (2) how to use the Plugin Manager to unhide the plugin when he want to see > the message again or get the plugin after he has installed the dependency. > > I want to arrange that the user only has to learn one thing. > > With most software (e.g. Firefox 3.6.28 is what I have), you only have to > look at the Add-ons dialogue. If the addon is not compatible, I expect it > either won't be offered or won't be installed. The same Add-ons dialogue > will allow you to do the same thing again. > > What about storing the dependencies in the listing file so they can be > checked before the add-on is offered (incompatible add-ons could be greyed > out). > > Import/export addons are already a problem if there is an error in the > plugin, it just says the the extension (e.g. .ged) is not recognised one has > to look at the Plugin Manager to see why (OK in my case it's a syntax error, > which would not occur in the released product, but you get the idea). It > would be better if selecting that particular import or export (either > manually or by the relevant extension) produced an error explaining what to > do. > > Regards, > Tim. > > > > -- > View this message in context: http://gramps.1791082.n4.nabble.com/Options-to-suppress-warning-messages-tp4662755p4662801.html > Sent from the GRAMPS - Dev mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |