View Single Post
Old 01-05-2019, 06:23 PM   #17
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
EM Version 1.0.4 now can create "icon with text" "Entity Type Column" "has" "Value" rules using entities.png as the icon.

I have no conceptual problem with adding new rules, since EM is using the Preferences > Look & Feel > icon rules dialogs "behind the scenes" to do all of the work so that Calibre cannot tell the difference between an EM-created rule and a human-created rule.

However, removing existing rules is not something I am comfortable with. Not at all. So, "orphan" rules that will no longer be used because the underlying Entity was deleted from Calibre's metadata are an issue for a human to rectify manually.

Also, given the labor-intensive nature of manually creating rules for other-than-EM, I am going to have EM stash multiple back-up copies of existing rules in an export-format file. Probably in "...\calibre\plugins\em_data\".

After reflecting on the "@" symbol, Version 1.0.4 of EM will automatically convert all existing EM data from "@" to "~", and the ToolTips etc. have been changed to reflect the "~" tilde. That is because I may want to create "real" @User Categories for each EM Entity Type having existing Entities of that Type along with their Values underneath in the Tag Browser, and I don't want any ambiguity about that tentatively possible future functionality that may or may not ever exist.



DaltonST
DaltonST is offline   Reply With Quote