[tw5] Re: Is there a way to make the sorttable.js script work in a static HTML Tiddlywiki exported file?

[Suzanne McHale]

Found a solution! See this Reddit post: 
https://old.reddit.com/r/TiddlyWiki5/comments/o5278c/is_there_a_way_to_make_the_sorttablejs_script/

-- 
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/d7a6dc65-3d1f-423b-8407-e9145a7debf3n%40googlegroups.com.

[tw5] Is List Grouping Using Tags or Tiddler Fields Possible?

[Darth Mole]

I currently am using the toc macro on pages to automatically display 
tiddlers that are considered sub-tiddlers in specific categories. I’m using 
tags to do this. 

IE: The Settlements tiddler has a toc macro to display all tiddlers listed 
as a settlement type via the tags. 

The only problem is that the sub-tiddlers won’t appear until I’ve made an 
individual tiddler, tagged with the Settlements tag, for them to be grouped 
under in the toc. The toc is based on tags AND tiddlers/tiddler titles, not 
just the tags. 

I know there is the list macro but I don’t see how you can limit the list 
of tiddlers by one tag (ie: Settlements) and then group them by a second 
tag (ie: Outpost). Especially if the tiddlers have more than 2 tags. 

I also came across the list grouping by tiddler type, and thought perhaps 
there is a way to do the grouping with a custom tiddler field at the bottom 
of the tiddler but I haven’t been able to make it work. 

Is it even possible to do what I want? I don’t want to have to make a 
placeholder tiddler for every settlement, organization, geography, etc., 
type regarding the toc macro when there isn’t a guarantee even a fraction 
of them would be used. 

Is there perhaps a way to make a hierarchy in the tags using a naming 
convention that will do what I want? IE: Settlement/Outpost

Thanks!

-- 
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/e10a27ec-a2f5-438e-bae6-741685a2f17cn%40googlegroups.com.

Re: [tw5] TiddlyWiki Documentation - Syntax

[Simon Baird]

I'm not following all the tech discussion here, but I like the idea of
accessible, standard documentation that's trivially easy to author.

One good example that comes to mind is the documentation for ansible
modules. There are lots of them, and they all have consistent, (mostly)
understandable docs. Perhaps there are some ideas there you could borrow or
steal.

A particularly useful section is the examples. For widgets a set of good
examples would be handy, and perhaps easier to use casually than the formal
syntax definition.

Example:
https://docs.ansible.com/ansible/2.9/modules/copy_module.html#copy-module
(Find many others here:)
https://docs.ansible.com/ansible/2.9/modules/modules_by_category.html


On Mon, Jun 7, 2021 at 7:22 PM TW Tones  wrote:

