Quote:
Originally Posted by CliffB
but you don't abandon a very valuable feature just because it has some flaws that can be worked around!
|
If that was the only issue, there'd be no discussion/problem. IF (and it's a really big and distant
if) Book View were ever removed, it wouldn't be because it "has flaws that can be worked around." I wish that was the only hurdle we faced. The problem is that the hoops that have to be jumped through to allow both Book View WYSIWYG editing AND Code View editing (and the synchronization between them) are getting higher and smaller all the time. We're also facing the eventual removal of WebKit (the rendering engine behind Book View--which is now deprecated, BTW) from Qt5. Which would mean
another overhaul of Sigil to continue to provide Book View/BookView-editing (if we wanted to avail ourselves of the feature-improvements/bug-fixes in future versions of Qt5).
Nobody
wants to go WYSIWYG-only or CodeView-only, but when the former is holding back advancements (not that that is happening
yet), or features/improvements that would be relatively simple to achieve without it, then we have to consider what would be best for the
majority of users (and our sanity).
But like Kevin said, there's no current plans to remove it. Just discussion. But please don't make the mistake of thinking we would ever axe it simply because it has a few flaws (or because we don't like it because we're "coders"). It's more complicated than that.