On 6/9/07, Richard Gaskin <[EMAIL PROTECTED]> wrote:
The Internet connection part of the equation is already in place, and no changes are proposed for that. The only thing proposed was that the program trigger that check once after startup. If there is a problem with the specifics you mentioned (firewalls, proxies, timeouts, etc.), those are not related to this proposed minor feature, but are part of the existing "Check for Updates" feature. If you've experienced problems running that you might consider submitting a BZ report outlining those so they can be addressed.
Richard, You of course are correct. But, the problem with automatic check for updates, is that it CAN create problems when the user least expects it. When explicitly chosing a menuitem "Check for Updates", a user understands the context of what is about to happen (or not happen). Launching Rev and have it hang for a series of moments, or provide a message after a 30 second timeout, IMO, only creates more opportunity for user dissatisfaction, more support tickets, etc.. My advice was to only to KISS. In fact, KISS is/was the mantra behind MC, right? I suppose I would accept a feature like the one you propose if a suitable interface could be created and the feature turned off by default. The suitable interface, IMO, would not be a silent try/failure/succeed, but rather a window popping up and telling the user what is about to happen, then going off and looking for updates and reporting back. Come to think of it, why not just put in IN RevOnline? best, Chipp _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
