Quote:
Originally Posted by Thasaidon
There need be no cursor syncing when switching modes. It is this syncing which has been said to cause many problems.
|
Allowing an either/or mode would still entail a massive overhaul of the codebase and would introduce even more complexity and more bugs. We've just achieved some stability after a major overhaul and would rather not have to do that again for a while.
It's not so much "synching" that's the problem (though I know I introduced the term). It's cursor position (knowing
where the cursor is being placed in the "real" document (html) when editing in the rendered Book View text, and elements that can't survive (or exist) when turning that rendered Book View text back into html. Most of this is handled by Qt, by the way. Meaning we're basically at the mercy of its bugs and quirks.
But so far, we've been able to introduce limited epub3 support (and keep working to add more) without needing to sacrifice Book View editing. So unless we smack into an insurmountable obstacle, there will be no push to remove Book View anytime soon (if ever). Just so long as people understand that continuing to make extensive edits in Book View will eventually bite you in the ass (even if you're very careful). It's just the nature of the beast.
I, personally, am uncomfortable promoting Sigil as a WYSIWYG editor when I can't, in good conscience, recommend that anyone actually
use the WYSIWYG interface for editing. I get tired of providing support that basically consists of, "don't do that in Book View." It's not a real answer (even though it's the ONLY one I can give).