[tw5] Tiddlywiki 5.1.23 when it will be released?

[Atronoush Parsi]

TW 5.1.23pre has tons of new features, it is Oct 20, 2020
Is there any chance to have this new release anytime soon?

--Atro

-- 
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/CAKHVXmqOKDzU-BpQtKYEpur_rKEtrkcvkO%2Bb0W8Ha8ZgWDXtTA%40mail.gmail.com.

[tw5] Re: Playing Sounds?

[TW Tones]

Eric,

Thanks for filling in the gaps. Do you know how to import a sound file and 
address it in the audio tag?

Tones

On Tuesday, 20 October 2020 15:08:01 UTC+11, Eric Shulman wrote:
>
> On Monday, October 19, 2020 at 7:14:11 PM UTC-7, Game Dungeon wrote:
>>
>>
 I want to play a short little ding every time I check something off my 
 to-do list. Any way to do that in ~TiddlyWiki?  

>>>
> Try this:
>
> 1) Create a tiddler "DoneSound", containing:
> 
>   
> 
>
> 2) In your <$checkbox> widget, add a "checkactions" parameter, like this:
> <$checkbox ... checkactions="""<$action-sendmessage $message="tm-notify" 
> $param="DoneSound" />""">
>checkbox text goes here
> 
>
> 1) The audio element uses "autoplay" and "controls", with a style 
> attribute to make the display of the controls more compact than the default 
> appearance.
> 2) The $checkbox widget uses checkactions="..." to send a "tm-notify" 
> message to display the DoneSound contents in the upper right corner of the 
> page.
> 3) Note that the notification message has a display duration of 3 seconds, 
> so it will only play up to 3 seconds of sound before automatically going 
> away.
>
> enjoy,
> -e
>

-- 
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/0905ba7f-2df4-4a7d-b03c-a11052cb577do%40googlegroups.com.

[tw5] Re: How to view tiddlers with unknown type as pre-formatted code

[bimlas]

TW Tones,

Forgive my ignorance, but I have rarely if ever seen any syntax 
> highlighting anywhere, in css etc...
>

   - Open a CSS and JS tiddler in 
   empty.html, 
https://tiddlywiki.com/empty.html#%24%3A%2Fboot%2Fboot.css:%24%3A%2Fboot%2Fboot.css
 
   %24%3A%2Fcore%2Fmodules%2Fbrowser-messaging.js for example.
   - Install Highlight plugin, restart the wiki
   - Open the tiddlers again, you should now see them with syntax 
   highlighting

Or am I misunderstood and you mean edit mode? In this case, Codemirror and 
the corresponding Codemirror "add-ons" (CodeMirror Mode CSS for example) 
must be installed. Besides, I don't know of any other syntax highlighting 
method.

we do not have a highlighter for wikitext and widgets.
>

That's right. I'm using the following Codemirror "extension", which gives a 
very nice syntax highlight in edit mode:

https://github.com/adithya-badidey/TW5-codemirror-plus 

-- 
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/88cd4e44-d0aa-4696-89f1-1f2b16e284aen%40googlegroups.com.

[tw5] Re: Playing Sounds?

[Eric Shulman]

On Monday, October 19, 2020 at 7:14:11 PM UTC-7, Game Dungeon wrote:
>
>
>>> I want to play a short little ding every time I check something off my 
>>> to-do list. Any way to do that in ~TiddlyWiki?  
>>>
>>
Try this:

1) Create a tiddler "DoneSound", containing:

  


2) In your <$checkbox> widget, add a "checkactions" parameter, like this:
<$checkbox ... checkactions="""<$action-sendmessage $message="tm-notify" 
$param="DoneSound" />""">
   checkbox text goes here


1) The audio element uses "autoplay" and "controls", with a style attribute 
to make the display of the controls more compact than the default 
appearance.
2) The $checkbox widget uses checkactions="..." to send a "tm-notify" 
message to display the DoneSound contents in the upper right corner of the 
page.
3) Note that the notification message has a display duration of 3 seconds, 
so it will only play up to 3 seconds of sound before automatically going 
away.

enjoy,
-e

-- 
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/ed013f2d-8fcf-4a82-b7ef-0276daf917fdo%40googlegroups.com.

[tw5] Re: Playing Sounds?

[Game Dungeon]

How would play this on the check though?

On Monday, 19 October 2020 at 21:01:10 UTC-5 TW Tones wrote:

> Hi,
>
> This HTML works is the done.mp3 is in the same location as a tiddlywiki 
> html file
>
> 
>   
>   Your browser does not support the audio element.
> 
>
>
> Perhaps placing this in an alert that closes after sufficient time.
>
>
>
> Regards
> Tony
>
> On Tuesday, 20 October 2020 05:12:59 UTC+11, Game Dungeon wrote:
>>
>> I want to play a short little ding every time I check something off my 
>> to-do list. Any way to do that in ~TiddlyWiki?  
>>
>

-- 
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/9619c997-8f5d-4974-a9d0-7787f88c7843n%40googlegroups.com.

[tw5] Re: Playing Sounds?

[TW Tones]

Hi,

This HTML works is the done.mp3 is in the same location as a tiddlywiki 
html file


  
  Your browser does not support the audio element.



Perhaps placing this in an alert that closes after sufficient time.



Regards
Tony

On Tuesday, 20 October 2020 05:12:59 UTC+11, Game Dungeon wrote:
>
> I want to play a short little ding every time I check something off my 
> to-do list. Any way to do that in ~TiddlyWiki?  
>

-- 
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/5450d775-9687-41ce-972f-5bc7ce08869eo%40googlegroups.com.

[tw5] Re: How to view tiddlers with unknown type as pre-formatted code

[TW Tones]

Bimlas,

Forgive my ignorance, but I have rarely if ever seen any syntax 
highlighting anywhere, in css etc... as well as surprised we do not have a 
highlighter for wikitext and widgets.

I just installed the core plugin but still cant see anything. A little 
Guidance would be appreciated.

FYI joshuas JSON mangler also includes CSV as a valid type, but when I drop 
an Excel generated CSV it gains another type. 

