You can make a list of tiddlers that are supposed to be viewed in order. Add this macro (or a variation of it) by Mohammed (https://kookma.github.io/TW-Utility/#demo%2Fsimple-navigation). This adds navigation to those tiddlers, so users can press 'previous' and 'next' buttons to go back and forth in a linear manner. You can then ofcourse style the buttons however you please. What makes this macro pretty handy is that it uses the order that is in the tag-dropdown list. You can drag-and-drop tiddlers in that list to change the order. So it is easy to rearrange and order your tiddlers, without changing links you've made in the text.
Op dinsdag 9 februari 2021 om 16:32:15 UTC+1 schreef [email protected]: > Thank you kindly Mat, PMario, and Mark S for all your comments. You have > given me much to think about it. > > > > In response to some of the clarifying questions, here are my > justifications for pursuing TiddyWiki, and my current requirements: > > > > - I like the fact that TW is a one file that can be easily viewed, > downloaded or make derivative works from. I can see, however, that may > cause file bloat and when adding images. A 400 mb single file isn’t going > to work when students will be likely using their underpowered smart phones > to read the text and images. Maybe I can host image in a folder and link > to > it from TW, but that would break the derivative part unless there is a > plugin to automagically create PDFs, downloadable EPUB, etc ( like there > is > download option for Wikipedia\Wikimedia). I just don’t want to constantly > maintain and update a separate file for that purpose. An acceptable > compromise might by a chapter by chapter download versus the whole thing. > Or maybe I shouldn’t care and just leave it to the end-user to figure it > out. Seems very rude though IMHO. This isn’t a critical feature for me, > but > it is part of the OER ethos. > > - To me, a linear process is going from Step 1, Step 2, and likewise, > reading from Chapter 1 to Chapter 2, and so on. You are correct that > books, > per se, are not very linear in their creation, but I was alluding to the > process in which they are read or understood. I don’t want to confuse > students by making it too easy to skip around and miss critical concepts > by > not going in a specific order, which can happen with “Research Wormholes” > on Wikipedia where all you wanted to find out was about Topic A but then > you get off-track by reading Topic B,C,D,E, etc. > > - I’m drawn to FLIF as a modern alternative to animated GIFs., which > depending on size and resolution can result in massive file sizes. I do > not > think that JPEG XL can serve animated content, if only be going by the > lack > of doing so for JPEG and JPEG2000. Considering device issues and internet > connection speeds, GIFs really aren’t going to cut it. I could fall back > on > APNGs, but that format doesn’t have much browser support either but it may > end up being the necessary compromise if I can’t get FLIF to work > correctly. The only player left in this small format field (AFAIK) is > Google’s WebP format, but cursory research reveals double the file size of > an equivalent animated GIF. > http://littlesvr.ca/apng/gif_apng_webp3.html You might point out to > just use videos, but people read faster than listening to the spoken word > or watching a video. I want to be able to serve short animations of 5-30 > seconds of content at a time, as necessary, fronted and backed by the > appropriate text explanation. I’m not a back-end developer so by > suggesting > to figure out a widget to make FLIF work with TW is probably the answer – > not going to happen. =) > > - I just saw the post about a TiddlyWiki Textbook. That’s really cool > and will try attempt to contribute only to see if that’s going to work for > my needs. In the meantime, I guess it’s time for some rigorous testing. > Aside from TiddlyWiki, I’ve been looking at DocuWiki and Wiki.js. I might > have an open source webhost lined up too (where server space and bandwidth > is limited – necessitating image compression algorithms), we’ll see. > > > > > Best wishes, > > Jeremi > > > > > > > > *From:* [email protected] <[email protected]> *On Behalf > Of *PMario > *Sent:* Monday, February 8, 2021 1:12 PM > *To:* TiddlyWiki <[email protected]> > *Subject:* [tw5] Re: TiddlyWiki for Books (Newbie Questions) > > > > On Monday, February 8, 2021 at 3:41:48 PM UTC+1 [email protected] > wrote: > > > > 3) How well does TW play with Javascript? I want to implement an open > source image compression algorithm that doesn't yet have major browser > support. The only way to use it at the moment is to wrap the image in a > javascript script. For those interested, I want to use this: > https://flif.info/ > <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fflif.info%2F&data=04%7C01%7Cjbigosinski1%40ncc.commnet.edu%7Ca1e517ed6bd54f6810e408d8cc5d19c5%7C679df878277a496aac8dd99e58606dd9%7C0%7C0%7C637484047522016933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mqHxOWTDlQsek%2B2rp6eVv72qSxQsKWOhwMuMGVNlPbQ%3D&reserved=0> > > > > TW plays well with JS, if you know how to do it. It is more advanced as > adding a script to a static page. TW is highly interactive and the "visual > elements" can be redrawn anytime. ... So you probably will need a new > widget, that can deal with your image format. > > > > FLIF will probably _never_ be supported by major browsers, since it is > superseded by JPEG XL > <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjpeg.org%2Fjpegxl%2F&data=04%7C01%7Cjbigosinski1%40ncc.commnet.edu%7Ca1e517ed6bd54f6810e408d8cc5d19c5%7C679df878277a496aac8dd99e58606dd9%7C0%7C0%7C637484047522016933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=D%2Fu1IOwicrI%2FSPWN62gpaLSM2fr3GFujYXKa7HJbJqQ%3D&reserved=0> > > which seems to be ISO standard now. According to the "tracking bugs" > browsers are focusing on JPEG XL. > > > > There seems to be a FLIF browser polyfill, that can be used. ... I did > play a little bit with the polyifll demo page. The advantage of the FLIF > file format seems to be, that it can "partially" download the image and > still show something. ... The polyfill seems to always download the whole > file. .. So IMO there will be no advantage. > > > > The github-flif page says, that development has stopped > <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FFLIF-hub%2FFLIF&data=04%7C01%7Cjbigosinski1%40ncc.commnet.edu%7Ca1e517ed6bd54f6810e408d8cc5d19c5%7C679df878277a496aac8dd99e58606dd9%7C0%7C0%7C637484047522026926%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vsRt2W4BRgf0MqyHUxAD1%2BvF%2BmvmOAjpfoYC6lo7X%2Bo%3D&reserved=0>. > > ... So for me it doesn't make too much sense to use this file format, > except you absolutely have too. > > > > Is there a reason, why you want to use FLIF? ... Or is it just a "want to > have"? > > > > -mario > > > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/4c397b8c-2eb9-4626-ac1e-4d502e4cbc5fn%40googlegroups.com > > <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Ftiddlywiki%2F4c397b8c-2eb9-4626-ac1e-4d502e4cbc5fn%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=04%7C01%7Cjbigosinski1%40ncc.commnet.edu%7Ca1e517ed6bd54f6810e408d8cc5d19c5%7C679df878277a496aac8dd99e58606dd9%7C0%7C0%7C637484047522026926%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=RLNI5mDrMVUUeXCnBJ4%2BJHR3B7TrJyWkFZhobTgKr0c%3D&reserved=0> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/cef67da6-4326-4c89-b1a8-9dad39841d6cn%40googlegroups.com.