> Sorry,
>
> I meant to add I think version three could be at the bottom of every
> definition with all parameters, copy or drag.
>
> Tones
>
> On Tuesday, 8 June 2021 at 09:21:02 UTC+10 TW Tones wrote:
>
>> *Stobot et al*
>> *I'm not that familiar with screen readers etc. but if you want to take a
>> crack at an example to help me understand, I'd be happy to look at it*
>> Nor am I but alt apparently making use of alt text is important for
>> images at least. No what I am saying is making use of the other features
>> like mouse over, tooltips etc... Of late I have being getting into
>> draggable payloads, especially of content as I describe in *On syntax
>> formats* below. Just drag a syntax form into your tiddler and edit.
>>
>> *On Syntax formats*
>> To me version one is almost useless, it resembles the list of parameters
>> already documented. But you still need to refer to the rest of the
>> document. Using version one as a code snipit still requires a lot of work.
>> I would favor version 2 but one for each of the different configurations,
>> ie a subset of parameters for each common form of the widget.
>>
>> *The details widget.*
>>
>> I use the html one a lot more know since something changed to make it
>> more reliable. It does store the initial state (open or closed) just not
>> the ongoing state, and in a larger number of circumstances this is all you
>> need. Also keep in mind that even the existence of the details widget can
>> be inside a list/reveal itself which is conditional. It is ideal for more
>> or less content. Using the summary tag you can actually place macros in the
>> details "heading" to show the number of something there inside the details
>> tag (I do not think $details does this).
>>
>> Not with standing this, there is the details widget in a plugin
>> https://tid.li/tw5/plugins.html#DetailsWidget and 14kb in size, but I
>> have not used it much lately.
>>
>> I wish we could get the equivalent of the old TWC nested sliders plugin
>> but perhaps this can be emulated in Mario's "Custom Markup" as he has also
>> demonstrated the the details widget can.
>>
>> *That reminds me;*
>> We could document a lot more features and methods in tiddlywiki or a
>> separate wiki that are not just about widgets, macros tweaks and filters,
>> but also making use of html and css. For example using css to toggle
>> content display: none; and possibly classes such as nest nest1 nest2 would
>> stand in for the nested sliders plugin.
>>
>>
>>
>> Although the reality is the Custom Markup plugin may be the most valuable
>> plugin since "relink" and possibly of even more consequence.
>>
>> Regards
>> Tones
>>
>>
>> On Monday, 7 June 2021 at 22:44:42 UTC+10 TiddlyTweeter wrote:
>>
>>>
>>>- To TiddlyTweeter's point, if <$details> stored state, wouldn't it
>>>just be a less-flexible <$reveal>?
>>>
>>> RIGHT. Point is it is just a dumb state that requires NO state tiddlers
>>> at all. You can simply, directly, change the toggle state.
>>>
>>> It is mostly ONLY useful for ON/OFF situations.
>>> For that it is elegantly simple in code!
>>>
>>> TT
>>>
>>>
>>> On Monday, 7 June 2021 at 13:15:15 UTC+2 Stobot wrote:
>>>
 Great continued feedback. I'll keep going, but just to mass-reply:

 PMario

- I agree that the "closed version" should be in a small general
syntax notes area - maybe right below the syntax block. Things like:
   - Each attribute can be given as "Text Value", {{Trancluded
   Value}}, or <>
- Still thinking through how to handle the "or" situations (need
tiddler value or tiddler and field, or just field, or tiddler and 
 index...)
   - Soren had the one example which might be great. I currently
   don't understand it clearly though, so will think on how to simplify 
 it

 Tones

- I'm not that familiar with screen readers etc. but if you want to
take a crack at an example to help me understand, I'd be happy to look 
 at it

 Ste

- I'll check out the stretch text thing. Others have suggested
details which seems to have similar aims (though is non-core)

 Mohammad / Odin / TiddlyTweeter

Re: [tw5] Re: Filter question: how to convert current tiddler title into a title list format

[Joshua Fontany]

Hi mehequeda,

You will want to read up on the 
"ListOps": https://tiddlywiki.com/#ActionListopsWidget

Best,
Joshua Fontany

On Tuesday, June 22, 2021 at 10:49:45 PM UTC-7 mehequeda...@gmail.com wrote:

> Thanks Saq, Tones and Jeremy, it was hidden in plain sight.
>
> The reason I need this is a design decision of some zettlekasten-like 
> features I'm implementing in my wiki. For example, tiddlers tagged with 
> Source are the books, articles, or other sources of concepts I want to 
> track and I've modified the view template to show some fields and 
> references to related things in a footer:
> [image: image.png]
> Now, I'm introducing buttons to create related tiddlers that have the kind 
> of relationship of the corresponding tab. Sometimes that means copying 
> current title in the author field. But in some case I need to set current 
> title in title list format because of the meaning of the field. For 
> example, a concept might have two authors.
>
> BTW, this is pretty much inspired by the amazing Soren's zettlekasten. 
> Thanks Soren!
>
> --
> Sebastián
>
>
> On Wed, Jun 23, 2021 at 2:20 AM TW Tones  wrote:
>
>> mehequeda,
>>
>> I am curious why you need to do this. Since titles are the key to all 
>> tiddler there handling as titles is innate to TiddlyWiki and the need to 
>> generate a title with the delimiters [[ and ]] is rare. An example would be 
>> using the listops functions and operators where this is handled 
>> automatically. Tiddlywiki finds or adds delimiters automatically in many 
>> cases for title handling, consider  else{!!title} used in a filter, the 
>> output will not split a tiddler title containing spaces into separate words.
>>
>> Regrads
>> Tones
>>
>> On Wednesday, 23 June 2021 at 07:10:04 UTC+10 mehequeda...@gmail.com 
>> wrote:
>>
>>> Hello wise tiddlywiki users,
>>>
>>> Let's say I want to convert the current tiddler title into list format. 
>>> For example:
>>>
>>>- For a tiddler named CamelCased, this is either CamelCased or 
>>>[[CamelCased]] (I prefer the format but I can settle with the latter)
>>>- For a tiddler named Name with spaces it must be [[Name with 
>>>spaces]]
>>>
>>> I'm stuck with trying to add squared brackets conditionally 
>>> [all[current]regexp[\s]addprefix[[[]addsuffix[]]]else{!!title}] because 
>>> that's not the right syntax for adding the brackets and also because this 
>>> feels common enough that it should be some easier way to "escape" a string 
>>> to a title list format.
>>>
>>> Do you know how to get it?
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/S5LM0L5ZVRo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/e971bff9-cdf0-407a-bc6b-e8b47580c36an%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/36b67124-16aa-49ba-9da1-80e99e863a2an%40googlegroups.com.

[tw5] Re: Using field value as macro input?

[clutterstack]

Sorry I didn't see this, Patrick. I hope you found a solution -- but that 
looks like a symptom of the fact that the currentTiddler variable 
 doesn't get set 
automatically in the sidebar. So you're looking for a searchterm (or 
search?) field on a tiddler that doesn't exist.