Regards
Tones


On Monday, 19 October 2020 22:32:06 UTC+11, bimlas wrote:
>
> Note for other users: if syntax highlighting doesn't work, set the 
> appropriate types in the Highlight.js plugin! From the documentation:
>
> You can also specify the language as a MIME content type (eg text/html or 
> text/css). The mapping is accomplished via mapping tiddlers whose titles 
> start with $:/config/HighlightPlugin/TypeMappings/.
>

-- 
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/f2f4bc9d-71c5-41b8-a001-94742346dd32o%40googlegroups.com.

[tw5] On To-DO List

[Game Dungeon]

I am rather new to ~TiddlyWiki, I have made my own To-Do list, but some by 
other people have blown mine out of the water :). Any tips on improving it 
(And I guess my tiddlers in general?) 

https://hastebin.com/dusaqajugu.php-template


-- 
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/5b766ab6-4a57-4301-a2b0-10120168116an%40googlegroups.com.

[tw5] Playing Sounds?

[Game Dungeon]

I want to play a short little ding every time I check something off my 
to-do list. Any way to do that in ~TiddlyWiki?  

-- 
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/9f27ac01-3c6d-4987-a1a1-b55e17e5657fn%40googlegroups.com.

Re: [tw5] A HOWTO: Filtered transclusion example (with transclusion template and simple markdown table) for my Template Documentation

[Felicia Crow]

Well so far it was a good Monday since my brain was willing to work again 
after a weekend of absolute no productivity and an absolute inability to 
concentrate on anything longer than five minutes.
And as for the "a certain way" I think one can take a look at your wikis 
and get a good idea.

Personally I don't have much of a plan beyond a more or less defined end 
goal so everything evolves very organically as I need it or think of it 
since I love to tinker with those things, but after the first thought of 
the idea itself the second is: Great now how many options can I cram into 
before it becomes bloated but it still can be used in more than one 
specific situation so that I have to only rewrite things in on place, and 
the third: What parts of this idea can I automate so I don't have to even 
touch them in the future once I am happy with how it works. Yet especially 
this automation but also the modular approach come with certain 
expectations and systems attached for it to work. Mostly in the form of 
fields and macros that select, sort, edit or create tiddlers based on the 
value of those fields.

For instance to use one of my more over-engineered examples: I have a 
button and a text field to create a new category for my world building 
since those can differ from case to case. Each category created this way 
has two components: The category tiddler itself that lists all entries 
belonging to it and allowing sorting them in different ways and a tiddler 
that is used as a template when creating a new item for the category. When 
I use one of the three ways to create a new item of this category - over 
the new tiddler button, from my missing tiddlers list or from the category 
tiddler itself - the same macro is called. This macro looks with which 
value it was called and then based on that looks for the right template to 
use and creates the new tiddler including adding the title when called from 
the missing tiddlers list. This only works because there are specific 
fields linking the template to the category that can't be changed or it 
won't work.
And while there is the very high chance that I eventually will look at 
having to change dozens of tiddlers because I changed my mind about now 
wanting an age field for all the characters instead of their birthday like 
in the template, it has to me the benefit that I can quickly create those 
entries and categories and having them already linked together without 
having to remember to fill out the specific fields/add the right tags to 
make it work.

I think this is also where once again the differing use case comes in. My 
whole main project - when I don't wander off to do something that seems 
more fun at the moment for instance tinker with question/problems posted 
here - is more in the vain of for instance noteself as to provide an 
overlay over the tiddlywiki core for a more or less specific use case. If I 
would have something more like your product reviews - maybe reviews of 
books that I have half finished - I probably would tend to a more open 
structure that I can more easily reorder when I want in the way I feel 
like, although probably still with more macros since great is still 
followed by how can I use it in more than one place with slightly different 
options while having one place to rewrite things.

So and talking about wordy, I would not call this answer short either, hope 
it is not too much of a wall of text and at least somewhat understandable.

A good Monday to you since here by now Tuesday is already on the imaginary 
horizon.
Felicia



On Monday, 19 October 2020 16:13:34 UTC+2, Charlie Veniot wrote:
>
> G'day Felicia, 
>
> Happy Monday !  (May seem like an oxymoron, but who knows?  Could be the 
> best Monday ever ...)
>
> I have a whole whack of metrics involved in my approach-taking decisions, 
> usually a snap choice to avoid getting stuck in the mud and overthinking 
> (me shoving sticks in my own wheels), and tweak as I go along when I reach 
> some pain-in-the-caboose tipping point (or have some bright or plain old 
> goofy idea I want to try).
>
> More often than not, I tend to get very irritated with "bloat" and 
> duplication/redundancy, and I find myself doing whatever to shave away even 
> just a few characters .
>
> A bit of a "take care of the pennies and the pounds will take care of 
> themselves" ?
>
> Then again, if "the fun in it" way surpasses any kind of irritation, then 
> I stick with the fun until no longer fun.  Well, the fun quickly takes a 
> nose-dive whenever I see an approach that is going to create an ugly mess 
> down the road.
>
> Being a software developer and always considering the design of 
> everything, I'm always thinking:  make everything easy/quick to adapt / 
> evolve / change (as per any new discovery or as per any mood strikes me).  
> That's the beauty of any wiki product: when things are done a certain way: 
> a wiki makes it really easy to completely reshuffle everything.
>
> Good 

[tw5] Playing Sounds?

[Game Dungeon]

I want to play a short little ding every time I check something off my 
to-do. Any way to do that in tiddly wiki?

-- 
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/fd8ea6f1-83e2-4dfa-bd19-d83fd814c6fen%40googlegroups.com.

[tw5] Re: Muuri Storyview

[BurningTreeC]

@Saq,

>One quick thought. Would it be doable as an option to have a specific part 
of the tiddler div be the element that is the drag handle? Perhaps the 
title, or a horizontal div above the title? It would allow for a UX where 
dragging tiddlers within/across stories is always enabled, and yet it 
doesnt interfere with scrolling, copying text etc.

Yes that's possible, I just have to add an attribute or a configuration 
tiddler for that... makes sense to me, so I'll implement this. Thanks for 
the idea

