I forgot to explain the attachment: it's a bit of fun, a screenshot of what
happens if you turn the explorer in on itself, clicking through the state
tiddlers that record the state of the tree.

To try it out, just open the explorer and click repeatedly on the prefix
$:/state/tree:

http://tiddlywiki.com/prerelease/#%24%3A%2Fcore%2Fui%2FMoreSideBar%2FExplore

Best wishes

Jeremy.


On Thu, Feb 19, 2015 at 2:28 PM, Jeremy Ruston <[email protected]>
wrote:

> Hi Mat
>
> Thanks for the thoughtful feedback.
>
> First of all, I consider it valuable addition or alternative to the very
>> long lists. Just a lot nicer to use this than to scroll forever.
>>
>
> I'm actually a bit disappointed with it. It was something I'd wanted to do
> for a while, and so had an image in my brain of how it would feel. But as
> it's ended up, it seems clunky and complex. I'm afraid I rather lost
> interest when I came up against an issue that I'll comment on below.
>
>>
>>    - I'm not sure the left numbering adds much. It probably makes it
>>    appear more cluttered.
>>
>> Yes, that's just that I'd not done the styles yet. I'll commit a fix
> shortly.
>
>>
>>    - IMO the slider chevrons are both too big and too heavy. I actually
>>    think that symbol in itself is a bit cluttery -
>>    - The symbol, or any symbol used like this, will add clutter because
>>    it is reapeated so much. (Compare this with bullet lists; bullets there 
>> can
>>    get away with it because they are perfectly aligned but there's still a
>>    balance to ot have them too large etc) ...but a possible solution would be
>>    to hide the slider arrow until onhover because they are a really a bit
>>    redundant as they always and only appear together with the number in
>>    parantheses! I.e leave the counting number in the paranthes visible but
>>    hide the arrow until hover.
>>    - Another aspect is that in e.g the control panel listing of plugins,
>>    the slider symbol (1) is on the right and (2) it is a simpler arrow. Maybe
>>    all of TW should by default keep a consistent slider arrow 
>> design/placement?
>>
>> I've fixed it up to use the single arrows and to put them on the left.
>
>>
>>    - (image).
>>    
>> <https://lh3.googleusercontent.com/-EB36PwTwbTI/VOUjoIgphZI/AAAAAAAAPq8/iWaFUOdyHz8/s1600/Explorer_problem1.PNG>
>>
>> I propose only one of the two almost identical entries is used. On the
>> one hand it is better with the top one, as it is a link. But on the other
>> hand opening the slider for that entry, we see its first item is
>> identically named but with the added "/".  I suggest omitting this step (
>> $:/tags/ControlPanel*/* ) and on that hierarchical level instead
>> immediately list the following blue links (i.e here ending with
>> *.../Info* and *.../Plugins* )
>>
> This is the point that deflected my initial enthusiasm for this experiment.
>
> The heart of the implementation in $:/core/ui/MoreSideBar/Explore is the
> macro "treeNode(prefix)" that renders the children of a specified prefix.
> It is invoked with <<treenode "$:/">> and then calls itself recursively to
> display the grandchildren of the specified prefix.
>
> The filter expression that is used to generate the children is:
>
> [all[shadows+tiddlers]removeprefix[$prefix$]splitbefore[/]sort[title]]
>
> The removeprefix operator is just removing the $:/ from the start of each
> title, discarding any tiddlers that don't start with that prefix.
>
> The splitbefore operator is new. It splits each input string to return the
> portion before the first "/" (if present, and including the slash). If the
> slash isn't present then the entire string is returned.
>
> This algorithm works well apart from the situation you've highlighted:
> where we've got titles that are themselves prefixes of other titles.
> Consider your example, where the prefix being processed is "$:/tags/". Then
> consider the three tiddlers  $:/tags/ControlPanel,
> $:/tags/ControlPanel/Info and $:/tags/ControlPanel/Plugins.
>
> Stripping the prefix gives us ControlPanel, ControlPanel/Info and
> ControlPanel/Plugins. The splitbefore operator then gives us ControlPanel
> and ControlPanel/, hence the two separate entries in the list.
>
> So, what's the fix. Well, the obvious one is to change the splitbefore
> operator so that it no longer includes the trailing separator in the
> returned strings. Then we'd just get ControlPanel back from the filter. The
> trouble then is that we've lost the slash; we know to render
> $:/ControlPanel, but we don't know whether or not there's any further
> tiddlers with that prefix. Anyhow, after going round in circles a couple of
> times I ended up working on other things.
>
> Fixing it is a good homework problem for someone :)
>
>>
>>    - I don't like slow animations, but I would prefer a fast one here
>>    just to smoothen the slider opening a tad. No animation at all here forces
>>    a short, but still existing, cognitive customization process.
>>
>> The reveal widget does have animation capabilities but here the hiding
> and showing is being done by the list widget, which has the more complex
> storyview animation mechanism. We'd need to add a storyview suitable for a
> slider.
>
>>
>>    - The numbers in paranthesis. I recall a few hangouts ago that
>>    someone asked what it was. I've seen it in other contexts so I knew 
>> already
>>    and I do see that it brings value, but it should probably be explicitly
>>    explained in eventual documentation for it. And/or perhaps it could be
>>    toggled hide/show with some parameter?
>>
>> It's the number of tiddlers that bear a given prefix.So, there are 564
> tiddlers starting $:/language/ for example.
>
>>
>>    - The cluttery aspect of mixing bold and normal links (ref #1205
>>    <https://github.com/Jermolene/TiddlyWiki5/issues/1205>) is negatively
>>    enhanced when also black non-links are mixed in (and, again, the heavier
>>    chevron)
>>
>> I'm not sure of the best solution to this. Clearly some of the entries
> are not links and some are links, and so they need to be rendered
> differently, but I agree that the current scheme is distracting.
>
>> Ok, hope this is of some actionable value. Again, I think it is a
>> definite improvement over the looong lists and it takes full advantage of
>> the "pathy" titles in an intuitive way.
>>
> I've fixed the easy stuff and posted a new prerelease to:
>
> http://tiddlywiki.com/prerelease
>
> Best wishes
>
> Jeremy.
>
>
>
>
>> <:-)
>>
>> --
>> 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.
>>
>
>
>
> --
> Jeremy Ruston
> mailto:[email protected]
>



-- 
Jeremy Ruston
mailto:[email protected]

-- 
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.

Reply via email to