Quote:
Originally Posted by Starson17
If you can articulate an improvement, the bug tracker is the best place to suggest it. Even better, if you can write the code, do that.
|
What version of python is this developed with, or is any recent version good enough?
Quote:
|
However, I can't agree that just because many users are unfamiliar with the advantages of tags, Calibre should be redesigned to use another interface you may prefer (that so far you haven't articulated very clearly). Most users just need some help in understanding how well tags work to do what they want done.
|
I'm not saying that tags shouldn't be used. I'm saying that for some things, there should be some abstraction between the user and manually editing and searching for tags. In the example of workflow, and this is off of the cuff.. you could have right mouse context menus that let you pick a status of a book, and the GUI simply added and removed tags. You could have those user defineable under preference or have a set list. A less specific implementation of something similar could just be a right mouse menu of "quick tags" that would allow you to add or remove a tag that you set up as a quick tag. This would require 2 clicks though.. one to remove a tag and one to add a tag when it changed status. If there was a list of tags just used for status, when a new one was selected, the function could scan and remove any of the other status tags which would only require 1 click.
For filtering on the status, you could have pre canned category of searches that will find the various statuses. I think you'd also want there to be precedence in searches so if you selected to view all ebooks with a specific status, you could leave that view applied and either select another filter/search and/or enter something in the search bar.
Right now, someone is going to have to read up on the syntax of the search bar or scroll through all the tags. And if they decide to use the search bar, what's the likelihood of the average person remembering the syntax of a compound search statement two weeks from now when they try to use it again? What's the likelihood of them being able to quickly get what they want with a couple of clicks on a pull down menu?
You could apply the same type of automation to the people example or other things like weather someone wants to track if they've read a book or not. You could also make these menus user enabled in preferences so you don't have to see them if you don't want to.
I think the open nature of tags is great, but sometimes software needs to be more focused for the specific task at hand as well.