BTC
saq.i...@gmail.com schrieb am Montag, 19. Oktober 2020 um 17:04:09 UTC+2:

> @BTC 
>  
>
>> My goal is that dragging between stories becomes very easy using the 
>> muuri storyview. I hope I can achieve that soon
>>
>
> One of the cool things already is that if you set Muuri to use just one 
> column, it gives an experience close to the classic storyview but you can 
> drag to re-order tiddlers within the story. So I am optimistic about your 
> goal. :)
>
> One quick thought. Would it be doable as an option to have a specific part 
> of the tiddler div be the element that is the drag handle? Perhaps the 
> title, or a horizontal div above the title? It would allow for a UX where 
> dragging tiddlers within/across stories is always enabled, and yet it 
> doesnt interfere with scrolling, copying text etc. 
>
> Note I did see that there is a SELECTTEXT_CONFIG but have not fiddled with 
> it, so it could turn out that the above isn't really necessary.
>
> Thanks BTC, excited to see where this leads.
> Cheers,
>
> Saq
>

-- 
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/b5b57462-e04b-46d1-8c6d-c355acb90039n%40googlegroups.com.

[tw5] Re: TiddlyTools/Time/AutoSaver and Streams don't play well together?

[cmari]

Thank you so much, this is great - and thanks especially for the 
explanation.
cmari

On Sunday, October 18, 2020 at 11:57:22 PM UTC-7 saq wrote:

> Thank you Eric. I'll push an update as soon as I get the chance.
>
> Regards,
> Saq
>
>
> On Monday, October 19, 2020 at 7:31:50 AM UTC+2, Eric Shulman wrote:
>>
>> On Sunday, October 18, 2020 at 5:00:36 PM UTC-7, cmari wrote:
>>>
>>> I'd like to be able to use the features of both 
>>> TiddlyTools/Time/AutoSaver 
>>>  and 
>>> Streams . But after 
>>> some experimenting, it seems that if I add both of these plugins to an 
>>> otherwise empty 5.1.22 TW, when I try to use the (TiddlyTools) Autosaver 
>>> option of "confirm before saving", I get the red javascript error 
>>> ("Uncaught TypeError: Cannot read property 'toString' of null). Is there 
>>> something I can do to prevent this error?
>>
>>
>> I took a look at the browser's debugging console, where it reports:
>> streams.html:13257 Uncaught TypeError: Cannot read property 'toString' 
>> of null
>>
>> $tw.utils.error @ streams.html:13257
>> $:/plugins/sq/streams/selection-vars-tweak.js:29 Uncaught TypeError: 
>> Cannot read property 'toString' of null
>> at TimeoutWidget.Widget.invokeActionString ($:/plugins/sq/streams/
>> selection-vars-tweak.js:29)
>> at eval (TiddlyTools/Time/action-timeout.js:40)
>>
>> Here's a summary of what occurs:
>>
>>1. The *TiddlyTools/Time/AutoSaver *countdown timer is processed by 
>>the <> macro,
>>2. which is defined in *TiddlyTools/Time/CountDown* and is called 
>>from *TiddlyTools/Time/Ticker*,
>>3. which is invoked once per second by 
>>*TiddlyTools/Time/action-timeout.js*,
>>4. which uses the *TWCore "invokeActionString()"* method.
>>5. which has been "hijacked" by the Streams plugin code contained in 
>>*$:/plugins/sq/streams/selection-vars-tweak.js*,
>>
>> Take note of these two lines from 
>> *$:/plugins/sq/streams/selection-vars-tweak.js*:
>>  if(activeElement && selection && (activeElement.tagName === "INPUT" || 
>> activeElement.tagName === "TEXTAREA")) {
>>  variables["selectionStart"] = activeElement.selectionStart.toString();
>>
>> This is where the error actually occurs.
>>
>> The problem is that the code is checking for *activeElement.tagName === 
>> "INPUT"*, which is OK when the activeElement has a "selectionStart" 
>> property.  However, in the AutoSaver settings panel, the "confirm before 
>> saving" checkbox is also an HTML "input" element, but because it is not a 
>> *text* element, it has no "selectionStart" property. Thus, attempting to 
>> invoke "toString()" throws the "Uncaught TypeError: Cannot read property 
>> 'toString' of null" error that is reported in the browser's debugging 
>> console and by the TiddlyWiki RMOD ("Red Message of Death").
>>
>> Note that 
>> https://developer.mozilla.org/en-US/docs/Web/API/DocumentOrShadowRoot/activeElement
>>  says 
>> this:
>>
>> Often activeElement will return a HTMLInputElement or HTMLTextAreaElement 
>>> object if it has the text selection at the time. If so, you can get more 
>>> detail by using the object's selectionStart and selectionEnd properties. 
>>> Other times the focused element might be a  element (menu) or an 
>>>  element, of type "button", "checkbox", or "radio".
>>
>>
>> The fix is to change the code in 
>> *$:/plugins/sq/streams/selection-vars-tweak.js *to ensure that when the 
>> *activeElement.tagName 
>> === "INPUT"*, the *activeElement.type === "text"*, which would then 
>> exclude "button", "checkbox", or "radio" input elements.
>>
>> Something like this will do the trick:
>>  if(activeElement && selection && ((activeElement.tagName === "INPUT" && 
>> activeElement.type === "TEXT") || activeElement.tagName === "TEXTAREA")) 
>> {
>>
>> If you edit the *$:/plugins/sq/streams/selection-vars-tweak.js* shadow 
>> tiddler and change the line of code as shown above, that will bypass the 
>> problem until Saq can provide an update to the Streams plugin.
>>
>> -e
>>
>

-- 
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/b4a38ad8-d9a7-4699-b806-17a0e2894259n%40googlegroups.com.

[tw5] Re: Muuri Storyview

[Eric Shulman]

On Monday, October 19, 2020 at 8:04:09 AM UTC-7, Saq Imtiaz wrote:
>
> One of the cool things already is that if you set Muuri to use just one 
> column, it gives an experience close to the classic storyview but you can 
> drag to re-order tiddlers within the story. So I am optimistic about your 
> goal. :)
>

Note that you can also drag to "re-order tiddlers within the story" using 
the Sidebar "Open" tab in a standard vanilla TiddlyWiki.

-e

-- 
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/0d5c35d0-8de9-4cd4-a02b-7aedaec238f2o%40googlegroups.com.

[tw5] Re: button to create tiddler tagged with currentTiddler title, author field variable

[Eric Shulman]

On Monday, October 19, 2020 at 7:30:49 AM UTC-7, Sapphireslinger wrote:
>
> When I hit the "New Quote" button embedded in all my book tiddlers, I want 
> to get a new tiddler tagged with (1) the title of the currentTiddler, (2) 
> the variable contained in the author field and (3) the word "quote". 
> I searched and tried all kinds of permutations for 2 hours but can't 
> figure it out. The version below makes a tag for every word of the tiddler 
> title and the author field, besides creating a weird field. :P 
>

Give this a try:
\define newtags() [[$(currentTiddler)$]] [[$(author)$]] [[quote]]

<$list filter="[prefix[Book -]]">
   <$button> New Quote
  <$vars author={{!!author}}>
  <$action-sendmessage $message="tm-new-tiddler" title=<> tags=<> />
  
   
   <$list filter="[tag!sort[title]]">
   <$link><$transclude field="title" mode="block"/>
   <$transclude field="text" mode="block"/>
   


Notes:
1) The newtags() macro constructs the desired tags field value, using 
[[...]] around each tag to handle spaces embedded in the current tiddler's 
title and author fields
2)  The $button gets the author field value as a variable, so that the 
newtags() macro can refer to $(author)$ internally

