[democrite]

Now that 1.0 is released, I'm not sure what is to come. Typically I use Sigil mainly to convert to EPUB 3, edit the TOC, and for the page list plugin. Btw, editing of the EPUB such as re-ordering files does not seem to update the pagelist; perhaps as intended and not yet added.

For all other edits, on macOS, I tend to use BBEdit. It loads an EPUB much quicker as it does no parsing, and for typical post-creation edits as corrections, I find BBEdit more convenient as it is quicker to bring up global search and replace (a dedicated shortcut) and one can save commonly used (complex) regexes. I also like BBEdit since it doesn't rewrite the entire EPUB on save, and as such I can keep track of date last modified.

Some features that I think would be great:

1. some apps index headers, CSS classes, and perhaps other elements. IDEs typically allow one to navigate code such as going to a particular class, function, etc. It would be nice if there was some shortcut to bring up some search dialog and then be able to go to a particular header in any file. Refactoring such as renaming a class and having the change applied globally would be nice too. There seems to little other options of highly refined EPUB editors, BlueGriffon a notable example that I have tried, and I would very much like if eventually Sigil adopted some IDE editing and navigation features helpful for large code bases or EPUBs.

2. TOC editor. Somewhat often I find commercial EPUBs with a less than ideal TOC, with entries not being in the correct hierarchy such as all H2s being H1 (chapter at the same level as part). In such cases, it would be nice to multiple select and then change level. It would also be nice if there was some drop down in the TOC editor that could set level 1–6 expansion, e.g. collapse all save up to H2. Handy to view at a glance and navigate long TOCs that may have dozens or hundreds of entries. When changing the level of an entry, it too would be nice if the collapse/expansion state was kept rather than auto-expanding.

One last thing, perhaps it can be done by the plugin maintainer, it would be more convenient if when converting to EPUB 3, one could keep the file name and overwrite the existing file. Renaming and replacing is a few extra steps that would be nice to avoid. As there is now more complete EPUB 3 support, perhaps the conversion from 2 to 3, and perhaps the reverse in the possible case of someone might wanting such, may be better suited as built-in as it may be now more used and more so in the future.