JS in Epub3 is useful for the designer -- so long as you're ebook is aimed to specific marketplaces (iOS Apple, Kobo marketplace, etc - but not KDP), using EPUB3 code.
Your chosen end user group is also key (is it a person sitting in a room reading an eBook late at night, or a person out walking along a hiking trail needing to look at their cell phone at the eBook for further information, or a photo gallery ebook).
If its just a person reading general fiction at home, or old books converted to epub, then that group of persons may not need anything more than Epub2 code, and a generic eReader device.
That being said, posting here at MobileRead (posting with the post heading specifically mentioning JS code).
Other sites out there:
ebooks.stackexchange, or at
stackoverflow (at epub3 tags).
Posting here on MobileRead has many Epub2 coders, and a core that code for Epub3 (using it in its basic form w/o touching its more extensive potential).
But for those epub designers who create new designed ebooks loaded with imagery, loaded with technical information intended for a user such as a sports based ebook -- then JS code certainly can be useful to the epub designer.
Start a new post page somewhere in ethernet world and we'd be interested to read your posts about epub JS code.
|