One approach is to set a named state tiddler for your edit-text widget to 
use (so you're not relying on a currentTiddler), then include that name in 
the filter ( [tag{statetid!!search}]). Another would be to set the 
currentTiddler variable using transclusion -- rather than putting your 
search tiddler straight into the sidebar, put a tiddler that transcludes it 
in the sidebar. More about how transclusion affects currentTiddler at 
tiddlywiki.com .

Best,
Chris
On Monday, June 21, 2021 at 8:00:48 PM UTC-4 prbru...@gmail.com wrote:

> That's brilliant, thanks so much. It works, but (weirdly?) not if I have 
> the date sorting, and not if the tiddler is put into the sidebar (the 
> search field field doesn't get filled!) 
>
> <$edit-text field="search" default="" placeholder="enter text to search" 
> tag="input"/> 
> 
> search is {{!!search}}
> 
> *<>*
>
>
> However, this is nearly there and I'm very grateful  ;-)
> On Monday, 21 June 2021 at 16:34:25 UTC+1 clutterstack wrote:
>
>> Or I should specify "you can *transclude* a text reference using curly 
>> brackets" since this can be a bit messy to keep straight. 
>>
>> Docs: https://tiddlywiki.com/#TextReference
>>
>> On Monday, June 21, 2021 at 11:28:33 AM UTC-4 clutterstack wrote:
>>
>>> Hi Patrick,
>>>
>>> Sorry if I'm misinterpreting. You can use a text reference in a filter 
>>> with curly brackets.
>>>
>>> It looks as though you're using Mohammad's timeline macros. I went to 
>>> https://kookma.github.io/TW-Timelines/ and made a new tiddler to test 
>>> your example. Adding the following gave me a timeline:
>>>
>>> <>
>>>
>>> Hope that helps,
>>> Chris
>>> On Monday, June 21, 2021 at 7:47:05 AM UTC-4 prbru...@gmail.com wrote:
>>>
 Matybe I wasn't clear enough

 I can get input into a field ("search") and assign it to a variable eg.

 \define thisList()
 <$list filter="[tag[$(TestVariable)$]]">
 \end
 <$set name=TestVariable value={{!!search}}>
 TestVariable is <>
 This list is <>
 
 

 <$edit-text field="search" default="" placeholder="enter text to 
 search" 
 tag="input"/> 
 

 this will list all tiddlers tagged with the value of the field "search"

 but I can't work out how to use that search term in another existing 
 macro as a filter such as

 <> 

 or 

 <>>> search:"$(search)$" date:"date">>
  
 any ideas please?
 On Friday, 18 June 2021 at 00:11:12 UTC+1 Patrick RB wrote:

> It look's like this is a common issue for newbies, but I'm using 
> timelines plugin to display tiddler filtered by tags (in this case 
> "snippet")
>
> <
> To aid quick searches and avoid editing the tiddler I have created a 
> text box input to set a field to inject input into tag[.] and a 
> custom 
> date field
>
> I can create, set and check the search field has the expected text, 
> but cannot get the timelines macro to accept the search field text, 
> though 
> the date field works fine.
>
> can any of you real developers help? Thanks! 
>
>
>

-- 
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/58a7a58a-d758-4e9c-b18c-c3b1a20f2d32n%40googlegroups.com.

[tw5] Re: change color of field / tag when selected

[S²]

Thanks a lot Soren - that's what I want.

I recognized line 5...

Perfect!

Soren Bjornstad schrieb am Mittwoch, 23. Juni 2021 um 18:33:55 UTC+2:

> Note: On line 5, I switched the field from *published *to *modified* so I 
> could test on TiddlyWiki.com and forgot to change it back. You probably 
> want it to be *published*.
>
> On Wednesday, June 23, 2021 at 11:29:59 AM UTC-5 Soren Bjornstad wrote:
>
>> If you switch to using a CSS class rather than the inline style to handle 
>> your coloring, you can use an a:hover selector to apply different styling 
>> when the cursor is over the link, like this:
>>
>> 
>> <$link to={{!!title}} tooltip="Titel: {{!!title}}">
>> <$view field="caption"><$view field="title"/>
>>  --- 
>> <$view field="modified" />
>>  aus Gruppe: 
>> <$view field="tags"/>
>> 
>> 
>>
>> 
>> .myclass {
>>   color: rgba(255, 201, 102, 0.8)
>> }
>> a:hover .myclass {
>>   color: red;
>> }
>> 
>>
>> You can also use *.myclass:hover *as the selector instead of 
>> *a:hover.myclass*, but then you have to hover directly over the text for 
>> the color to change, rather than anywhere on the link.
>>
>> I am not sure if this would work with a drop-down and keyboard selection.
>>
>> On Wednesday, June 23, 2021 at 10:39:19 AM UTC-5 S² wrote:
>>
>>>
>>> Hello,
>>>
>>> is it possible to change the color of "published" and "tags" when 
>>> selecting an entry in the search list:
>>> (for "title" it is working fine...)
>>> [image: search.png]
>>>
>>> my Code:
>>>
>>> 
>>> <$link to={{!!title}} tooltip="Titel: {{!!title}}">
>>> <$view field="caption"><$view field="title"/>
>>>  --- 
>>> <$view field="published" 
>>> />
>>>  aus Gruppe:  
>>> <$view 
>>> field="tags"/> 
>>> 
>>> 
>>>
>>> Thanks for feedback
>>> Stefan
>>>
>>

-- 
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/f486c4fd-6f46-4925-9eae-39ef541f4102n%40googlegroups.com.

[tw5] Re: change color of field / tag when selected

[Soren Bjornstad]

Note: On line 5, I switched the field from *published *to *modified* so I 
could test on TiddlyWiki.com and forgot to change it back. You probably 
want it to be *published*.

On Wednesday, June 23, 2021 at 11:29:59 AM UTC-5 Soren Bjornstad wrote:

> If you switch to using a CSS class rather than the inline style to handle 
> your coloring, you can use an a:hover selector to apply different styling 
> when the cursor is over the link, like this:
>
> 
> <$link to={{!!title}} tooltip="Titel: {{!!title}}">
> <$view field="caption"><$view field="title"/>
>  --- 
> <$view field="modified" />
>  aus Gruppe: 
> <$view field="tags"/>
> 
> 
>
> 
> .myclass {
>   color: rgba(255, 201, 102, 0.8)
> }
> a:hover .myclass {
>   color: red;
> }
> 
>
> You can also use *.myclass:hover *as the selector instead of 
> *a:hover.myclass*, but then you have to hover directly over the text for 
> the color to change, rather than anywhere on the link.
>
> I am not sure if this would work with a drop-down and keyboard selection.
>
> On Wednesday, June 23, 2021 at 10:39:19 AM UTC-5 S² wrote:
>
>>
>> Hello,
>>
>> is it possible to change the color of "published" and "tags" when 
>> selecting an entry in the search list:
>> (for "title" it is working fine...)
>> [image: search.png]
>>
>> my Code:
>>
>> 
>> <$link to={{!!title}} tooltip="Titel: {{!!title}}">
>> <$view field="caption"><$view field="title"/>
>>  --- 
>> <$view field="published" 
>> />
>>  aus Gruppe:  
>> <$view 
>> field="tags"/> 
>> 
>> 
>>
>> Thanks for feedback
>> Stefan
>>
>

-- 
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/ca102a22-10e5-4389-9ddf-f44622609503n%40googlegroups.com.

[tw5] Re: change color of field / tag when selected

[Soren Bjornstad]

If you switch to using a CSS class rather than the inline style to handle 
your coloring, you can use an a:hover selector to apply different styling 
when the cursor is over the link, like this:


<$link to={{!!title}} tooltip="Titel: {{!!title}}">
<$view field="caption"><$view field="title"/>
 --- 
<$view field="modified" />
 aus Gruppe: 
<$view field="tags"/>




.myclass {
  color: rgba(255, 201, 102, 0.8)
}
a:hover .myclass {
  color: red;
}


You can also use *.myclass:hover *as the selector instead of 
*a:hover.myclass*, but then you have to hover directly over the text for 
the color to change, rather than anywhere on the link.

I am not sure if this would work with a drop-down and keyboard selection.

On Wednesday, June 23, 2021 at 10:39:19 AM UTC-5 S² wrote:

>
> Hello,
>
> is it possible to change the color of "published" and "tags" when 
> selecting an entry in the search list:
> (for "title" it is working fine...)
> [image: search.png]
>
> my Code:
>
> 
> <$link to={{!!title}} tooltip="Titel: {{!!title}}">
> <$view field="caption"><$view field="title"/>
>  --- 
> <$view field="published" 
> />
>  aus Gruppe:  
> <$view 
> field="tags"/> 
> 
> 
>
> Thanks for feedback
> Stefan
>

-- 
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/bf069b5c-8002-4e11-b157-fd36d3abde23n%40googlegroups.com.

[tw5] change color of field / tag when selected

[S²]

Hello,

is it possible to change the color of "published" and "tags" when selecting 
an entry in the search list:
(for "title" it is working fine...)
[image: search.png]

my Code:


<$link to={{!!title}} tooltip="Titel: {{!!title}}">
<$view field="caption"><$view field="title"/>
 --- 
<$view field="published" 
/>
 aus Gruppe:  
<$view field="tags"/> 



Thanks for feedback
Stefan

-- 
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/dfbce74e-7487-4126-acbb-040eb9885c7fn%40googlegroups.com.

Re: [tw5] Re: TiddlyWiki SO cool ...

[CJ Veniot]

Although I'm no fan of social media (Twitter, Instagram, Tik Tok, etc.
etc.), my answer would be YouTube, Blogs and all social media options.

Via titles that equal use cases, and not titles about the product (well,
with loads of metadata some somebody looking for TiddlyWiki, or TW, can
find these social media jewels.)

So draw folk to the videos and such via problems that need to be solved, or
approaches to doing certain things.

For example, thinking of the discussion about notetaking and notemaking.

Instead of a social media something like "Notetaking with TiddlyWiki", draw
folk in with something like "Agile Notetaking" (well, some title that draws
folk, in the spirit of whatever draws people to viral videos.)

So flood the media with marketing not of the product itself, but of the
full breadth and depth of solutions that coincidentally are handled with
TiddlyWiki align with whatever plugins when they apply.

As another example, my Le P'tit Aurèle 
project.  If I were to (when the project is ready) blitz social media with
stuff related to that project, it would all be with titles that fall under
an umbrella of "Constructing Comprehensive yet User-Friendly Multilingual
Dictionaries"  (well, something sexier that can go "viral").  And every
"post" to whatever social media would have a "by the way, this was built
with TiddlyWiki."

If there are a ridiculous number of videos out there on how to do
real-world good stuff and they all of the things done happen to be done
with TiddlyWiki, I think that would grab some attention.

Something like that ...




On Wed, Jun 23, 2021 at 6:15 AM TiddlyTweeter 
wrote:

> Ciao cj.v...
>
> Yeah. In the practicalities of dealing with code I think it is easy to
> forget/set-aside certain things,
>
> The FREEDOM TW brings to dealing with information design and use is not
> shouted enough.
>
> I'd love if the tool were more widely used.
> I'm thinking a bit here out loud.
>
> How can we communicate better to potential end users its fundamental
> benefits?
>
> Best wishes
> TT
> On Wednesday, 23 June 2021 at 03:47:15 UTC+2 cj.v...@gmail.com wrote:
>
>> That would be a perfect theme song for TiddlyWiki.  Freedom for sure !
>>
>> I find Jon Batiste one of the coolest guys.  Wonderfully talented and
>> seems like a genuinely awesome human being.
>>
>> On Tuesday, June 22, 2021 at 6:04:50 PM UTC-3 TiddlyTweeter wrote:
>>
>>> https://youtu.be/3YHVC1DcHmo
>>>
>>> Oh yeah
>>> TT
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/HK3SOQdYvTs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/ea5e6f6d-f14b-4a6c-9a11-6504f80fe279n%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/CAMu8EfNiJMGKG488cVfYFSKi3EwQA_Sdus5stkjxmQCGewhXgw%40mail.gmail.com.

[tw5] Re: Edit While Scrolling Content CSS

[Mat]

iamdar... , you may be interested in the SideEditor 


<:-)

