View Single Post
Old 10-25-2021, 12:43 PM   #1
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,873
Karma: 6120478
Join Date: Nov 2009
Device: many
Possible To-Do List for Future Sigil Releases Post Sigil 1.8

For those interested ...

Here is a list of possible To-Do items for future Sigil releases.


Under consideration for future Sigil releases
  • - Add Indicator in Status Bar if epub in old Sigil "Standard Format"
  • - Add some form of templating supported for HTML TOC and Index generation (but maybe better by plugin)
  • - Multiple paragraph justification setting via the CV alignment icon (although PageEdit does this now)
  • - Add a regex to be used to build TOC when no headings tags exist (considering but this is against accessibility)
  • - Add GetInfo dialog to BookBrowser to add/change Semantics and Manifest Properties on a File
  • - Add sorting of Validation results by bookpath and error message
  • - Add export of Validation results to csv
  • - Update to version 2 of the C regular expression library
  • - Add checkbox to limit search replace to be outside tags (and add to Saved Search controls)
  • - Add CSSToolbox and GUI to help users create, manipulate, and merge multiple css stylesheets/selectors
  • - Update gumbo parser with recent WhatWG changes
  • - Add case-sensitivity checkbox for Spellcheck filter

If you have other ideas that you feel would benefit MANY users that would NOT be better as plugins, please let us know.

FYI:

Based on ideas from Tex2002ans, over the last month or so I have been working offline of a CSSToolbox codebase to act as the backbone for a GUI tool to:
  • - merge selectors across separate css stylesheets
  • - convert script tags into external stylesheets
  • - convert inline-styles into an external stylesheet
  • - delete selectors from a stylesheet
  • - rename class selectors in stylesheet and then updating all html code that uses it
  • - strip out a set of properties across all selectors and stylesheets
  • - compare two selector property lists to find matching selectors across stylesheets
This is still a long way from fruition but will hopefully help people who work with epubs that have separate but near duplicate css stylesheets (one per chapter) as might be produced by In-Design.

Last edited by KevinH; 10-25-2021 at 06:34 PM.
KevinH is online now   Reply With Quote