MobileRead Forums - View Single Post

pittendrigh · 03-10-2018, 02:43 PM

indeed. I'm 70 with deteriorating eye sight so have to read digitally (with enlarged font). But I do so with all of my desktop my phone and a large tablet, all of which can surf the net as well as display a book. I wouldn't consider a books-only device.

Perhaps more interesting is a looming inverse. I've written some server-side software that works (will be open source perhaps within the year) that displays any epub3 (epub2 is coming but the TOC parser is easier on epub3) as a website.

Bibi does that too but bibi is not embeddable. My software is so simple it will be easily recreated. But mine creates two DIV elements, one for the TOC (which can be minimized with Javascript) and the page contents, all of which can be embedded inside any Content Management System (which Bibi cannot).

My software isn't the point. What is interesting, I think, is the idea that any and all complex websites would be better off re-creating themselves in book-like format.

In other words I'm NOT suggesting your ebook should become a website. I am suggesting your website should become an ebook that displays online, inside a browser. At least if you have a complex site with more than a few pages. Especially so for How-To-Do it instructional pages, for photography, computer programming, financial investments, boat building, kitchen/bathroom remodelling etc.

If you have a complex website you'd be better off reformatting as a book. So the ebook reader is indeed dead for me (I'd rather use a browser phone or tablet). And the stoneage website is dead too. I'd rather see that website organized like an online ebook.

03-10-2018, 02:43 PM	#314
pittendrigh Connoisseur Posts: 78 Karma: 1332336 Join Date: Mar 2011 Location: montana Device: none	indeed. I'm 70 with deteriorating eye sight so have to read digitally (with enlarged font). But I do so with all of my desktop my phone and a large tablet, all of which can surf the net as well as display a book. I wouldn't consider a books-only device. Perhaps more interesting is a looming inverse. I've written some server-side software that works (will be open source perhaps within the year) that displays any epub3 (epub2 is coming but the TOC parser is easier on epub3) as a website. Bibi does that too but bibi is not embeddable. My software is so simple it will be easily recreated. But mine creates two DIV elements, one for the TOC (which can be minimized with Javascript) and the page contents, all of which can be embedded inside any Content Management System (which Bibi cannot). My software isn't the point. What is interesting, I think, is the idea that any and all complex websites would be better off re-creating themselves in book-like format. In other words I'm NOT suggesting your ebook should become a website. I am suggesting your website should become an ebook that displays online, inside a browser. At least if you have a complex site with more than a few pages. Especially so for How-To-Do it instructional pages, for photography, computer programming, financial investments, boat building, kitchen/bathroom remodelling etc. If you have a complex website you'd be better off reformatting as a book. So the ebook reader is indeed dead for me (I'd rather use a browser phone or tablet). And the stoneage website is dead too. I'd rather see that website organized like an online ebook. Last edited by pittendrigh; 03-10-2018 at 02:46 PM.