Good points.
Yes, this discussion only impacts epub3 users. A "Finalize" button or menu would not really be needed for an epub2.
If updating the epub3 manifest properties was cheap and fast, no worries but it needs to run in a bunch of threads concurrently to ask each html resource to check its contents and report back if it does specific things.
We just have to figure out the best place to make this happen once after all changes, thus my wish for some way of knowing when it would be a good time to do this for epub3.
Quote:
Originally Posted by Turtle91
A menu item that said something like "Finalize" or "Publish" or "Push this button as the VERY LAST thing you do on this ePub" would be fairly obvious. Newbs go through a fairly short/steep learning curve when they first use Sigil anyway. I don't think that kind of a button would be hard to understand.
I'm assuming these ePub3 auto-save functions would only be a factor if you are working in ePub3...these features wouldn't even be looked at if you were still in ePub2. When I finally get around to making the switch to 3, I would like the idea of having the "finalize/publish" button rather than an auto-save feature. There are already several buttons I push in the editing process when finishing the book: spell-check, css-cleanup, Generate TOC, epubcheck...really easy to add/replace one of those with a "finalize ePub3" button.
|