Another possible feedback

It you are aware, there is a changecount value added to, with each change 
of a tiddler in the current session. A Simple icon with 1-9 then + on 
tiddlers who have a change count value quickly displays which ones you are 
editing a lot in the current session. 

We can also review which tiddlers are in the current history list whether 
they are still open or not.


Regards
Tones

On Tuesday, 1 September 2020 10:39:37 UTC+10, TW Tones wrote:
>
> Brian,
>
> Nice to hear a contra-view however;
>
>    - No solution like the one discussed would be compulsory and unlikely 
>    even in the standard distribution
>    - In some ways I am proposing a defacto standard that a number of 
>    people agree to, you use it if you want too
>    - All elements should be selectable, and as I proposed they need to be 
>    subtle.
>    - Whilst I think developers may love it, I disagree with the 
>    suggestion that new users would not benefit from this, or even innocent 
>    users of a website that happens to be tiddlywiki.
>       - The reason is people do respond to subtle information even if not 
>       consciously
>       - The information should be of use to the user but we do not always 
>       know what is useful to the user ahead of time.
>       - Tags and view templates, title and groups or lists all can be of 
>       relevance to the user because that is the way tiddlywiki works
>       - Just as someone can choose a theme, they can a choose rich 
>       highlight mode or not
>          - I would argue, even promote such a solution that it would have 
>          far less impact on a user than changing the theme.
>       - You are saying "not outside there content", but I am suggesting 
>    bringing out hidden content, in ever so subtle ways.
>
> I did not put the argument in my suggestion, but there is a science and 
> cognitive basis to my proposal. One that recognises that humans can extract 
> information even collected subconsciously, if that information is 
> observable.  There is also a driver in the human mind to abstract knowledge 
> then apply it in different places - this is a key feature of creativity.
>
> if any of this kind of styling were added to the default install, I would 
>> hope that they are not active by default, but made easily discoverable in 
>> the Control Panel by someone who is interested in having more meta 
>> information readily available.
>
>
> Of course, but time will tell if it is an advantage to the naive, new user.
>
> Regards
> Tones  
>
>
>
>
> On Tuesday, 1 September 2020 04:48:40 UTC+10, Brian Radspinner wrote:
>>
>> I really like this as an idea for a *developer's plugin*, but *not as 
>> default styling*. IMO, most of the mentioned styling is superfluous and 
>> distracting to a new user, or one who doesn't plan on using TW as a 
>> development platform. 
>>
>> If the idea that all tiddlers are just components that are technically 
>> all at the same level and can change levels at any time, I don't like the 
>> idea of making tiddlers look different outside of their content based on an 
>> individual's needs. System tiddlers are already separated by their titles 
>> and being relatively hidden, additional visual cues are redundant; unless 
>> you have a specific need to have a specific group of system tiddlers stand 
>> out for your own personal needs.
>>
>> If any of this kind of styling were added to the default install, I would 
>> hope that they are not active by default, but made easily discoverable in 
>> the Control Panel by someone who is interested in having more meta 
>> information readily available.
>> On Monday, August 31, 2020 at 3:27:44 AM UTC-7 PMario wrote:
>>
>>> Hi Foks,
>>>
>>> Since there are different elements shown. I did an experiment some time 
>>> ago for a different thread, that defined some colors for TW tables. 
>>>
>>> I'm kind of proud about the idea for styling different elements _and_ 
>>> areas within a TW table. 
>>>
>>> The example used hardcoded styling, which is acitve as soon as a tiddler 
>>> is visible. ... So the user "className" must be unique. 
>>>
>>> Examples attached. 
>>>
>>> Link to: Original thread 
>>> <https://groups.google.com/d/msg/tiddlywiki/6XSqLdhH1dQ/psFmcV9JCAAJ>.
>>>
>>> have fun!
>>> mario
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/41dea1fd-3082-4cb7-8dcd-c5323b02f2ffo%40googlegroups.com.

Reply via email to