Posts: 2,441
Joined: Mar 2010
Reputation:
54
jingai
Skilled Skinner
Posts: 2,441
I read through that thread, and personally I have to agree that this functionality belongs in an add-on, not in the skin itself.
Posts: 2,441
Joined: Mar 2010
Reputation:
54
jingai
Skilled Skinner
Posts: 2,441
People probably wouldn't accidentally enable it, but I still think it should be in an add-on and not a feature of each skin. The biggest reason is that since it's destructive by nature, it should be the same option in every skin. The easiest way to make it a global feature is to, well.. make it globally available via an add-on. That allows me to be absolutely sure that it's disabled everywhere by disabling/uninstalling it in one place, rather than switching to each and every skin I might have installed to disable it.
Plus.. why have all skin authors duplicate the work when you can put it in one place?
Posts: 2,416
Joined: Nov 2008
Reputation:
31
stoli
Skilled Skinner
Posts: 2,416
I have to agree features like this should be in an addon. Even then I don't think it should be developed at all. In nearly 20 years of software development I have always argued against any sort of instant automated deletions. It's just a disaster waiting to happen. When past clients pushed for features like this I would always point out how they could do it but never would I let my team do the work. I'd rather lose a client than have a bug delete the wrong data...
<soap box off>