Ciao Matthew Thank you for taking the time to do that example. Its helpful. Its helping me think freshing about what "context" is.
It prompted me to think that maybe there could be a way that each Paragraph Tiddler (when gone to via an Href, in its singularity, not its embedded appearance in transclusion) might have buttons top and bottom to programmatically Transclude the Next (down) or Previous (up) paragraphs when clicked. I'm not quite sure how to do that but it seems a possible solution? If it works then then one might keep expanding as needed? Best wishes Josiah On Wednesday, 25 January 2017 20:49:36 UTC+1, Matthew Lauber wrote: > > Here's an example of what I mean. > > On Wednesday, January 25, 2017 at 2:36:32 PM UTC-5, Matthew Lauber wrote: >> >> Soemthing else that could be work is to create a ViewTemplate that lets >> you "add context". When a paragraph tiddler is viewed directly, It >> displays the preceding paragraph based on the list field of the chapter, or >> the sort order of the tiddler titles or whatever you're using to transclude >> all paragraphs into the chapter section. But when the tiddler is >> transcluded you wouldn't get that, so your chapters would still work >> properly. But you wouldn't be able to scroll back arbitrarily in the book >> that way, just get the surrounding N paragraphs. >> >> Matt >> >> On Wednesday, January 25, 2017 at 2:28:21 PM UTC-5, Jed Carty wrote: >>> >>> There has been lots of discussion about this without much resolution. To >>> my knowledge the only result of these discussions is that it isn't >>> reasonable to make something that lets you navigate to a chunk smaller than >>> a single tiddler because in order to do that you end up making an object >>> that has all the properties of a tiddler and you end up back where you >>> started. >>> >>> With that said, in specific situations it may be desirable to make >>> different behaviour using a plugin or something. >>> >>> In the case of books many people (including me) have looked into this a >>> lot and I think that the answer may be to create a story view that displays >>> a set of tiddlers in order to give a chapter-by-chapter or page-by-page >>> view of the book, then to reach the next chapter or page the tiddlers that >>> are displayed are all changed at once. This way you can still navigate to a >>> single paragraph because it will be its own tiddler, but when you navigate >>> to it instead of opening just that tiddler it gives you the full >>> page/chapter that it belongs to. >>> >>> I don't think that anyone has gone much farther than just describing >>> this. In the book he is working on Eric made a lot of nice tools for >>> presenting a tiddlywiki in book form, but I haven't played with it myself >>> so I don't know if his work applies here. I don't think this is really what >>> he was working on making. >>> >>> Unfortunately now that I have a job I actually like I spend much less >>> time playing with new tiddlywiki things. I may look at this a bit and see >>> if I can throw together a quick prototype that maybe someone else can >>> polish later tonight since this keeps coming up. Regardless of what form >>> the solution takes, putting together a book is probably going to be a >>> significant amount of work because all of the tiddlers are going to need to >>> be labeled and tagged correctly to make the organisation and ordering fit >>> what is wanted. >>> >> -- 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 post to this group, send email to [email protected]. 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/c024dc3a-878d-4eef-a615-4535f9343a28%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
