View Single Post
Old 12-17-2020, 07:35 PM   #57
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by BeckyEbook View Post
What am I missing?
  • The ability to rename files in BookBrowser via plugins.
Explanation: I KNOW this requires checking all linkages to every other file, but since Rename in the GUI does this all the time, the plug would do it too.
The gui does it by invoking a large amount of code in SourceUpdates that handles searching for and updating any links all using multiple threads.

The plugin interface is a file based interface and can not callback to invoke that code. So all of that code would need to be duplicated and rewritten in python and then maintained in parallel for all future versions.

Quote:
  • Ability to enable/disable adding Sigil version to metadata in the OPF file.
Explanation: I would not like to offend the creators and developers of Sigil with this proposal, I simply express my subjective opinion. I am proud to use Sigil, but like having clean metadata. Theoretically, the output plugin could help, though invoking a plugin and simply hitting "Save" makes a difference.
Most software : Word, Excel, PDF, etc includes metadata on what software created it and modification date and time. Sigil deserves the same respect.

With your skills you could easily comment out the offending lines and make your own builds. I think you regularly do that anyway, right? It is just metadata. There are plugin approaches that can do this quite easily too.

Quote:
  • Templates for the table of contents/index.
Explanation: I mean the possibility to "build" a different layout, because the current one has a hardcoded <div> structure, even if I adapt it to my needs, another TOC refresh will restore the default layout again.
This is where a plugin could help, if there was a function that would give the TOC/index "ingredients" to styleaccording to the current table of contents settings, including "sigil_not_in_toc", "sigil_index_marker" etc. Sure, you could write a plugin to do the table of contents in a different form, but the plugin would do 99% of what Sigil is already doing, adding only the final layout of the TOC.xhtml file.
There are already stylesheets you can add to help refine how things are displayed. So I am not sure exactly what you want to change in your "styling". Please generate a complete list of the aspects of the html toc that would need to be changed so that I have some idea of how to modify the creation code to handle those options.


Thanks.
KevinH is online now   Reply With Quote