On Friday, June 5, 2015 at 1:08:37 PM UTC-7, Mat wrote:
>
> @Eric (will post separately if he doesn't see this)
>
> In hangout #85 I just noted that you, in talking about the book features, 
> mention a mechanism to record the sequence in which tiddlers are *viewed 
> ("it's not the history list" etc). *May I ask how this is done, briefly? 
> How is a "viewing" registered?
>

I think I said it's not the $:/StoryList, which uses the "list" field to 
track the currently displayed tiddlers, in the order they are *shown* in 
the StoryRiver.  In contrast, the $:/HistoryList uses JSON-formatted data 
in the "text" field to record each time a "navigation event" occurs.  This 
is handled by the core and occurs automatically. 

The $:/HistoryList JSON data includes not only the titles of the tiddlers, 
but also other information about the rectangle used to animate the opening 
of each tiddler. 

Note that $:/HistoryList also contains a separate field, 
{{$:/HistoryList!!current-tiddler}}, which is the title of the most 
recently opened tiddler.

To get the titles from the JSON data, I wrote a custom filter, JList.js, 
which allows me to write "jlist[$:/HistoryList!!title]" in a <$list> 
filter.  I then run that through another custom filter I wrote, 
"Unique.js", to remove duplicate titles from the jlist[...] results.  This 
list is then displayed in a popup as the "history" of tiddlers, allowing 
easy navigation back to any tiddler viewed during the session, even if it's 
not currently opened.

-e



-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/ec9d5674-8de2-4a77-ab5d-a92ce9d8aa5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to