Hi everybody,
I posted this at github (https://github.com/Jermolene/TiddlyWiki5/issues/1290) so if anybody wants to comment this, please go to github and discuss it there in order to avoid two discussions. > After careful considerations, I want to make this proposal to change the > default navigating behaviour of tiddlywiki. Please excuse the bold markup, > markdown doesn't support underline and I wanted to highlight certain > points. Also the arguments are not meant to be rude in any way, it is just > an attempt to improve the behaviour of our great tiddlywiki :) > The problem setup > > > Let's say I have 3 Tiddlers open > > A // *fully displayed in the window* > B // *partly displayed in the window* > C // *not displayed; too far down* > D // *not displayed; too far down* > > Unless D is not larger than the page height, clicking on the D-link in the > "Open" Tiddlers Panel will *not* scroll D to the top of the viewport but > only scroll so far down that D is fully displayed with all it's content. > > > Why is this bad? > > > > - This is not a standard web behavior: When using internal website > links to page anchors (#), any browser will scroll *always* until the > anchor is *at the top of the page* and not just till it is in the > viewport somewhere at the bottom. > - It is the philosophy of tiddlywiki to create tiddlers with small > information chunks and link them. So when *aiming at creating a wiki > with tiddlers all having small content bodies*, and navigating to > these tiddlers, they may *not be immediately recognized after the > navigation-scroll* as the *user always looks at the top of the webpage > first* where he/she expects the content to be and the *navigated > tiddler might instead be displayed at the very very bottom*. > - Referring to the example given above, if Tiddler C has a size of 70% > of the page height and D 30% then the user might think he/she falsely > scrolled to C instead of D since D is displayed at the top. > - Frameworks like bootstrap use "hot zones" to unfold the table of > contents on the sidbar if an anchor makes it into the "hot zone" (scroll > this site for an example http://getbootstrap.com/components/). If an > anchor link is clicked, the anchor is focused at the top (in the hot zone) > and the toc unfolds. In tiddlywiki, this is not possible, because we never > know if a tiddler that is navigated to makes it to the top unless its body > is longer than the pageheight or it is newly opened. So it is not possible > to define a zone where we can say "this tiddler in the story-river is > currently focussed" to trigger an event. > > > Conclusion > > > It would be great if we could change the current navigating behavior of > tiddlywiki in a way that tiddlers, whether navigated to or freshly opened, > are always scrolled so that the tiddler frame's top is always at the > viewport top. *This facilitates user orientation and allows programmers > to know where "navigated" tiddlers will appear.* > > Regards Felix > -- 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.
