Considering the demise of BookView

[C-novice]

Sad that BV's days are numbered. Could it become something like a plugin then? So those of us who like it can still use it? Or would that still bring maintenance issues?

[Toxaris]

Originally Posted by DiapDealer

If you're looking at it in Preview, don't you already know what it is?

Good point. Like I said, I never used it like that myself.

[Toxaris]

Originally Posted by C-novice

Sad that BV's days are numbered. Could it become something like a plugin then? So those of us who like it can still use it? Or would that still bring maintenance issues?

I don't see how. The plugin would basically become an editor in itself then.

[Hitch]

Originally Posted by Toxaris

I don't see how. The plugin would basically become an editor in itself then.

I am 99% sure that if BV were able to be put into a plugin, without all the concomitant problems that are causing it to be put down in the first place, Diap and Kev would happily do that, but there are, as I understand it, overwhelming issues with it.

Hitch

[C-novice]

Originally Posted by DiapDealer

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.

I'm afraid to ask but is Book View gone yet? or have you changed your mind DD?

Here's to still believe in hopes and miracles.

[Turtle91]

Hopes are dashed...
Miracles do exist...but it would take more than a miracle to change their minds...
BV still exists...as of now...

[DiapDealer]

Yes: Book View will still be in the next release. We won't pull a "Surprise, no Book View!" on users.

No: we've not changed our minds about hating BV with a passion and planning to eventually remove it. If anything, we keep running into more and more situations where Book View foils our plans for continued Sigil improvements.

[KevinH]

If it helps, one idea when removing BookView is to pull the BV related code into a transitional standalone Qt single xhtml file editor app so that people could still use "open-with" on a CodeView window and get something that acted like BookView (and but it would still have all the same problems).

That would still allow us to remove all of that flowtab and BV related code and ui, and free up a bunch of icons in the mainwindow for more plugin icons and actions including pre-packaging some plugins to extend Sigil.

[Thasaidon]

Originally Posted by KevinH

If it helps, one idea when removing BookView is to pull the BV related code into a transitional standalone Qt single xhtml file editor app so that people could still use "open-with" on a CodeView window and get something that acted like BookView (and but it would still have all the same problems).

That would still allow us to remove all of that flowtab and BV related code and ui, and free up a bunch of icons in the mainwindow for more plugin icons and actions including pre-packaging some plugins to extend Sigil.

If that is doable without an excessive amount of work or creating more problems than it is worth, then it sounds like an ideal solution to the BV problem.