[TW5] Closing tid should set focus to previous tid - @Felix

85 views
Skip to first unread message

Mat

unread,
May 28, 2015, 2:22:48 PM5/28/15
to tiddly...@googlegroups.com
[Article from TWaddle]

To my satisfaction, Felix' proposals for user options on how to open a tiddler seem to make it to 5.1.9. Great!

IMO we should have some equivalent option for tiddler closing. Quite often I wish I would come back to the previously viewed tiddler instead of having the tiddler story pulled up into place which puts focus on whatever arbitrary tiddler is there... distracting my little brain, just a tad.

Luckily, Felixes "opening behaviour" mentioned above means that if you set new tiddlers to "open above the current tiddler", then the previous tiddler will be what appears. Still, that is incidental and it also doesn't solve the problem if you opened the new tiddler from the sidebar.

I propose a "$:/core/ui/ControlPanel/Settings/LinkFromBehaviour". It should actually save the viewing history a few steps back so that you can "close this one... aha, so that is what I was doing previously, well I'll close it now... aha, so that is what I did 3 tiddlers ago, well I'll close it now... aha". How many steps should be saved? Well, the reasonable answer is "as many as there are tiddlers open" since those are the only titles relevant. It would really be the list in tab Open, but in another order. (...unless Felixes other invention, Top Story View is used).


Thoughts?


<:-)

Felix Küppers

unread,
May 29, 2015, 6:46:11 AM5/29/15
to tiddly...@googlegroups.com


To my satisfaction, Felix' proposals for user options on how to open a tiddler seem to make it to 5.1.9. Great!

Thanks :)


IMO we should have some equivalent option for tiddler closing. Quite often I wish I would come back to the previously viewed tiddler instead of having the tiddler story pulled up into place which puts focus on whatever arbitrary tiddler is there... distracting my little brain, just a tad.

Yes, that would be nice. But sadly there is no real way to specify which tiddler you previously viewed - I mean maybe on a larger screen you looked at a tiddler more below. Is this the tiddler previosly viewed then? Or do you mean the tiddler previously navigated to? or the one you scrolled into view?


Luckily, Felixes "opening behaviour" mentioned above means that if you set new tiddlers to "open above the current tiddler", then the previous tiddler will be what appears. Still, that is incidental

Incidential or not, it is happening :)



I propose a "$:/core/ui/ControlPanel/Settings/LinkFromBehaviour". It should actually save the viewing history a few steps back so that you can "close this one... aha, so that is what I was doing previously, well I'll close it now... aha, so that is what I did 3 tiddlers ago, well I'll close it now... aha".

This already exists and is what the HistoryList does. The problem with jumping back on closing is: what if you scrolled down the river and close some arbitrary tiddler? should it jump back to the link from where you opened it? What if that tiddler is already closed. what if that tiddler is far at the top (possible since tiddlers can now also be opened at bottom, not just above or below or at top)?


How many steps should be saved? Well, the reasonable answer is "as many as there are tiddlers open" since those are the only titles relevant. It would really be the list in tab Open, but in another order. (...unless Felixes other invention, Top Story View is used).

Or maybe I misunderstood you and you just want to have an open list that is sorted by the order of navigation events?


-Felix

Mat

unread,
May 29, 2015, 1:48:33 PM5/29/15
to tiddly...@googlegroups.com
Felix Küppers wrote:

That is interesting! Not the fact that you're clearly fluent in Swedish, but I'm referring to that the blue color made me think it is a link... but it isn't... but it is definitely something as indicated from my mouse cursor... so I looked at the code and it's marked up with <a lang="sv">. How did you do that? Did it cause translation? Are there more commands that can be used in google groups to format things with markup? (I'm hoping for a way to markup my signature.)


Ok, back to the OP
 
 
Yes, that would be nice. But sadly there is no real way to specify which tiddler you previously viewed - I mean maybe on a larger screen you looked at a tiddler more below. 

Very good point. Still (@everyone) we should consider that the current situation is always scrolling to a, from an information POV, arbitrary tiddler. Even if we can't know the optimal scroll-to every time I do think there is contextual information when you go from tiddler A to B that we can use to make qualified estimations for a good scroll-to tiddler. @anyone, I'd love to hear your ideas on how we can make use of this

If anything, the default story view should scroll up to the immediate tiddler above where there is a chance the closing tiddler came from.

But, more generally, to scroll to the tiddler that contained the link to this closing tiddler is a better-than-current approach. BTW, scrolling back to A if closing B would include the case of scrolling to the immediately adjacent tiddler if that is where it did come from (which is rather likely), both for the case of "open new tiddler below" (as in default story view) and the new "open tiddlers above".

If A is closed then, sure, I guess the adjacent arbitrary tiddler is good enough. The "chain of events" is kind of broken anyway then.


Or maybe I misunderstood you and you just want to have an open list that is sorted by the order of navigation events?

I would guess such a list is where the sequence is taken from. 


Anyway, the point is to set the focus on the most meaningful tiddler for the viewer. How can we do this?


<:-)
TWaddle.tiddlyspot

Mat

unread,
Jun 5, 2015, 4:08:37 PM6/5/15
to tiddly...@googlegroups.com
@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?

Thanks

<:-)
TWaddle.tiddlyspot

Eric Shulman

unread,
Jun 5, 2015, 8:31:05 PM6/5/15
to tiddly...@googlegroups.com
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



Danielo Rodríguez

unread,
Jun 6, 2015, 3:25:55 PM6/6/15
to tiddly...@googlegroups.com
That is definitively a feature I have missed more than once

Jeremy Ruston

unread,
Jun 7, 2015, 4:51:35 AM6/7/15
to TiddlyWikiDev
Hi Mat

As others have noted, the colossal problem is figuring out which tiddler was last viewed. We do track tiddlers as they are navigated, but I'm pretty sure that that is not the same thing.

Best wishes

Jeremy.


On Sat, Jun 6, 2015 at 8:25 PM, Danielo Rodríguez <rdan...@gmail.com> wrote:
That is definitively a feature I have missed more than once

--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
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/2eaa3abb-129c-494d-8f12-8bcbe5cca993%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Jeremy Ruston
mailto:jeremy...@gmail.com
Reply all
Reply to author
Forward
0 new messages