David wrote :
> On Tue, 14 Jun 2005 08:28:31 +0200, "Michael Vilhelmsen"
> <(E-Mail Removed)> typed
> furiously:
>
>>>
>>> Since you do not know, ahead of time, the level of your customers'
>>> knowledge and/or expertise you should always allow the choice.
>>
>> hmm - I partly agree with you.
>> But we have in our company taken this aproach.....
>> Since the use in our program has to call a specific funktion in our program, he (or she) only does this KNOWING whats he his doing.
>> He is given some warnings, and if he continue, there is no going back.
>>
>> So the user has a choise. But after saying Yes, I will, he has no more to do.....
>
> 30MB here, 30MB there, before you know it you have 300MB or 3000MB
> cluttering up your C: drive. Sheesh! I remember when my machine only
> had two 360KB floppies. My first hard drive was a whopping 5MB.
It will always only be 30Mb.
Next update will overwrite the prior backup.
So never more than 30 Mb.
>
> Since the C: drive is the main drive used, and often the only drive in
> most systems, programmers have developed the bad habit, in my opinion,
> of dropping everything onto that drive and don't care that it may be
> the smallest drive in the system or, at least, not the only drive. By
> ignoring the desires of the user your software can be found less
> desirable and so sales suffer.
True.
But the main part of our users are not very good at using Windows (and that putting it mildly!).
Its not unlikely, that when I talk to the user, I tell them to press the START button.
They do not not what I'm talking about.
So I'm stuck between given the user as much freedom as preferable, and still have users with little knowlegde being able to use the system.
The reason to making a backup at all, is that we actually have had customers who manage to delete, alter or other things the main files of our program.
And it is easyer to restore files, when a backup is available !
And also - some of our users don't even have an internet connection. Not even a dial up !
So give them an update can only be done by sending a CD.
Hence the backup.
>
> If some one foisted such a program on me it would, likely, not remain
> on my system for very long. I track every installation and check both
> files and registry entries. If I find too much going onto the C:
> drive, without my OK, then I am probably not going to bother with that
> program again.
Here - personally - I'm of the same opinion.
But the fact is, that the main part of the users really don't care.
The program should just work.
And if it dosn't we shall just fix it. Preferable yesterday!
So as I see it, its a very fine walk between letting the user having a choise, or making my life as developer and supporter easier.
That said, I agree with you, that a program, should not fill up any drive with just temp. filer, backup files or any other things without cleaning up. At least every once in a while....
Michael
--
Best Regards / Venlig hilsen
Michael Vilhelmsen
This is an automatic signature of MesNews.
Site :
http://mesnews.no-ip.com