enjoy,
-e

-- 
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/b925c2f9-be8d-4863-885d-f9c9f477d5b4o%40googlegroups.com.

[tw5] Re: Muuri Storyview

[Saq Imtiaz]

@BTC 
 

> My goal is that dragging between stories becomes very easy using the muuri 
> storyview. I hope I can achieve that soon
>

One of the cool things already is that if you set Muuri to use just one 
column, it gives an experience close to the classic storyview but you can 
drag to re-order tiddlers within the story. So I am optimistic about your 
goal. :)

One quick thought. Would it be doable as an option to have a specific part 
of the tiddler div be the element that is the drag handle? Perhaps the 
title, or a horizontal div above the title? It would allow for a UX where 
dragging tiddlers within/across stories is always enabled, and yet it 
doesnt interfere with scrolling, copying text etc. 

Note I did see that there is a SELECTTEXT_CONFIG but have not fiddled with 
it, so it could turn out that the above isn't really necessary.

Thanks BTC, excited to see where this leads.
Cheers,

Saq

-- 
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/2accf2da-57c1-4fcb-a47b-0862ffc97193o%40googlegroups.com.

[tw5] Re: Muuri Storyview

[BurningTreeC]

@All, Wow, a lot to comment to :)

@Saq

Thanks for the mashups that add Stories to the Muuri Demo, I was really 
curious if it works out well!

>Being able to drag between stories could be very handy. I've considered 
adding that for the Stories plugin but ultimately didn't have the 
motivation for it. With Muuri it would have greater appeal.

My goal is that dragging between stories becomes very easy using the muuri 
storyview. I hope I can achieve that soon

>Anyway, don't let me distract you with all the talk of multiple stories :)

It doesn't distract me, I had multiple stories in mind the way I created 
muuri


@TiddlyTweeter

>*Regarding mobile* ... where I toyed some. I think there is need to assert 
an approach and stick with it. 
In terms of mobile interface it might be better, eventually, to hide the 
"column number" button (I assume through CSS based on screen size 
detection?).
I'm not convinced of value of even 2 columns on mobile--though it may be my 
bias in having a rather small dimensional smartphone?

On mobile I honestly like the classic storyview more, even if it would need 
some css tweaking like smaller tiddler titles and less space between 
tiddlers (my opinion).
Still on mobile, using the muuri storyview with only 1 column makes 
dragging a bit complicated / difficult to handle. On bigger smartphones I 
think two columns work fine

>*Regarding the "Finger Toggle" & scrolling *... This applies to both 
desktop & mobile, particularly on mobile. It can be hard to scroll UP after 
moving stuff around with the "Finger Toggle" active to switch it OFF. On 
mobile particularly trying to scroll up you can just end up moving Tiddlers 
around rather than actually scrolling up. Maybe the toolbar for Muuri 
should be attached somewhere so its always visible?

On mobile that's a bit of an issue, you're right. There's the need to 
access the dragging-toggle button to be able to scroll up/down... As 
@Atronoush mentioned before, there are solutions like Nicolas Petton's 
Notebook theme that add a bottom panel with the page-controls buttons. 
Something like that I had in mind, I just didn't want to add another 
solution to the muuri storyview when there are already many solutions made 
by others, like @JD or @Nicolas Petton

>Further ... I'm glad to see, also, that "*In Tiddler Muuri*" are still 
supported. Its an extremely efficient way to, for instance, create 
galleries, as your example shows.

Yes, that was important to me. A muuri within a muuri within a muuri should 
also work (and so on :P )

>I think in actual practice I'd use Muuri to *arrange a site* for online 
publishing I do NOT want users to mess with.

Ok, yes I didn't think about that so much. There's the option to disable 
dragging and to hide the dragging button from the pagecontrols menu, then 
disabling the dragging-keyboard-shortcut by removing the tag 
$:/tags/KeyboardShortcut and doing the same for the columns button and the 
two columns shortcuts...

What I'm getting at is its a tool for content/organisation by developers as 
much as for end users. Yes?

Which tool do you mean? Muuri itself or the dragging on/off button?

Maybe? Maybe some hidden option to HIDE the tool could aid publishers 
publish their arrangement without worry the end user will mess with it?

I would go with the options described above...

>I just stumbled on what looks like a minor CSS issue ... replication on 
tablet ...

Thanks, you've found an issue I'm investigating :) ! Yet I couldn't find a 
problem in MY code so I'll leave an issue at the muuri github page, maybe 
its creator can tell me more about this problem (I hope so)



