felixhayashi / tw5-topstoryview Goto Github PK

Once Jermolene/TiddlyWiki5#1662 is merged, the "top story plugin" shall only be responsible for making tiddlers scroll till they their title is visible at the top of the window. It shall not do any rearrangement anymore.

1. The draft is closed.
2. TW scrolls up and immediately all the way back down.
3. The draft's underlying tiddler is correctly put at top and the scroll should be only to the top

A "bug" spotted by @twMat at ggroups:

Small bug(?): If you, for instance on the TiddlyMap site, click tab Open. Then click the edit button on any tiddler not on top (i.e scroll down). This sets the Draft on top... but this is not reflected in tab Open.

https://groups.google.com/d/msgid/tiddlywiki/0605cb75-738f-4ccb-82fd-f4f52772bc38%40googlegroups.com?utm_medium=email&utm_source=footer

The TW5-TopStoryView is split into two Plugins

• The TW5-HotZone Plugin: This will fire a change everytime another tiddler is scrolled into a certain "hotzone". The plugin will be used for TiddlyMap's live view (felixhayashi/TW5-TiddlyMap#121).
• The TW5-TopStoryView Plugin: This plugin will make sure, the navigated tiddler frame is always scrolled to the top of the window.

The open at top behavior will be outsourced to the core as already discussed in #7.

This problem affects the pop and the classic storyviews!

The topstoryview gets confused if a draft is open somewhere in the river and the original tiddler gets opened in the river at the very top and then the draft button is pressed:

1. The original tiddler is removed
2. draft is opened
3. The previous draft is removed

I thought about this a long time and my conclusion is that it is better to not move a draft to the top of the river like a newly inserted tiddler and instead open and close it at the same place like the original tiddler.

Why?

1. When e.g. wanting to delete a whole set of tiddlers from the system that exist at the bottom (worst case) of in the river you'll always have to click "edit" (which will open the tiddler at the top), delete it and scroll back down to open another tiddler.
2. When editing a tiddler you have a goal in mind, you want to add delete or modify information. So it is very distracting if a tiddler scrolls to the top after you clicked "edit". It might even cause you to forget what you wanted because the scroll animation distracts you.

Very minor:

Ctrlpanel > Plugins > ...to see the information tabs for a plugin.

TW plugin manager only default-displays an information tab if it is titled "readme" - not eg. "README" or "Readme" (latter is the case with TopStoryView).

Did I mention this is a minor point? No - oh, sorry, it is a minor point.

Hello @felixhayashi

I just noticed a.. funny? behavior in your view. If you navigate from a tiddler to another, then it appears on top of the first one and navigation occurs. If you click the same button (I did not tried with links) to navigate again to that tiddler without moving the scroll at all, then the tiddler that is on top will appear at bottom. Of course you have to use two tiddlers that fits in the screen at the same time.
I don't know if this could be considered a bug.

Regards.

Select top story view and open any number of tiddlers. You will be able to scroll further down than you should be, like there is some fixed amount of empty space added at the bottom of the story river.

Tested with TiddlyWiki 5.1.22, Chrome and Edge. There seems to be more "space" at the bottom in Chrome than in Edge.

Thank you very much for this and well done. I'm using it on a personal TW based tool and it is improving the experience a lot: Tiddlers that would not be visible after navigation (because you can see a small portion of them already) are now displayed perfectly. Would be possible to change where the tiddlers appears? I like how it navigates but I would prefer to have the tiddlers appearing below the current one.
https://groups.google.com/d/msgid/tiddlywiki/dac9fa9f-862b-43d1-97a2-2c67b7c0a95a%40googlegroups.com

Scrolling is always until the top is reached, but as @danielo515 points out, insertion/opening could be done at bottom. This should be possible via an option.

What I can do is to

• always open tiddlers at the bottom of the river instead at the top.
• I can also add an option to make the plugin behave completely like "classic" and only always scroll to the top of the newly inserted tiddler or the linked tiddler...

When installing the TopStoryView, change the story view into "top" at next reboot.

I assume it happens quite often that the user forgets to change the story view. Then the live view won't work properly.

The "offset settings" (in $:/config/topStoryView) is reached via Ctrlpanel>Plugins>TopStoryView>Configuration. This is IMO too obscured.

I propose that TopStoryView also adds a setting to $:/core/ui/ControlPanel/Settings along with those other comparable settings there. Perhaps a suitable location there wuold be close to the "Tiddler Opening Behaviour" section ($:/core/ui/ControlPanel/Settings/LinkToBehaviour)

Problem is: the insert function should not call scrollIntoView() – this is done later when TW invokes navigateTo()!

I would like (to discuss) a story river where instead of scrolling through the story to get to an already open tiddler, that the story order itself changed and the jump would actually move the tiddler to the top. That way anything jumped to, whether new or already open would sit at the top of the story. This sounds counterintuitive but actually takes full advantage of the nonlinearity of hypertext while in contrast jumping around in a stroy river implies that there is some "right" order to a flow of tiddlers, namely the order they are first opened in. If everything always moves to the top of the river no matter what context it is opened from, and whatever the source of the jump moves down a notch you always have a sort of archaeology of the story you are creating. Recent things are near the surface, and tiddlers that have not seen focus in a while are further down. Saq Imtiaz's always open on top used to do this in TW2, which I think @tobibeer or someone updated. THis river idea provides a consistency as well, in that you are never scrolled somewhere you don't expect -- whatever you are reading is at the top and focused, and whatever you read just before is immediately below. WHile it may not seem like a big difference, if you use it for a while it gives a sense of bearings that is less disorienting and easier to manage than scrolling around. The other way to do this is with a tabbed view instead of a river, in which case the "whose on top" issue becomes irrelevant. But that is a whole nother thing that would be a differnt plugin. I already raised this over at the main TiddlyWiki site, in a conversation you were in along wth @tobibeer and others. If you want to try the tabbed version of TW2, I have one called FiddlyWiki that you can try to get the idea. It used to be open-on-top before the tabs, but both basically serve the same function.

ANyway, thanks for all your work on this and TiddlyMap, and if this is a no-go, you can just tell me to learn to code already and do it myself! I wish I could.