Quote:
Originally Posted by kovidgoyal
@ficbot: Adding specific columns to meet specific demands will very quickly lead to chaos. Instead, at some point in the future I will add the ability for user to define their own columns.
|
I'm definitely looking forward to this.
You might want to consider the "source" column, though, because it would be of use to just about any calibre user who gets their books from more than one place. I've been using the "publisher" field for this, and using tags for publishers when they're important, but that's kind of bass-ackwards. Like many (perhaps most) ebook aficionados, I have my preferences in book sources, mostly due to their formatting, file quality, cleanup, etc., so I need to keep track of the source in order to make it easier to tell when I can replace a book from a higher-quality source. Unlike most other possible fields I could think of, this one really may be of enough universal benefit to be worth adding.
I know what you mean about the chaos, though. I feel for you. Years ago, I was selling some fairly popular software in a tiny niche market, and my users kept asking for more and more features to be added to its scripting language. I resisted for exactly that reason. If I'd extended it to incorporate every feature request, it would have ended up not only
harder to learn and understand, but huge, slow, and impossible to maintain. I'm big on general-purpose tools. You don't want to have to have a different hammer for every kind of nail.
In more direct reply to rchiav:
If I invited you over for dinner, would you criticize my food, my cooking, even my teacups (ignoring the shocked looks on the faces of the other dinner guests), and demand that I cook something special just for you? No? Then don't do it with calibre. We're all guests at Kovid's table. We didn't buy the food, we didn't cook it, and most of us aren't even helping with the dishes. If we don't like what he's serving, we can always go home and cook our own.