@The Rest about Stories

I believe multiple stories have their use-cases since we're manipulating 
different lists, where one could be the normal story list and another one 
could for example be a prioritized to-do-list where we can re-arrange tiles.
I can imagine, like @Saq wrote, that users can be very creative and use the 
muuri storyview in many different ways - given that it works well enough. 
And that's it from me atm, I'm going back to have a look at the code, maybe 
later today I'll have dragging between stories working... We'll see :)

all the best,
BTC


saq.i...@gmail.com schrieb am Sonntag, 18. Oktober 2020 um 12:00:49 UTC+2:

> Thanks for the clarification @BTC.
>
> I did a quick mashup adding Stories to your Muuri demo.
> Works pretty well, you can have Muuri in both stories or just one. 
>
> I think having a classic story view in the default story and muuri in the 
> second could be very powerful for making good use of a large screen for 
> some of my workflows.
>
> If you are curious, the files are here:
> Muuri in both stories:
> https://saqimtiaz.github.io/sq-tw/temp/muuri-stories.html
>
> Muuri in the second story only, with the first story only using 35% of 
> available space.
> https://saqimtiaz.github.io/sq-tw/temp/muuri-stories-alt.html
>
> Being able to drag between stories could be very handy. I've 

[tw5] button to create tiddler tagged with currentTiddler title, author field variable

[Sapphireslinger]

When I hit the "New Quote" button embedded in all my book tiddlers, I want 
to get a new tiddler tagged with (1) the title of the currentTiddler, (2) 
the variable contained in the author field and (3) the word "quote". 

I searched and tried all kinds of permutations for 2 hours but can't figure 
it out. The version below makes a tag for every word of the tiddler title 
and the author field, besides creating a weird field. :P 

<$list filter="[prefix[Book -]]">

<$button>
<$action-sendmessage $message="tm-new-tiddler" title=<> *tags= <>  <> 
quote />*
New Quote


   <$list filter="[tag!sort[title]]">
   <$link><$transclude field="title" mode="block"/>

   <$transclude field="text" mode="block"/>
   


-- 
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/99e18e46-7a94-49c5-9677-86320a2f016an%40googlegroups.com.

Re: [tw5] A HOWTO: Filtered transclusion example (with transclusion template and simple markdown table) for my Template Documentation

[Charlie Veniot]

G'day Felicia, 

Happy Monday !  (May seem like an oxymoron, but who knows?  Could be the 
best Monday ever ...)

I have a whole whack of metrics involved in my approach-taking decisions, 
usually a snap choice to avoid getting stuck in the mud and overthinking 
(me shoving sticks in my own wheels), and tweak as I go along when I reach 
some pain-in-the-caboose tipping point (or have some bright or plain old 
goofy idea I want to try).

More often than not, I tend to get very irritated with "bloat" and 
duplication/redundancy, and I find myself doing whatever to shave away even 
just a few characters .

A bit of a "take care of the pennies and the pounds will take care of 
themselves" ?

Then again, if "the fun in it" way surpasses any kind of irritation, then I 
stick with the fun until no longer fun.  Well, the fun quickly takes a 
nose-dive whenever I see an approach that is going to create an ugly mess 
down the road.

Being a software developer and always considering the design of everything, 
I'm always thinking:  make everything easy/quick to adapt / evolve / change 
(as per any new discovery or as per any mood strikes me).  That's the 
beauty of any wiki product: when things are done a certain way: a wiki 
makes it really easy to completely reshuffle everything.

Good luck me explaining "a certain way".  Insta-thoughts:

   - Every tiddler is a first-class citizen
   - No tiddler exists in (or is bound to, or dependent on) any 
   hierarchical (or other kind of) structure; any tiddler can, though, 
   participate in an infinite number of relationships, and each relationship 
   provides informative structure for some contextual meaning
   - Avoid, almost dogmatically, writing a "thing" more than once (write 
   once, transclude everywhere else)

All of that only half-way into my first morning cup of coffee.  No matter 
time of day or levels of caffeine, always wordy ...



On Monday, October 19, 2020 at 9:56:31 AM UTC-3, Felicia Crow wrote:
>
> Hi Charlie,
>
> wordy is great if it is this informative.
>
> Honestly I thought about your product tiddlers when asking about templates 
> because I wondered if it would be faster to have a template tiddler 
> containing a certain set of fields already and just creating new product 
> tiddlers from there with the fields only having to be filled out instead of 
> creating everything anew each time you add a new product, but I can see how 
> this would not have that much benefit in your case depending on how many 
> standard fields you have in your product tiddler.
>
> I think where I get far more benefits from template tiddlers and the main 
> reason I use them is that I have many fields in my wiki that my various 
> macros need, but that can be either already filled out in the template 
> itself or when creating a tiddler from the template.
> But then my wiki is intended to eventually become a template in itself to 
> be able to copy it and collect my various world building/writing ideas into 
> wikis depending on world instead of scattered throughout the dozens of 
> physical notebooks, files and formats they are currently in so I think 
> already the use case dictates a different approach in this case.
>
> As for the changing all the tiddlers when the template changes I wonder if 
> something could be done to update the tiddlers created from the template 
> when the template changes, but then it is the question what changes and how 
> things can be combined. So at most probably a add/delete field for every 
> tiddler created with this template and then either only if the change is 
> universal or showing a list of which tiddlers to update.
> And another idea for the pile...
>
> Hope you have a good day!
> Felicia
>
>
> On Thursday, 15 October 2020 16:50:10 UTC+2, Charlie Veniot wrote:
>>
>> G'day Felicia,
>>
>> In all of the various TiddlyWiki instances I've created, I've only done 
>> something akin to cloning with "Medication Journey" journals in my ADHD 
>> Slice'n Dice 
>>  
>> TiddlyWiki.
>>
>> I am a tweaker by nature, always incrementally 
>> iterating/adjusting/tweaking/refining/etc. etc. as a slowly get things just 
>> right (matching whatever intertwingled mess of a puzzle picture in my head.)
>>
>> The problem I have with creating a  bunch of tiddlers as clones of a 
>> tiddler template:  when I want to make an adjustment (and I will 
>> undoubtedly make umpteen adjustments to anything as everything becomes less 
>> muddied), I have to then go to every tiddler created from whatever template 
>> and adjust each one accordingly.  That's a huge pain in the caboose.
>>
>> Eventually, I may create some buttons for tiddler creation as copies of 
>> template tiddlers in my Product Reviews 
>>  
>> TiddlyWiki, but there has to be some significant benefit.  At the moment, 
>> I'm not seeing any.
>>
>> My a

