06-12-2018, 07:37 PM | #1 |
null operator (he/him)
Posts: 20,567
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
Considering the demise of BookView
There has been some discussion of late regarding the exorcising of Book View. I thought it might b worthwhile to have somewhere users can document any concerns.
BR |
06-12-2018, 07:39 PM | #2 |
A Hairy Wizard
Posts: 3,094
Karma: 18727053
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Bookview?!?! What's that?
|
Advert | |
|
06-12-2018, 07:47 PM | #3 |
null operator (he/him)
Posts: 20,567
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
I don't use Book View very often, hardly at all in fact, but there's one feature I have used to good effect and that's Format->Remove Formatting. In Book View it only removes styling tags (bold, italics etc) within the selected text (e.g. an entire html file), but retains paragraph, division, etc tags as-is. In Code View it removes all tags.
Maybe Remove Formatting could have two options when used in Code View - All Tags, and Styling Tags Only. That which you love to hate, what on earth will you do without it BR Last edited by BetterRed; 06-12-2018 at 08:48 PM. |
06-12-2018, 08:42 PM | #4 |
Well trained by Cats
Posts: 29,799
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
The only reason I use BV is when I try and save and get an error warning and I have no clue WHICH TAB(s) it is coming from.
I switch to BV and start closing Tabs. When I hit the error, the editor switches to CV and asks (I always choose the manual mode fix. I have seen Auto make worse hash outa mile pile of dodo ) what to do? If there was a summary of all the (malformed) error locations (the same info that shows in the pink boxes) that would satisfy my reason for hanging on. |
06-12-2018, 09:11 PM | #5 | |
A Hairy Wizard
Posts: 3,094
Karma: 18727053
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Quote:
|
|
Advert | |
|
06-12-2018, 09:22 PM | #6 | |
Hedge Wizard
Posts: 800
Karma: 19999999
Join Date: May 2011
Location: UK/Philippines
Device: Kobo Touch, Nook Simple
|
Quote:
That would be nice and very useful. WHEN BV goes I would like to see Preview being assigned the '<>' icon. If Preview was invoked by the '<>' icon and the Preview screen replaced the CV tab (as BV does now). BV could then be invoked by F10 and appear in a separate window like Preview is currently. If this was done I think the use of BV would diminish dramatically while allowing the people use it for very minor corrections to do so. |
|
06-12-2018, 10:59 PM | #7 |
Wizard
Posts: 2,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
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. |
06-13-2018, 01:08 AM | #8 | |
Connoisseur
Posts: 57
Karma: 600000
Join Date: Jan 2018
Device: Galaxy Tab S2
|
Quote:
But: as soon as the current master found his way to a release i dont need BV any more (clickable links). Pink error boxes are shown in Preview as well. |
|
06-13-2018, 03:49 AM | #9 | |
Hedge Wizard
Posts: 800
Karma: 19999999
Join Date: May 2011
Location: UK/Philippines
Device: Kobo Touch, Nook Simple
|
Quote:
That is something new I have learnt today. |
|
06-13-2018, 04:32 AM | #10 |
Chalut o/
Posts: 410
Karma: 145324
Join Date: Dec 2017
Device: Kobo
|
For me "BookView" edition is the big advantage of Sigil compared to other ePub editor.
For small text changes (without formatting, just added and deleted plain text) has the best for this function (Caliber, wordy ; Jutoh, not quickly ; and there's not many others I know) In "BookView" we look at and read quickly our book, we locate the elements to be modified. Another very easy thing in "BookView": add separation marks, to quickly separate the pages of the book if needed. In clear, all simple operation, which requires quick and visual feedback for certain ease of operation, which would be incredibly more complicated in "CodeView" And if the modification is a little more subtle => go "CodeView" Okay it's not optimized, okay it's buggy. A lot for some. But, for answer the Thread title : Demise the BookView would be a biggest mistakes and a big loss for Sigil. One good thing to do is to explain to users that "BookView" is only an "interactive preview", but "incomplete". A quick editing aid, not the main tool. Useful for text editing, not the formatting. @Thasaidon Switch "BookView" and "Preview", why not. But a practical and quick access solution would be to put "BookView" in a "Preview" submenu, or have the 3 buttons "Preview", "CodeView", "BookView". Last edited by un_pogaz; 06-13-2018 at 05:10 AM. |
06-13-2018, 01:07 PM | #11 |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
I never use Bookview, I do everything in Codeview with the preview window activated. Based on all the discussions in the past, Bookview is holding back Sigil in its developments.
|
06-13-2018, 01:49 PM | #12 |
Grand Sorcerer
Posts: 27,548
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
It's only a question of when Book View goes away, not if. It's become a boat anchor when it comes to Sigil development. It's buggy and it's increasingly unmanagable. It's fine for everyone to bring up things they still use BV for (mainly so alternatives can be suggested), but don't get your hopes up that Book View will get a reprieve. That ship has sailed. Book View is on borrowed time.
|
06-13-2018, 02:15 PM | #13 |
Grand Sorcerer
Posts: 27,548
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
|
06-13-2018, 09:03 PM | #14 |
Hedge Wizard
Posts: 800
Karma: 19999999
Join Date: May 2011
Location: UK/Philippines
Device: Kobo Touch, Nook Simple
|
|
06-13-2018, 09:10 PM | #15 |
Hedge Wizard
Posts: 800
Karma: 19999999
Join Date: May 2011
Location: UK/Philippines
Device: Kobo Touch, Nook Simple
|
It does not have to be the '<>' icon itself. But I would like an icon just for Preview with the screen replacing the CV tab (as BV does now) or perhaps adding it as a new tab. This would allow quick switching between CV and Preview.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
The demise of the gadget | issybird | News | 135 | 05-11-2017 08:44 PM |
Suggestion : Migrate BookView to a plugin | BetterRed | Sigil | 1 | 08-14-2016 05:56 PM |
Dame Demise | stuartneild | Self-Promotions by Authors and Publishers | 3 | 02-14-2011 11:38 AM |
Could lack of piracy be the e-book's demise? | TadW | News | 44 | 02-12-2009 05:34 PM |