Thread: Plugin Removal
View Single Post
Old 04-25-2015, 08:33 PM   #5
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,758
Karma: 30237526
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by DiapDealer View Post
I just don't see a lot of incentive for someone to spend time creating what—at best—would essentially be a "check here to maybe/sorta cleanup some extra files this plugin may have created ... or not" box.
I don't want to belabour the point - but in my imaginary pseudo C implementation, the question to the user would be raised by the PI not by the framework.

The framework would have

Code:
removePlugin(pluginSelected)
{
    ...
    if (pluginSelected.removalCleanup != null)
        pluginSelected.removalCleanup();
    ...
}
The plugin would have

Code:
removalCleanup()
{
    ...
    if (askQuestion("Remove the dross?") == true)
    {
          remove myJsonFile();
          remove myHelpFile();
          ...
    } 
    ...
}
But clearly it's not going to happen, so as my great grandfather would say... san fairy ann

BR
BetterRed is online now   Reply With Quote