Re: [tw5] A HOWTO: Filtered transclusion example (with transclusion template and simple markdown table) for my Template Documentation

[Felicia Crow]

Hi Charlie,

wordy is great if it is this informative.

Honestly I thought about your product tiddlers when asking about templates 
because I wondered if it would be faster to have a template tiddler 
containing a certain set of fields already and just creating new product 
tiddlers from there with the fields only having to be filled out instead of 
creating everything anew each time you add a new product, but I can see how 
this would not have that much benefit in your case depending on how many 
standard fields you have in your product tiddler.

I think where I get far more benefits from template tiddlers and the main 
reason I use them is that I have many fields in my wiki that my various 
macros need, but that can be either already filled out in the template 
itself or when creating a tiddler from the template.
But then my wiki is intended to eventually become a template in itself to 
be able to copy it and collect my various world building/writing ideas into 
wikis depending on world instead of scattered throughout the dozens of 
physical notebooks, files and formats they are currently in so I think 
already the use case dictates a different approach in this case.

As for the changing all the tiddlers when the template changes I wonder if 
something could be done to update the tiddlers created from the template 
when the template changes, but then it is the question what changes and how 
things can be combined. So at most probably a add/delete field for every 
tiddler created with this template and then either only if the change is 
universal or showing a list of which tiddlers to update.
And another idea for the pile...

Hope you have a good day!
Felicia