On Wednesday, June 16, 2021 at 6:32:47 PM UTC+2 iamdar...@gmail.com wrote:

> Hello,
>
> The below CSS is a slightly modified submission by Soren over on a 
> different thread: https://groups.google.com/g/tiddlywiki/c/AbBmtgL7s74
>
> When a Tiddler is edited it drops to the bottom of the screen and stays 
> there until it is saved. While locked at the bottom of the screen you can 
> still open and scroll through other Tiddlers. When scrolling the Tiddlers 
> being viewed go behind the one being edited. Also, the edit Tiddler is set 
> to 500px height so if the Tiddler has a lot of content a scrollbar will 
> appear vs it pushing up the screen and covering more of the stream. I 
> wanted to post it here because the above thread was getting very long and I 
> wanted to share the below code in case it was helpful for anyone else.
>
> div.tc-tiddler-frame { max-width: 60em; margin-left: auto; margin-right: 
> auto; } 
> div.tc-tiddler-edit-frame { max-width: 90em; margin-left: auto; 
> margin-right: auto; max-height: 500px; overflow:auto; position: fixed; 
> bottom: 0; z-index:2; } 
> div.tc-tiddler-body { max-width: 50em; margin: auto; }  
> .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor { width: 69%; } 
> div.tc-tiddler-preview-preview { width: 29%; }
>
>
> Some things to consider:
>
> 1) If you Edit more than one tiddler at a time they will overlap each 
> other.
> 2) If you use a plugin like Stroll, specifically its two column view, 
> while the edit tiddler will move to the bottom and allow scrolling, the 
> alignment is based on which column the tiddler was in prior to selecting 
> edit.
> 3) This is new code so any unintended effects it may have on other areas 
> of TiddlyWiki are unknown.
>
> Thanks!
>
>
>

