Sigil download link based on webkit and equipped with Book View option?
 

A pity that for unknown unknown reasons:

• If the WYSISWYG Book View view has been removed and because JavaScript does not work in the preview window, JavaScript can no longer be tested
• Automatically making an EPUB file suitable for reading in an EPUB 2 device increases the chance that readers cannot read the EPUB
• If PageEdit

is unable to directly read an EPUB file, the EPUB must first be unpacked each time to be read and tested.

For people with an Ebook reader developed around 2010 who would like to write and test a simple story with a PDF layout in an EPUB file, they will undoubtedly be satisfied with the current version of Sigil :D. Unfortunately :rolleyes:, it is no longer the most convenient development environment for developing an interactive EPUB, or an EPUB that takes into account all kinds of dimensions of today's telephone screens and wants to use the possibilities of EPUB3 and HTML5 frameworks.

Most of the Sigil bugs that I have suffered were caused by saying goodbye to Book View option. Apart from some well-known buttons, the use of PageEdit unfortunately does not offer much to all kinds of existing HTML editors.

:help:Who has a Sigil download link for me based on webkit and equipped with Book View option?

The reasons are not unknown. You just don't agree with, or care about them. Those reasons have been discussed for years. Not our fault that you didn't come around to participate until now.

Javascript was never able to be tested reliably with Sigil using Book View with WebKit.

Sorry, but you're all wet about the latest version of Sigil being more limiting (for preview/proofing options) than the older version. You're entitled to prefer the older version, but you're not entitled to spread misinformation about the capabilities of the new versions (which include javascript, EPUB3 and HTML5).

And neither did Book View. Sigil's WYSIWYG editing capabilities have always been inferior to most existing HTML editors. That's true of Book View and PageEdit.

Pretty much everyone does. Yourself included. The Github Sigil releases page (easily found from the "Downloading Sigil (and other important links)" sticky thread here, and from the links in the Sigil Github wiki) has every release we've ever done of Sigil in recent (and not so recent) history. Sigil 0.9.14 was the last version that supported WebKit and Book View.

Some corrections: You really do not need to unzip an epub to use PageEdit. Sigil has added an option to specify an external xhtml editor and launch it by the push of an icon in Sigil.

Also note, that for safety reasons, users have to enable book based javascripts to run in Sigil in their preferences. The same is true for PageEdit.

In Addition: Sigil is using Webkit or somethin else to render the (X)HTML, which allows much more then actual e-reades can display. Most of them rely on Adobes RMSDK which can only display a subset of CSS 2.1, for example all pseudo-elements are taken into account which the renderer used by Sigil displays correctly. margin:auto is to allowed to be ignored, which is not the case in normals CSS and much more.

As links can be tested in the preview window i cant see any advantege of supporting bookview any more. It cuased more trouble and everya now and then postings here asking why its so problematic to insert text or even edit it

And one more correction: javascripts when enabled by the user do run in Preview in Sigil. This is in fact how we support MathML in Sigil.

@KevinH: Thanks for pointing me to the option to turn on JavaScript (good security behavior:D) which was not implemented for Book View (bad security practice:angry:) and yours suggestion to implement PageEdit as an external (X)HTML editor to restore the old View Book functionality. Current Sigil content with include non-saved changes can indeed displayed and saved in PageEdit.

@Vroni: I did a lot of investigation to see how to implement Responsive Mobile frame works like Bootstrap 3 or 4, Materialize can be ported to EPUB. I get the best result on different tablets and Android telephones with the free GitDen reader which has also a free Apple version (not tested by me).
I see the best result with CSS only frameworks which are designed to work with different Browsers. Sadly all browser tests never show results for EPUB. Therefore you need to test what is working as expected and what is not working at all within Sigil and the E-reader. Especially those frameworks who have webkit replacement for not implemented CSS function gives the best results in GitDen. I have good results with Skeleton version 2.0.4, which include a normalize.css to overcome all kinds of browser issues. I drop font loading from Internet or if needed like the Awesome or Google font, I store a modified version into the EPUB.

@DiapDealer: I’m aware of the fact is that it is the development team or developer to accept, reject and prioritize bug fixes, new options, how they follow the standards for HTML5 and JavaScript, and which options are set for an out-of-the-box setting. In the many years of discussion you refer to, I saw therefore no reason to add something meaningful to it.

Try PocketBook:

https://play.google.com/store/apps/d...eader&hl=en_US

It has two render engines: RMSDK and WebKit. And you can choose what engine to use to open an epub. The WebKit engine practically supports all css3 properties (for both, epub2 and epub3).

This is indeed a very nice E-reader RbnJrg, smooth navigation and a lot of functionality. Many thanks for your advice.