On Thursday, 15 October 2020 16:50:10 UTC+2, Charlie Veniot wrote:
>
> G'day Felicia,
>
> In all of the various TiddlyWiki instances I've created, I've only done 
> something akin to cloning with "Medication Journey" journals in my ADHD 
> Slice'n Dice 
>  
> TiddlyWiki.
>
> I am a tweaker by nature, always incrementally 
> iterating/adjusting/tweaking/refining/etc. etc. as a slowly get things just 
> right (matching whatever intertwingled mess of a puzzle picture in my head.)
>
> The problem I have with creating a  bunch of tiddlers as clones of a 
> tiddler template:  when I want to make an adjustment (and I will 
> undoubtedly make umpteen adjustments to anything as everything becomes less 
> muddied), I have to then go to every tiddler created from whatever template 
> and adjust each one accordingly.  That's a huge pain in the caboose.
>
> Eventually, I may create some buttons for tiddler creation as copies of 
> template tiddlers in my Product Reviews 
>  
> TiddlyWiki, but there has to be some significant benefit.  At the moment, 
> I'm not seeing any.
>
> My approach to writing and organizing content is to get something down as 
> quick as possible that is good enough (a process of progressive 
> elicitation?), and then slowly/incrementally/iteratively adjust as 
> needs/requirements ( information-bits / structures, the pictures) dictate 
> (become clear.)  The plan/direction unfolds as I see the bits written down 
> and structured.  Never "big requirements/plans up front".  That's the 
> beauty of any Wiki: it allows agility and even massive change to anything 
> can be done quickly.  (Unlike dealing with a bunch of separate 
> files/documents in some hierarchy of folders.)
>
> Very organic to fit my granola personality.
>
> Oops.  I got wordy.  Hard thing to fix ...
>
> Cheers !
>
> On Thursday, October 15, 2020 at 11:19:59 AM UTC-3, Felicia Crow wrote:
>>
>> Hi Charlie,
>>
>> somewhat off-topic, but your answer to Atro led me to a question 
>> regarding another kind of template. Seeing how streamlined your wiki is, 
>> but having not seen anything in this direction: Have you thought about 
>> using templates to create certain tiddlers, either by cloning the template 
>> or using a button?
>>
>> Kind Regards,
>> Felicia
>>
>>
>>
>> On Thursday, 15 October 2020 15:33:54 UTC+2, Charlie Veniot wrote:
>>>
>>> Hello Atro,
>>>
>>> Those are excellent questions.  Without having pondered deeply about it, 
>>> here is my immediate blathering of thoughts:
>>>
>>> I generally much prefer transclusion wherever I can use that instead of 
>>> a macro.  For the way this old sponge of mine works, transclusion often 
>>> makes more sense to me than a macro (maybe because I always think in a 
>>> transclusion way (with *everything*, TiddlyWiki or not.)  I also get 
>>> annoyed with macro syntax for whatever reason (in the same way somebody 
>>> would prefer the colour green while somebody else the colour blue.)
>>>
>>> There are certain things that, to me, macro is hands down the way to 
>>> go.  What these things are, I'm not sure.  Maybe it is enough to say that 
>>> what can't be nicely done via transclusi

[tw5] Re: How to inherit tags when creating a new tiddler?

[PMario]

Hi, 

You can use: https://tiddlywiki.com/index.html#ActionCreateTiddlerWidget 
and have a closer look at example 4 and 5

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/a07d4d7e-de9f-4b90-8ee8-c384083c0dffo%40googlegroups.com.

[tw5] Re: How to inherit tags when creating a new tiddler?

[PMario]

Hi Pedro,

 - You can use the "Clone" button, 
 - Give it a new name 
 - Go to the text field 
   - CTRL-A
   - backspace
Done! 

All your tags are there and the text field is overwritten. 

Just an idea, that doesn't need any tweaking and works out of the box for 
every TW. 

-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/b4a56270-70fb-46f9-9478-68f3fcf6d9d2o%40googlegroups.com.

[tw5] Re: How to view tiddlers with unknown type as pre-formatted code

[bimlas]

Note for other users: if syntax highlighting doesn't work, set the 
appropriate types in the Highlight.js plugin! From the documentation:

You can also specify the language as a MIME content type (eg text/html or 
text/css). The mapping is accomplished via mapping tiddlers whose titles 
start with $:/config/HighlightPlugin/TypeMappings/.

-- 
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/6c34729b-dcb7-4260-8cca-254f0f83d687n%40googlegroups.com.

[tw5] Re: Transclude tiddler title or text field as a "combination".

[Felicia Crow]

Sorry a little late, but my brain was out of commission for the weekend so 
I only finished my solution now, but good to see that Charlie could help 
you already.

Still if you are interested: I used two macros working with the given 
titles/tags to make it more modular so it can be extended in the future. 
The only thing I have yet to work out is different combinations for the 
same colour.

The first and simpler macro is used to get the colours needed to mix the 
colour:

\define get-combination()
<$list filter="[!has[draft.of]tagsort[title]first[]]">
<$link to=<> />

<$list filter="[!has[draft.of]tagsort[title]butfirst[]]">
+ <$link to=<> />

\end

The only difference between the filters is that the first only uses the 
first result and the second uses the rest to get the formatting of 'colour 
+ colour' with as many '+ colour' as needed for the current combination.
So the filter in  detail:

   1. *!has[draft.of]* just makes sure that only tiddlers not currently 
   edited are used.
   2. *tag* looks for tiddlers that are tagged with the 
   title of the tiddler the macro is called in. For instance if you call the 
   macro in a tiddler called 'Orange' it will look if there are tiddlers 
   tagged 'Orange'.
   3. *sort[title]* sorts the resulting list by the tiddlers titles.
   4. *first[]* then discards everything except for the first title in the 
   list and *butfirst[]* does the opposite and takes the rest.

The second macro that is used to get all combinations with a specific 
colour:

\define get-color-combinations()
<$list filter="[tags[]]" variable="tag">
<$list filter="[tag[Mixed Color]]" variable="mixed-color">
<>
<$list filter="[!has[draft.of]tag!]" variable=
"other-color">
 + <$link to=<> />

= <$link to=<> />



\end

And the details:

   1. The first list just gets all the tiddlers of the currentTiddler and 
   puts it in a variable called *tag* as to not overwrite currentTiddler.
   2. The second list filters for mixed colors related to the 
   currentTiddler.
  1. ** is just a shortform of title and looks for a tiddler 
  that is named the same as the value of the tag variable.
  2. *tag[Mixed Color]* then looks if the tiddler it found has the tag 
  'Mixed Color'.
  3. the result gets put into a variable called *mixed-color* once 
  again so currentTiddler isn't overwritten.
   3. Then the title of the current tiddler is 'printed' as the first part 
   of the final text. This is not a link as this is the currently used tiddler.
   4. The third list then looks for the other colour/colours that are 
   tagged with the current mixed-color.
  1. *!has[draft.of]* once again making sure only tiddlers not being 
  edited get used.
  2. *tag* looks for tiddlers tagged with the value of 
  mixed-color.
  3. *!* but only take those that aren't the 
  current-tiddler.
  4. and another variable this time called *other-color*.
   5. Now print each found colour with '+ other-color' to create the second 
   part of the result. These are all links to their respective tiddlers.
   6. And finally when the previous list is finished with adding colours 
   add '= mixed-color' plus a line-break as the third and last part of the 
   result. Once again this is a link to the tiddler.
   
The first macro can be used both in tiddler with a mixed colour and in a 
general combination overview like so:
<$list filter="[!has[draft.of]tag[Mixed Color]sort[title]]" >
<$link to=<> />: 
<>



The second macro can be used in any colour tiddler that is part of a mixed 
colour both basic colour and mixed colour.

And because this reply is not long enough already here a few screenshots:

Tiddler 'Red' with <> in use also showing a 
combination from three colours:


Tiddler 'Green' showing the colours needed to mix it via 
<>:

The overview tiddler of possible combinations:

And a version of the Violet Tiddler that uses both macors:

I attached a json file for easy import should you want to use it/play 
around with it.
Also I second Charlie in that I would love to see whatever the end result 
might be.

Kind Regards,
Felicia


On Tuesday, 13 October 2020 17:45:04 UTC+2, vinvi...@gmail.com wrote:
>
> Hello,
>
> Tiddlers a + b are tagged with tiddler 1.
> Tiddlers a + c + d are tagged with tiddler 2.
> Tiddlers a + b + c + d are tagged with (Ip).
>
> In tiddler (Ip), I want to show ALL letter combinations: (transclude 
> tiddler titles as a link)
> POSSIBLE COMBINATIONS:
> a + b → tiddler 1
> a + c + d → tiddler 2
>
> In tiddler a, I want to show all letter combinations with tiddler a: 
> (transclude tiddler titles as a link)
> POSSIBLE COMBINATIONS:
> a + b → tiddler 1
> a + c + d → tiddler 2
>
> In tiddler b, I want to show all letter combinations with tiddler b: 
> (transclude tiddler titles as a link)
> POSSIBLE COMBINATIONS:
> b + a → tiddler 2
>
> In tiddler 1, I want to show the letter combination: (transclude textfield 
> of tiddlers)
> a + b
>
> In tiddler 2, I want 

[tw5] Re: How to view tiddlers with unknown type as pre-formatted code

[bimlas]

Thank you for your answers!

Although I don't like to overwrite Javascript tiddlers, Saq's solution is 
perfect for me.

Because syntax highlighting also works thanks to the Highlight.js plugin, 
it is good to display text files as code.

-- 
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/f5993b00-5ab2-4ea6-a51d-dcc1fce52bedn%40googlegroups.com.

[tw5] Drag and dropping accross lists: add or replace tags depending on state?

[Petri M.]

Hi. I just noticed that if I have a table with rows/columns and if those 
cells have the <> macro in them, then I can drag the 
items of the list *from cell to cell* instead of just within a cell. But 
then I noticed that when I do this I just *add a *tag to the dragged 
tiddler corresponding to the tag of the other cell. The old tag is never 
actually removed. 

I fould this thread 
about 
this issue and the fix works fine. However, how should I proceed if I'd 
like to have *both* functionalities? For instance, depending on a state 
tiddler or something. I tried to find something like an *if else *clause 
but did not really find anything applicable.

-Petri

-- 
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/ff19f03c-944c-46ff-8330-720fa86529e0n%40googlegroups.com.

Re: [tw5] Re: How to inherit tags when creating a new tiddler?

[Pedro]

Hi Tones,

Thanks for the hint. I didn't know the clone button and it surely may help
sometimes but it seems that custom buttons will better fit my needs.
I was successful in customizing the new-here button. I cloned it, named the
new version as custom-new-here, and inserted tags={{!!tags}} in its
actions. It works perfectly. When I create a new tiddler using the
custom-new-here button it is created with its "parent tiddler" tags.

To replicate this behavior on new-journal-here I had to define a new value
named inheritedTags

*<$set name="inheritedTags" value={{!!tags}}>*

and modify the definition of journalButtonTags() to get it



*\define journalButtonTags()$(journalTags)$ $(inheritedTags)$\end*

I removed the reference to [[$(currentTiddlerTag)$]] since I'm not
interested in the name as a tag.

Thank you Tones =)
--
Pedro Alves