-- 
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/f62bbc85-e6c7-43cd-beeb-ca23422f42cfn%40googlegroups.com.

[tw5] Re: TiddlyWiki SO cool ...

[TiddlyTweeter]

Footnote, cj.v...

Jon Batiste is certainly one great musician :-)

https://www.youtube.com/watch?v=gyds04mi_Z0 (JAZZ NIGHT IN AMERICA)

 TT
On Wednesday, 23 June 2021 at 03:47:15 UTC+2 cj.v...@gmail.com wrote:

> That would be a perfect theme song for TiddlyWiki.  Freedom for sure !
>
> I find Jon Batiste one of the coolest guys.  Wonderfully talented and 
> seems like a genuinely awesome human being.
>
> On Tuesday, June 22, 2021 at 6:04:50 PM UTC-3 TiddlyTweeter wrote:
>
>> https://youtu.be/3YHVC1DcHmo
>>
>> Oh yeah
>> TT
>>
>

-- 
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/cff5c3af-5736-4e60-a6f0-5d26bfd5c00bn%40googlegroups.com.

[tw5] Re: TiddlyWiki SO cool ...

[TiddlyTweeter]

Ciao cj.v...

Yeah. In the practicalities of dealing with code I think it is easy to 
forget/set-aside certain things,

The FREEDOM TW brings to dealing with information design and use is not 
shouted enough.

