On 19 Feb 2012, at 14:40, Nick Hall wrote:
> On 19/02/12 00:24, Tim Lyons wrote:
>> On 18 Feb 2012, at 23:41, gramps-devel-
>> request@... wrote:
>>> Looking at the options again, I don't think we need any changes.
>>> is already an option to just notify updates only. I have been
>>> using the
>>> defaults, and with an internet connection, I haven't had any
>>> problems at
>>> all. Most of the suggestions are just refinements to something that
>>> works well already.
>> Sorry, but I don't think it does work well enough already.
>> (1) If you don't have an internet connection, apparently start-up
>> hangs to 10 minutes. (I don't know this from personal experience
>> because I do have a connection, so this doesn't bother me).
> Did you read the first part of my email? Doesn't urllib2 provide a
> timeout parameter that will fix this bug?
I'm not sure that a timeout parameter would make any difference. It
seems that it times out after 10 minutes anyway (and if I understand
what has been written in the mailing list, this was actually changed
from 3 minutes, so could presumably be changed back to a smaller time
if wanted). The problem is that it does the check at all even on the
> For the future, I think that the non-GUI part of the code that
> checks for new updates should run in a separate thread.
>> (2) If you don't install a particular add-on the first time Gramps
>> starts and asks you, there is no way to do so later (unless the add-
>> on changes) because 'Check now' only checks for New and/or Updated
>> add-ons. This does affect me, because I didn't chose to install ALL
>> the add-on when I first started, so now there is no way to get at
>> the ones I didn't install. I think this is a real problem, and I
>> would love it to be fixed!
>> The Plugin Manager 'Refresh Addon List' didn't work at all when i
>> was running trunk. Now I am running gramps34 branch, it has started
>> working, but I gather that this looks in a different place from the
>> Preferences 'Check now', so presumably won't give the same add-ons.
> My own opinion is to keep the update code separate from the add/
> remove code. We should remove the ability to add new plugins from
> the update code.
Well then even more so should the initial update check on first run be
However, from the user point of view, having separate interfaces to
add new plugins and update existing ones is very confusing. Suppose he
decides to add a new plugin, and does it, but doesn't get told that
another existing (perhaps related) plugin is out of date. Or he
updates his plugin, but doesn't get told there is a new one that has
just been added to the repository.
> The Plugin Manager should be fixed so that we can add new plugins.
(You can add new plugins from the plugin manager, the only problem is
apparently where it goes to look for them). I was hoping that someone
who had already looked at the code would fix it, because I have not
looked at the code at all, and am just assuming how it works from what
has been said in the mailing list and how it doesn't work for me at
> In the future, it would be nice to enhance the Plugin Manager.
> Perhaps we could add pictures and descriptions of the plugins?