*PhD candidate in Computer Science*

*Institute of Computing - University of Campinas*


Em seg., 19 de out. de 2020 às 00:14, TW Tones 
escreveu:

> Pedro,
>
> Have you tried the clone button?, Clone and edit is a quick way to achieve
> this. But it is also easy to build custom buttons.
>
> If you want a custom button you can clone or edit the New Here Button $:/
> core/ui/Buttons/new-here
> Then modify it to get the behaviour you want.
>
> Eg in the actions tags={{!!tags}}
>
> Regards
> Tones
>
> On Monday, 19 October 2020 07:09:05 UTC+11, Pedro wrote:
>>
>> Hi,
>>
>> I'm trying to implement a different behavior on my tiddly wiki instance.
>> It's a research diary and I have many macros that index different subjects
>> by tags. So, when I create a new tiddler linked to an existing one (so,
>> using the button "create a new tiddler that links to this one"), I would
>> like that it have the same set of tags than the original one.
>>
>> I have no idea how to implement it! Can anyone give me some directions?
>>
>>
>> --
>> Pedro Alves
>>
>>
>> *PhD candidate in Computer Science*
>>
>> *Institute of Computing - University of Campinas*
>>
> --
> 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/0263ab93-7296-48c1-a80b-70f58abd2848o%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CACW_pa2iNWR0W6hwuu4ZMr1%2BsFkju7Li5b2f0jzs3mr2-fzN%3DA%40mail.gmail.com.

[tw5] Re: How to view tiddlers with unknown type as pre-formatted code

[Saq Imtiaz]

Hi Bimlas,

>From what I recall this behaviour is determined by the appropriate parser 
for the tiddler type. See wiki.parseText which defaults to vnd.tiddlywiki 
for unknown types.

For CSS/JavaScript the text parser is used which wraps everything in a 
codeblock.
See: core/modules/parsers/textparser.js

Unknown tiddler types I believe are handled as text/vnd.tiddlywiki, so you 
would need to change that default for unknown types. Alternatively you 
could pre-define all the types you might need to use the text parser.

Hope this helps.
Saq

On Monday, October 19, 2020 at 10:27:45 AM UTC+2, bimlas wrote:
>
> When you open a Javascript or CSS tiddler, it displays it as pre-formatted 
> code. If my research is accurate, this behavior is determined by the 
> transclude widget, but I couldn’t investigate the condition.
>
> How can it be solved that e.g. display Markdown tiddlers (type: 
> text/x-markdown) as code (so I don't have to install the Markdown plugin 
> and still make my notes easy to read)?
>

-- 
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/4ea8c23f-7f08-4f6d-975b-106dd45527c9o%40googlegroups.com.

[tw5] Re: How to view tiddlers with unknown type as pre-formatted code

[Eric Shulman]

On Monday, October 19, 2020 at 1:35:09 AM UTC-7, bimlas wrote:
>
> To make the question more accurate: my goal is to keep tiddlers of 
> different formats distinguishable by type type (Markdown, Asciidoc, 
> reStructuredText, LaTeX, etc.), but if that type is unknown to TiddlyWiki, 
> then I can view them as I do in a text editor.
>

Create a tiddler "ShowUnkownTiddlerTypeAsText", tagged with 
$:/tags/ViewTemplate, containing:
\define hidebody()  [data-tiddler-title="$(currentTiddler)$"] .tc-
tiddler-body { display:none; } 

<$list 
filter="[get[type]addprefix[$:/language/Docs/Types/]!is[shadow]!is[tiddler]]"
 
variable="unknown_type">
   <><$text text={{!!text}}/>


Notes:
1) The hidebody() macro uses CSS to suppress the display of the tiddler 
body for the current tiddler
2) $list checks to see if the type field of the current tiddler is unknown 
to the system (i.e., doesn't have a $:/language/Docs/Types/... definition 
as either a shadow or regular system tiddler)

-e

-- 
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/08449769-a02b-4caf-b368-4e22c10d18a0o%40googlegroups.com.

[tw5] Re: How to view tiddlers with unknown type as pre-formatted code

[bimlas]

To make the question more accurate: my goal is to keep tiddlers of 
different formats distinguishable by type type (Markdown, Asciidoc, 
reStructuredText, LaTeX, etc.), but if that type is unknown to TiddlyWiki, 
then I can view them as I do in a text editor.

-- 
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/f9c4818c-e0a7-4529-a27f-87fd69480aecn%40googlegroups.com.

[tw5] How to view tiddlers with unknown type as pre-formatted code

[bimlas]

When you open a Javascript or CSS tiddler, it displays it as pre-formatted 
code. If my research is accurate, this behavior is determined by the 
transclude widget, but I couldn’t investigate the condition.

How can it be solved that e.g. display Markdown tiddlers (type: 
text/x-markdown) as code (so I don't have to install the Markdown plugin 
and still make my notes easy to read)?

-- 
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/1363a9f8-e2ef-4690-b7f0-8fbe719dbfa6n%40googlegroups.com.