Plugin cannot be disabled

[BetterRed]

Originally Posted by JimmXinu

I suspect you mean someone else--I only just found this thread and I don't remember ever discussing it before.

I thought it came up in the to-and-fro we had about View Manager a long time ago.

Thinking about it now, I might be conflating it with: why do some toolbar/menu items have drop down glyphs whilst others don't have them -- e.g. Preferences & View Manager. You definitely explained the 'why' of that to me in the VM context.

BR

[Comfy.n]

Originally Posted by JSWolf

But could you not set the interface plugin to be disabled the next time Calibre is run?

if possible, that would be great!

much easier than going through the config folder and manually removing the PI

[chaley]

Originally Posted by JSWolf

But could you not set the interface plugin to be disabled the next time Calibre is run?

No, because of what Kovid said.

Originally Posted by kovidgoyal

user interface plugins cannot be disabled because the main calibre GUI is built from them. Disabling them would break it. One could of course allow disabling custom user interface plugins, but adding that is not worth the effort to me.

He is saying that disabling builtin user interface plugins will break calibre. No matter when they are disabled. He further says that solving the problem (detecting if a plugin is builtin or not) isn't worth the trouble.

(Apologies if I am putting words in Kovid's mouth.)

[Quoth]

Isn't there an option to start or reload Calibre without any 3rd party plugins?

[theducks]

Originally Posted by Quoth

Isn't there an option to start or reload Calibre without any 3rd party plugins?

Yes! It is on the Preferences Menu

[JSWolf]

Originally Posted by chaley

No, because of what Kovid said.

He is saying that disabling builtin user interface plugins will break calibre. No matter when they are disabled. He further says that solving the problem (detecting if a plugin is builtin or not) isn't worth the trouble.

(Apologies if I am putting words in Kovid's mouth.)

What's the difference between removing the plugin and disabling it (when Calibre shuts down)? In both cases, it would not be there for Calibre to build on the next time it's run.

[chaley]

Originally Posted by JSWolf

What's the difference between removing the plugin and disabling it (when Calibre shuts down)? In both cases, it would not be there for Calibre to build on the next time it's run.

We are talking about *builtin plugins*. These cannot be removed.

[JSWolf]

Originally Posted by chaley

We are talking about *builtin plugins*. These cannot be removed.

I was thinking plugins such as View Manager which cannot be disabled.

[chaley]

Originally Posted by JSWolf

I was thinking plugins such as View Manager which cannot be disabled.

I suggest you actually read the posts. Kovid said that he isn't interested in doing the work to detect disabling non-builtin plugins.

[BetterRed]

In Windows: to 'disable' a specific User interface plugin (e.g View Manager) try this:

1. open the Configuration directory by pressing the button in Prefs->Misc
2. open the plugins folder
3. tack .save on the end of the relevant plugin zip -- e.g. rename to View Manager.zip.save
4. restart calibre

To restore the plugin do that again, except in step 3 remove the .save.

I have File Explorer configured to show file extensions.

BR

[JSWolf]

Originally Posted by BetterRed

In Windows: to 'disable' a specific User interface plugin (e.g View Manager) try this:

1. open the Configuration directory by pressing the button in Prefs->Misc
2. open the plugins folder
3. tack .save on the end of the relevant plugin zip -- e.g. rename to View Manager.zip.save
4. restart calibre

To restore the plugin do that again, except in step 3 remove the .save.

I have File Explorer configured to show file extensions.

BR

Yes, that will work.

[Quoth]

Originally Posted by BetterRed

In Windows:
I have File Explorer configured to show file extensions.

GOOD!

First thing to do with a new laptop/PC or fresh install. Also disable EVERY sort of autorun.
I remember when Win 95 came out and CD autorun, I said "Didn't MS learn from the Amiga floppy autorun virus debacle?".

It's of course a major article / subject all the things that MS has on by default that should be disabled or uninstalled on logging in to a fresh install.