> > Does not looks like a toc? > Sure looks like a toc, but I don't think a toc alone is what it's all about.
What is it about? The ability to not just open a "section tiddler", in-place or standalone, but to *open it in the context of an "aggregated story" tiddler*, whether that aggregation was achieved manually or automatically, doesn't matter... thus a representation preserving the story-lineup (not just when tw opens) ...whereas if things were dynamically added or removed to this story, so would the toc be ammended or truncated and vice versa. In short, the usecase is to scroll to (a section) tiddler X within (an aggregated story) tiddler Y ...preferably without Y having to be open yet. I really don't see that in... http://tiddlywiki.com/#Creating%20SubStories <http://www.google.com/url?q=http%3A%2F%2Ftiddlywiki.com%2F%23Creating%2520SubStories&sa=D&sntz=1&usg=AFQjCNFOHkkTZ8r0UqlabUz-livRSsjBfg> ——— I'm sure this has been discussed at lengths, but not being able to leverage sections has the side-effect of bloating up the tiddler namespace, like... Author A — Story X Author A — Story X — Summary Author A — Story X — Chapter 1 Whereas at some time in the past, the list of tiddlers was a lot more concise with a mere... Author A — Story X Architectural constraints be what they may, for simplicity's sake, I think it's a good tenet to provide means for reducing the number of required tiddlers to a minimum. What could be interesting is the ability to have substories / subsections actually embedded within a "story tiddler", via some sort of nested JSON construct / field, which would sure require some UI magick to have it represented as a substory, probably right after the main story, and then of course the ability to make that content editable. If need be, there could even ba a way to "explode" such a substory construct to actual tiddlers. ——— Don't get me wrong, I can see how exposing substories as individual tiddlers provides benefits as in... http://tw5.scholars.tiddlyspot.com ...where you can thus add individual notes, ideas, comments, etc. to individual chapter tiddlers of book tiddlers, which sure wouldn't be possible with the above approach where substories where contained within some field of a parent story-aggregate. But then, again, it would really be nice to see all of book and chapters in one story lineup as... story tiddler chapter 1 chapter 2 ...with the ability to directly open / go to any (generated) "section" via some clickable toc (or a manually defined link, really), and preferably some backlink in a "section heading" to quickly jump back to the toc ——— Of course, I am totally aware that that's a big wishlist. ^_^ Best wishes, Tobias. -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
