View Single Post
Old 07-19-2016, 05:45 PM   #5
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
@wladdy,

The end result of that thread is simply: There will be no new datatypes at all.

"Calibre Companion" and all of the other 3d party software that interacts with Calibre might crash and burn if there were a new datatype.

Kovid and Chaley agreed that instead of adding the new datatype that I proposed, the current datatype of "comments" (long-text not shown in the tag browser) will be enhanced to have a checkmark in Preferences > Add Your Own Columns that says "plain text", and another that says "show with label in book detail view".

As you know, comments do not currently appear in the book detail view with any labels.

The intention is to make the datatype of comments be both long-text and short-text depending on the user's checkmarks in the new checkboxes when a custom column of that datatype is first created.

So, "comments" will become "text not shown in the tag browser". The type of text (html or plain) will be up to the user.


DaltonST

Last edited by DaltonST; 07-19-2016 at 06:06 PM. Reason: fix typos
DaltonST is offline   Reply With Quote