I'd love if the tool were more widely used. 
I'm thinking a bit here out loud.

How can we communicate better to potential end users its fundamental 
benefits?

Best wishes
TT
On Wednesday, 23 June 2021 at 03:47:15 UTC+2 cj.v...@gmail.com wrote:

> That would be a perfect theme song for TiddlyWiki.  Freedom for sure !
>
> I find Jon Batiste one of the coolest guys.  Wonderfully talented and 
> seems like a genuinely awesome human being.
>
> On Tuesday, June 22, 2021 at 6:04:50 PM UTC-3 TiddlyTweeter wrote:
>
>> https://youtu.be/3YHVC1DcHmo
>>
>> Oh yeah
>> TT
>>
>

-- 
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/ea5e6f6d-f14b-4a6c-9a11-6504f80fe279n%40googlegroups.com.

[tw5] Re: Embedding tiddler title in image URL

[PMario]

Hi,
The docs can be found at: 
https://tiddlywiki.com/#Transclusion%20in%20WikiText  Also click the links 
at the end of the tiddler!!
-m

-- 
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/1a811b34-a175-4fb0-bee6-63c25367a6aen%40googlegroups.com.

[tw5] Re: Embedding tiddler title in image URL

[PMario]

On Wednesday, June 23, 2021 at 9:17:46 AM UTC+2 cjec...@gmail.com wrote:

Mini-rant: all these different syntaxes are just a tad confusing :) 
> Sometimes {{..}}, sometimes {{{..}}}, sometimes <<..>>, sometimes $(..)$, 
> probably others I haven't stumbled on yet. Hard to keep track.
>

We do have to do different things, that doesn't work with the same syntax. 
The parser needs differences to decide what to do. 

{{title}} ... is the *convenience shortcut* for <$transclude tiddler=title 
/> and it produces the exact same output.

{{{ [[filter string]] }}} is the *shortcut* for  <$list filter="[[filter 
string]]"><$link />

