View Single Post
Old 06-12-2018, 10:59 PM   #7
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by BetterRed View Post
I don't use Book View very often, hardly at all in fact,
I only use it in two cases:

One: When I'm working on some absolutely spaghettified/mangled HTML and want to manually split chapters.

In Book View, you can easily see where the cursor is located, and then you can press Edit > Split at Cursor or Ctrl+Enter.

Preview is missing the cursor + Code View is sometimes not human-readable (think InDesign mess where every word is wrapped in a hundred-character <span>).

Two: When I go through a book and want to quickly add/tweak <h1-h5> to text. I can scroll through and visually see what text should be what heading. Then I can click on it + Ctrl+1 through Ctrl+5 to give it the proper heading level.

Book View changes instantly.

With Preview there is a very long delay, and sometimes when syncing between Code/Preview, it jumps to other locations (Book View doesn't have that problem).

And Code View, it's very hard to visually see the code should actually be (many times blog posts accidentally have stuff like <p><strong>Subheading</strong></p>).

Last edited by Tex2002ans; 06-12-2018 at 11:06 PM.
Tex2002ans is offline   Reply With Quote