On 26 Aug 2018, at 20:57, 'Mark S.' via TiddlyWiki <tiddl...@googlegroups.com> wrote:I'm curious about the "stacked" view. When the cards/tiddlers you can't really see nor access the cards that are behind the top card. Would the finished version allow one to click on the edge of a card and have it come forward?

ah, I answered my own question. If the close button always took you to the previously opened tiddler, you could never close them all except with a close all button. Also, I imagine it would be an endless loop of the current and previous tiddler, since when closing one and opening the previous, the new 'previously open' tiddler would be the one just closed.
On Sunday, August 26, 2018 at 5:14:56 PM UTC-5, David Gifford wrote:Yay! Now I won't be "cheating" anymore by using the Zoomin view for a purpose for which it wasn't made!Also I second the goal of having TW 'navigate' back to the previous tiddler. But why a separate button? Why not make that part of the close tiddler button when in STM?
Blessings,Dave
On Sunday, August 26, 2018 at 11:24:06 AM UTC-5, Jeremy Ruston wrote:I’ve started work on improvements to give the core a true “single tiddler mode” (STM), whereby the story river is restricted to only a single tiddler at the time. The current “zoomin” storyview looks like a STM but actually keeps previously open tiddlers in a hidden-but-still-open state that has an impact on performance.You can try out the improvements by visiting the prerelease and engaging the “zoomin” story view (other story views are not affected by these changes):Notes:* The familiar zoomin navigation animation is currently broken by these changes but I intend to repair it* The “open” sidebar tab isn’t much use when there is only a single tiddler in the story river. I’ve added a “History” tab which is much more useful. However, I’m not happy to add another top level sidebar tab, so I want to find another way of resolving things* The “close tiddler” button in the view toolbar isn’t very useful in STM. I’d like to replace it with a button that navigates back to the previous tiddler in the history* Switching back and forth between drafts is much easier with the new “draft indicators” — try editing a tiddler, and then using the sidebar to navigate to another tiddler (see https://github.com/Jermolene/TiddlyWiki5/issues/3409)You can see the implementation details on GitHub:https://github.com/Jermolene/TiddlyWiki5/pull/3412Any feedback or questions welcome,Best wishesJeremy.
--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c8aa4977-307d-4db9-b705-fe59e9171354%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/24ab12c5-3018-4b18-8b1b-4dcbd1c210d5%40googlegroups.com.
title: $:/core/ui/Buttons/close
tags: $:/tags/ViewToolbar
text:
<$button message="tm-close-tiddler" tooltip={{$:/language/Buttons/Close/Hint}} aria-label={{$:/language/Buttons/Close/Caption}} class=<<tv-config-toolbar-class>>>
<$list filter="[<tv-config-toolbar-icons>prefix[yes]]">
{{$:/core/images/close-button}}
</$list>
<$list filter="[<tv-config-toolbar-text>prefix[yes]]">
<span class="tc-btn-text"><$text text={{$:/language/Buttons/Close/Caption}}/></span>
</$list>
<$action-navigate $to={{{ [list[$:/StoryList!!list]before<currentTiddler>]}}}/>
</$button>
I was interested in the ability to use a link to a tiddler in a wiki (from another tiddlywiki or website) that opened a tiddler, somewhat like a permalink would do, except to open the selected tiddler and nothing but that tiddler, no side bar, toolbar (optionally) nothing. An example use case is a link or iframe to https://tiddlywiki.com/#Filter%20Operators as a reference.
Lets not throw the baby into hot-water urging "static" on this. I think TonyM's point was that we can increase flexible intelligence in delivery via single Tiddler (no cruft) Mode. I think performance is likely to be good.
The key for me is a way to access the single tiddler view of a tiddler in any wiki which I presume means being able to address it on the address line/url
This is why am requesting it in a release as we will be able to avoid installing something to achive it.
For wikis we own, perhaps even host with update we could perhaps already host say a survey questionnaire tiddler that is all that some one sees from following the url.
Regards
Tony
Agreed, I want interactive not static.
The open in new window option could be fixed to use css correctly, more faithfully display the tiddler content then provide a way to activate it through the address line eg: wikiaddress###tiddlername
Regards
Tony
On 27 Aug 2018, at 14:24, @TiddlyTweeter <Tiddly...@assays.tv> wrote:Ciao Mat
@TiddlyTweeter wrote:I think performance is likely to be good.
Mat repled ...Well, the "performance" is to a great extent a result of the wiki ...
Yes but. The assemblage of the sidebar is significant. Its not just size, its complexity for render. Reducing all "cruft" I think will improve performance?
And, why have it when you don't need it?
I also find this concept very appealing... even if I must admit I'm not quite sure what I'd do with them ;-)
I think TonyM, or at least I, was pointing to Use Cases where the content of the TW could contain disparate items AND gets focused on ONE at a time, un-menued.
An example could be a Newsletter. You only want the latest to show, or one where a topic is directly addresses a raised issue. Listing them all would more be a service for archivists than end-users, if you get what I mean?
In short, many Use Cases, I think benefit from minimal delivery of "ALL BUT ONLY" in one Tiddler/"Effective Page".
Best wishes
Josiah
--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b7c0e225-c5ca-43a3-a972-1305d1f8c8a1%40googlegroups.com.
--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c60128e7-8dfb-49cc-8ac8-72eaee5f7fcc%40googlegroups.com.
The new Zoomin view also creates an empty story, if your users close all the tiddlers from the history.
I'm not sure if you're still monitoring this thread based on the previous comments, but for myself and all of the users at my company, a purpose-built single page mode would be great. In almost all circumstances my goal is to make it seem more 'normal' to my end-users (Microsoft dominated U.S. corporate environment).
I'm adding users based on overlap with SharePoint sites / lists. The keys to increase adoption at my company based on the user feedback I'm getting is a few things:
- General theme. People are used to header based buttons and left-navigation. The "Material Theme" posted on the Groups here has got me pretty close.
- Single page mode. People get confused by all of these "floating windows" and accidentally close them all leaving it empty. The pre-TW5 with single page mode was closer to my current desires.
Personally I don't mind the default design, but from a "send to people and they intuitively know how to navigate it" standpoint, the single page mode would help a lot. See screenshots if are interested in seeing how far I've got compared to a SharePoint example.Just wanted to add a different perspective. I would *kill* for a SharePoint theme that lumps all of this together.