All,

I think we are missing something here, with the new layout switch cloning 
the required tiddlers for  new layout, and modifying the equivalent to 
$:/core/ui/ViewTemplate/body to do the desired behavior. The underlying 
tiddlers will update in the core, and returning to the default layout will 
allow the user to see the updates. The fact is your "extra layout" may 
break if something changes in the core but you have copies of the older 
version in your layout definition, and you can just switch layouts.

Remember when cloning a set of tiddlers for a new layout, rather than clone 
you can transclude a core tiddler. Add to that the ability to review the 
differences would make this easy.

A tool to clone a tiddler by replacing the text field with a transclusion 
of the original OR the content (if you wish to edit the copy) would 
simplify this.

What I am suggesting is to clone tiddlers and use a provided hackable 
feature such as the Layout switch, you will then have both your modified 
tiddlers and the core tiddlers can remain shadows only and thus receive 
updates.

Regards
Tones


On Friday, 26 February 2021 at 04:35:09 UTC+11 Mat wrote:

> OK so here's a small thing for overwritten shadow tiddlers. For (only) 
> these tiddlers you get a little button in the toolbar which, when clicked, 
> opens the tiddler in edit mode with the split screen and "diff comparison 
> to shadow" activated. 
>
> This does not solve the question "Does my overwrite need attention because 
> of the update?" but it is at least some small thing to support overwrite 
> handling. 
>
> <:-)
>
> On Thursday, February 25, 2021 at 5:46:07 AM UTC+1 [email protected] 
> wrote:
>
>> How about (automatically) tagging changed tiddlers in the editor?? 
>> [[is[shadow]] contains all the automatic tiddlers, $:/config/AutoSave etc. 
>> $/tags/ModifiedShadow from the editor would not. 
>> Or include a comparison in the plugin display. Just happened to tinker, 
>> might look something like this 
>> https://test-plugins.tiddlyhost.com/#%24%3A%2Fplugins%2Fsvendrion%2Flittle_tools%2FChangedShadows:%24%3A%2Fplugins%2Fsvendrion%2Flittle_tools%2FChangedShadows
>>
>> /de Wie währe es, im editor geänderte tiddler (automatisch)zu taggen? 
>> [is[shadow]] enthält die ganzen automatischen tiddler,  $:/config/AutoSave 
>> usw.  $/tags/ModifiedShadow vom editor würde das nicht. 
>> Oder in die Pluginanzeige einen Vergleich einbauen. Hab zufällig gerade 
>> gebastelt, könnte so ähnlich aussehen wie 
>> https://test-plugins.tiddlyhost.com/#%24%3A%2Fplugins%2Fsvendrion%2Flittle_tools%2FChangedShadows:%24%3A%2Fplugins%2Fsvendrion%2Flittle_tools%2FChangedShadows
>>
>>
>> si schrieb am Montag, 22. Februar 2021 um 17:16:31 UTC+1:
>>
>>>
>>> AFAIK if you edit a shadow tiddler this is the equivalent of just 
>>> creating a new tiddler with the same name, which overrides the original 
>>> shadow tiddler.
>>>
>>> I remember someone mentioning that tweaking core tiddlers is a bad idea 
>>> in general because it means that that tiddler won't get updated when you 
>>> import a new version of the plugin/core. Is this correct? If so what is the 
>>> best way to approach tweaking shadow tiddlers?
>>>
>>> (An example of a tweak that I have made is adding a dynannotate widget 
>>> to $:/core/ui/ViewTemplate/body, which allows me to add annotations to 
>>> all of my tiddlers. I have also made a few tweaks to plugins like Streams.)
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d14be930-6e94-4f0d-a69d-c29e46ce638bn%40googlegroups.com.

Reply via email to