[chaley]

Originally Posted by BetterRed

This one:

Attachment 212910

AFAIK: It's is only accessible a) if you have some unused space in the Tag Browser window, and b) via the use of a right button mouse click.

Thanks.
At the moment that context menu shouldn't be fully removed. It is possible to 'hide' all categories in the tag browser, resulting in an empty space. At that point the only way to show some category is to go to Preferences / Look & feel / Tag browser and check at least one category. The context menu for that category will have the "Show category" context menu where you can select other categories.

I think the other two, Change subcategorization scheme and Expand, could be removed. I'm not yet convinced it is worth the trouble or resulting confusion.

I see it as historical clutter*. In early calibre the Manage category menu could only be accessed via what was then the "Alter Tag Browser" button. It is now available via Toolbars and menus, and via a keyboard shortcut (I have it in the Book list context menu and via Ctrl+Shift+C); in addition individual category dialogues are available via the category item context menus in the Tag Browser and Book details.

So removing this clutter is worth annoying users that expect to find it there? It is there by default, no toolbar or context menu adaptation necessary, so I expect that many people do use it.

*Likewise: the Create catalogue in Conversion… I would scrap it too.

This I don't agree with. It needs to be somewhere by default so that a user can be directed to it. Between enhancement requests and forum posts, I think we get a question weekly about how to make a catalog, in particular CSV ones. Having "All GUI actions" somewhere by default would solve that problem.

I was about to suggest scrapping the Layout button in the status bar but I have a better idea - put Preferences in the status bar and remove the "Preferences must be in the main toolbar or menu" restriction, and put your All GUI actions there too.

This is another example of "It it isn't there it isn't anywhere."

Added: But Preferences, Layout, All GUI actions would be still available in Toolbars and menus and Keyboard shortcuts as they are now… and why not Jobs too.

Interesting idea. EDIT: I took a quick look at using the status bar for general tool buttons such as preferences and all gui layouts. It isn't easy, to the point where any benefit exceeds the work required. It isn't clear that it is even possible without major surgery to put an action-based item (preferences etc) on that toolbar. "Layout actions" was done in reverse: the action code uses stuff deep-down in calibre's initialization to implement the action. I was wrong. Adding permanent action-based buttons to the status bar is straight-forward.

I'll think further, but one fundamental rule for me is that something that is "there by default" today must still be "there by default" tomorrow, not requiring the user to add an action to something. Moving things around might be reasonable but would incure a cost for everyone used to where the "thing" is now. Of course, Kovid would make the final decision on any of this.