I've already written a tiny extension which does just that.
Sorry for the double post.
Cn somebody delete the first one?
I'm talking about an extension, which users can turn on and off. An extension should never compromise the data in the database, especially when it's not data created by the extension. An extension, when disabled, should leave the board as though it were never there.Dragosvr92 wrote: ↑Thu Dec 17, 2015 8:45 pmVSE, If you want to remove them, you just do it, knowing you cant get them back.
I dont see what is so destructive if you dont give any relevance to the data. It is like throwing something you dont need to the garbage. You make sure you dont really need it, before throwing it.
First all extensions can accommodate any style as long as its author chooses to provide styling for other styles when necessary. If you don't want to use some of the features of an extension, don't use them. If they can't be avoided, then that extension is not right for you, or ask the author if they could implement ways to make such features configurable.Dragosvr92 wrote: ↑Thu Dec 17, 2015 8:45 pmMany extensions have to be edited to make them compatible with your style. Or to remove features you dont need out of it.
If the user knows what they are doing, i dont see whats wrong in that. If they want support, they can revert to the stock files, or kindly ask if the dev wants to help or not.