Quote:
Originally Posted by BetterRed
So, its better that thousands of users change the "Column Header" value on their "#pages" custom columns, rather than one developer change the "Column Header" value on the "pages" built-in column.
|
BetterRed, and anyone in this debat, I undertstand your disapointement, but what solution do you propose? What name should the built-in Calibre page count column have? A relatively explicit, clear, and concise name that contains a
Pages Count?
And above all, what
serious issue you want to solve by?
Until now, excuse me for this lack of politeness, but your best argument was
Quote:
|
Their is two column named "Pages" in my library. Please fix this for me.
|
That's not an argument, it's an opinion.
Because, at no point you did raise
real and
serious issues that was more greater than "annoying".
So we could argue that of because of the Pages Count plugin, their is a lot of librarys that already contain a "Pages" column...
But that's not enough. Because it's far too easy to rename a custom column create by the user to reflect their real use of it.
Okay right, that annoying, that need a bit work from the user that fall in this situation, but that the better we can do.
So, unlike you proposes a real solution, a solution that will be discussed and may or may not be accepted, you words are not matter.
In addition, we do not know the actual statistics on the number of people who have installed the Pages Count plugin, or even less the people that use a column named "Pages", but thousands of users on the
2,000,000 calibre one? That less than 1%. Thousands seem a lot, but on a more wider view, is not enough affected user to realy start to envisaged to rename it on something else. And a warning on the changelog will be good enough.
Unless someone puts real arguments and real issues tha matter on the table, I consider the subject of the namming of the Calibre Pages closed.