> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 22 November 2004 17:26
> To: Dave Page
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] RFC: Update wizard
>
> > That won't necessarily pick up typos of course. Can we
> utilise CVS for
> > this somehow, and use it's built in version numbering?
>
> Not directly. The binaries would be corrupted. In the rare
> case of typo
> fixes without count change the count could be increased
> manually. It's a
> kind of version number anyway. We could use the date too.
Why would binaries be corrupted?
> > That'll even allow segregation of major version updates
> using branch version numbers.
>
> We don't need that. A newer language file also covers
> previous versions.
Does it? You mean, if we remove strings from the source, they remain in
the po files after a merge? Seems kinda inefficient...
> > Have you thought about documentation updates?
>
> Um, no. No problem really, because we already can load the doc from a
> zip. Consequently, we should stop distributing single files, and
> distribute the zip only.
In that case then, why distribute the languages seperately?
> >>Questions:
> >>- How to inform the user about possible updates? MsgBox?
> >>Toolbar button showing enabled? Update check will be
> >>performed asynchronously, so it might pop up in the middle of
> >>something.
> >
> >
> > Status bar message with flashing icon?
>
> Annoying, if you don't want to update. Maybe non-flashing.
As I also suggested though, there should be an option to turn off
auto-checking on the options dialogue. But I could live with non
flashing.
> Or toolbar button, which changes appearance if download is available.
No, I don't think we should use the tool bar. It's there to allow the
user to control the application, not to provide feedback.
> The download dlg should be accessible even if no update was
> automatically detected, to enable manual triggered updates.
Yes, agreed.
Regards, Dave.
