Gonzalo,<br><br>WebKit can do things that EPUB would not normally allow. Project Gutenberg makes EPUBs by taking the hand crafted web page and putting it in a Zip file with some XML files. On Read it looks just like the original web page. On a Kindle it might look just awful.<br>
<br>I don't know if the ENYO framework is entirely JavaScript (in which case it could be included in the EPUB) or if it has some non-JS portions. It sounded to me like it did. Those portions would need to be added to Read.<br>
<br>James Simmons<br><br><br><div class="gmail_quote">On Mon, Aug 27, 2012 at 12:27 PM, Gonzalo Odiard <span dir="ltr"><<a href="mailto:gonzalo@laptop.org" target="_blank">gonzalo@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't understand the relation.<div>We already use webkit, then, we can use play javascript if needed.</div><div>I think epub2 standard does not allow javascript, I don't know epub3</div><span class="HOEnZb"><font color="#888888"><div>
<br></div></font></span><div><span class="HOEnZb"><font color="#888888">Gonzalo </font></span><div class="im"><br>
<br><div class="gmail_quote">On Mon, Aug 27, 2012 at 1:39 PM, James Simmons <span dir="ltr"><<a href="mailto:nicestep@gmail.com" target="_blank">nicestep@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What it sounds like you could do is incorporate the ENYO framework into the Read Activity, then make EPUB format books that include JavaScript. Since Read uses WebKit it already renders EPUB books created from web pages (like those from Project Gutenberg) better than Nooks and Kindles do, and having some JavaScript on the pages would be a natural thing to experiment with.<br>
<br>James Simmons</blockquote></div></div></div>
</blockquote></div><br>