Hi, maybe it was a wrong impression, but my understanding was that javascript code, in addition to being avoided in html tiddlers, has to be executed before DOM creation, so cannot be propagated (or not resolved) up to the end of the chain, so to be executed by the browser after TW rendering. That's because the final object has to be static HTML. For instance I needed to add a couple of js libraries (one for table manipulation, one for chess game parsing) which usually in my html note collection I added directly to the script calls in the HTML head section. I tried to add this code to TW but I realized (that's where I could be wrong) that I had to write a plugin incorporating the libraries. Otherwise I would not be able to add js call to external libraries directly in the tiddlers, or even via js macros. So I was arguing that for eventual epub exporting, which would be based on static HTML, it were not possible to add js call section in order to have dynamic pages. In last case one could think, by means of epub3 format, to use TW as dynamic site generator... am I wrong? thanks and regards,
Netsaver, Rome (IT) Il giorno sabato 26 maggio 2018 12:22:00 UTC+2, Jeremy Ruston ha scritto: > > Dear Paul > > I can see that Epub3 format can execute also scripts in JS subfolder. > > > JavaScript support is inconsistent and limited on current readers, hence > my interest in techniques to avoid dependence on it. > > Why is not technically possible to write JS code in some tiddler belonging > to epub project and appending references to it in the final html pages? > There's some design constraint? > > > I don’t think there is any design constraint within TW5 there; is there a > reason you thought there might be? > > Best wishes > > Jeremy > > > e.g. create tiddler sort-table.js, adding sort capabilities to all tables > with class 'sortable', add it to the project, then add also tiddler > chapter1, containing a table with class 'sortable'. The sort-table.js > tiddler should be published in the JS folder of the book and references to > it (<script src="js/sortable.js"></script>) could be added (automatically? > or via processing instruction in every tiddler?) to html tiddler(s). > > In a similar concept: is it possible to create (system/common/shadow or > whatever) tiddlers containing js code which is to be appended as script to > some tiddler 'after its rendering to html', so to be executed by the > browser when it's loading the final product > e.g. if I tag a 'sort-table.js' tiddler with tiddler names 'hosts', > 'addresses', etc. would mean that TW should append js reference to > sort-table in #hosts and #addresses html subcode. This behavoiur (if > possible!) coud be kept when developing an eventual ebook plugin. > What am I missing? > > Thanks and regards, > Paul Netsaver, > Rome, IT > > > > > Il giorno venerdì 25 maggio 2018 10:43:28 UTC+2, Jeremy Ruston ha scritto: >> >> I very much like the idea of an epub3 output format for TW5. >> >> As others have noted, the epub3 format itself can be fairly simple (plus >> the general rule that it is always orders of magnitude easier to generate a >> particular format than it is to parse/accept that format). We already have >> a JSZip plugin that can handle the creation of a ZIP file from a bunch of >> individual files. >> >> One aspect that particularly interests me is the production of redundant >> static pages to reproduce the functionality of a dynamic experience. For >> example, consider a table of a few columns of data that we’d like to >> publish such that the user can click on a column heading to sort by it. The >> usual approach would be a small JS plugin that rearranges the DOM when the >> column header is clicked. Instead, we could pre-generate static HTML >> representations of every combination of sorting for the table, and then >> construct links between them. So, if the initial rendering is ordered by >> first name, and the user clicks on the column for the second name, they >> would actually be navigating to a different rendering of the data sorted by >> second name. >> >> I believe that this approach could go a long way: a sort of flipbook >> approach to user interface design. >> >> Best wishes >> >> Jeremy. >> >> >> >> On 25 May 2018, at 04:02, Greg Davis <gregdav...@gmail.com> wrote: >> >> Mark S. >> >> Hi, >> Well if it is Science Fiction there is always Baen official slush for >> publication http://baen.com/ >> >> If you have not given it to a beta reader and/or editor. You can try the >> crit forums on Baen's Bar (have to register) the Slush Pile is for general >> critiques. Other critique forums are Baen's Universe Slush is for short >> stories and 1632 Slush is for stories in Eric Flint's Ring of Fire Universe. >> http://bar.baen.com/ >> >> On Thursday, May 24, 2018 at 9:48:31 PM UTC-5, Mark S. wrote: >>> >>> I guess we're all in the same boat. I've got one medium story finished, >>> but wasn't sure where to submit it. >>> >>> -- >>> >>> On Thursday, May 24, 2018 at 7:44:58 PM UTC-7, Greg Davis wrote: >>>> >>>> Tony >>>> >>>> GO FOR IT ! ! >>>> >>>> Hey, I was IT. Life interrupted but I am trying to get back to the >>>> project I started along time ago. First drafts and notes scattered all >>>> over. Wish I'd had TiddlyWiki back then to keep track of everything. >>>> >>>> Best Wishes, >>>> Greg >>>> >>>> On Thursday, May 24, 2018 at 7:12:04 PM UTC-5, TonyM wrote: >>>>> >>>>> Josiah, >>>>> >>>>> The incentive is very powerful for a sub-sector of users, when I was >>>>> younger I wanted to be a cosmologist and science fiction writer. An IT >>>>> career happened instead. Only recently I started to think about writing >>>>> again because I could build a universe, a solar system and a number of >>>>> planets and document it in TiddlyWiki. To think that within that wiki the >>>>> eventual content can be produced then published to a common reader format >>>>> sounds great. We can do this to PDF with our browsers so what extra value >>>>> is direct to epub offer? I imagine a richer index and more? >>>>> >>>>> If however there are good PDF to epub converters I would not waste our >>>>> time with another export format but add it to improving PDF outputs. >>>>> >>>>> Regards >>>>> Tony >>>>> >>>> >>>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "TiddlyWiki" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to tiddlywiki+...@googlegroups.com. >> To post to this group, send email to tiddl...@googlegroups.com. >> Visit this group at https://groups.google.com/group/tiddlywiki. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/29761c36-7cb5-4aff-b629-7e740cee208c%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/29761c36-7cb5-4aff-b629-7e740cee208c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to tiddlywiki+...@googlegroups.com <javascript:>. > To post to this group, send email to tiddl...@googlegroups.com > <javascript:>. > Visit this group at https://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/8aae62a1-c840-442a-bd91-ffc8775fe4b9%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/8aae62a1-c840-442a-bd91-ffc8775fe4b9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/0ca407f3-7d4b-431b-a713-ddfd5227670f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