-

<>  is the syntax to call a macro that has to be defined with:

\define macro-name() some text

macros do only 1 thing. They substitute text. 

-

\define build-url(title) https://tiddlywiki.com/#$title$

<>

With this example the parameter that is given to the macro call, will 
replace the string $title$. Then the macro output is used. 



\define build-url(title:Plugins) 
[[https://tiddlywiki.com/#:$(currentTiddler)$ $(a)$ $(b)$ $title$]]

<$vars a=Learning b=Features>
<$tiddler tiddler="HelloThere">
<>



The code above does a similar thing. It replaces $(currentTiddler)$ with 
the variable currentTiddler, that is defined by the tiddler-widget. The 
same is true for "a" and "b" ... title is from the first example

The outer [[]] is needed, to be able to uses spaces between the elements. 
.. If you don't have the braces the link would need to look like this.

https://tiddlywiki.com/#:$(currentTiddler)$%20$(a)$%20$(b)$%20$title$

Hope that helps a bit
-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/66918be2-5aed-495c-859f-8d92399f5285n%40googlegroups.com.

[tw5] Re: Embedding tiddler title in image URL

[cjec...@gmail.com]

Hey, cool! The $(..)$ syntax was the key. It also works within tiddler 
transclusion, e.g., {{$(currentTiddler)$ Discussion}}, which allowed me to 
finished the template. My main tiddlers now just have the single line 
<> and everything works.

Mini-rant: all these different syntaxes are just a tad confusing :) 
Sometimes {{..}}, sometimes {{{..}}}, sometimes <<..>>, sometimes $(..)$, 
probably others I haven't stumbled on yet. Hard to keep track.

Thanks to both of you for your help!

--nathanael

On Wednesday, June 23, 2021 at 12:51:52 PM UTC+8 Eric Shulman wrote:

> On Tuesday, June 22, 2021 at 7:45:51 PM UTC-7 cjec...@gmail.com wrote:
>
>> ...embed the tiddler title in the url, i.e.:
>>
> [img[images/{{!!title}}.jpg]]
>> But of course that just gets read literally. I've also tried using a 
>> variable with the same result:
>> <$set name="image" value="images/{{!!title}}.jpg">
>> [image[<>]]
>> 
>>
>
> The problem is that you can't directly mix field transclusion syntax, 
> e.g., {{!!fieldname}}, within other wiki syntax, e.g., [img[...]]
>
> The solution is to define a macro that constructs the desired wiki image 
> syntax, like this:
> \define showImage() [img[images/$(currentTiddler)$.jpg]]
> Then, invoke it like this:
> <>
>
> Notes:
> * By default, within each tiddler, the variable "currentTiddler" holds the 
> name of the tiddler
> * In normal tiddler content, you can use either {{!!title}} or 
> <> to *display* the name of the tiddler
> * Within the macro definition, $(...)$ does a *text substitution* of the 
> indicated variable, where the variable is defined *outside* the macro
> * After variable substitutions are done, the resulting macro content is 
> "returned" for rendering
> * Thus, if the above macro is invoked within a tiddler named "Tiddler1", 
> the macro content returned by <> will be: 
> [img[images/Tiddler1.jpg]], which is the syntax you want.
> * To use <> in multiple tiddlers, just place the showImage() 
> macro definition in a tiddler by itself (e.g., "ShowImageMacro"), and then 
> tag that tiddler with *$:/tags/Macro*.
>
> Also, as an alternative to using a macro definition to construct the 
> desired syntax, you could use the <$image> widget with a parameter value 
> that is assembled using "filtered transclusion", like this:
><$image source={{{ [[images/]addsuffixaddsuffix[.jpg]] 
> }}} />
> However, this syntax is obviously more complex to produce the exact same 
> result.
>
> 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/1e273193-745a-4283-94b4-ab2343f231ebn%40googlegroups.com.