[tw5] Re: Stylesheet question. I am trying to find the cause of the story river's top margin

[Álvaro]

If you want tiddler on the top of viewport, it works in empty edition -> 
https://tiddlywiki.com/empty.html

[image: padding-top.png]


Unless you are not looking for that or there is a lack of information about 
what you want or about details of your tiddlywiki. 
El miércoles, 6 de abril de 2022 a las 20:12:07 UTC+2, thyl...@gmail.com 
escribió:

> Setting padding-top to 0 didn't work.
>
> On Wednesday, April 6, 2022 at 6:08:14 AM UTC-5 Álvaro wrote:
>
>> The story river doesn't have any margin between it and the top of 
>> viewport.
>> If you are talking about the gap between the first tiddler in story river 
>> and the top of viewport. It is caused by the `padding` of the story river, 
>> you can remove it:
>> ```
>> .tc-story-river {
>>   padding-top: 0;
>> }
>> ```
>>
>>
>> El miércoles, 6 de abril de 2022 a las 9:23:00 UTC+2, thyl...@gmail.com 
>> escribió:
>>
>>> Hello,
>>> I am trying to find what the cause of the margin of the story river's 
>>> top margin. Can't find it in any stylesheet.
>>>
>>> This is what I have tried in a custom stylesheet.
>>> ```
>>> section.tc-story-river {
>>>   position: absolute; //position: fixed also has been tried.
>>>   top: 0px;
>>>   border: 1px solid black;
>>> }
>>> ```
>>> But the CSS is not behaving the way I would expect. I looked at the all 
>>> the parent containers and cannot find anything could causing the story 
>>> river being pushed down.
>>> 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/f8bd4169-3715-4be2-bbf0-2b1b2dc04baan%40googlegroups.com.

[tw5] Re: Stylesheet question. I am trying to find the cause of the story river's top margin

[Álvaro]

The story river doesn't have any margin between it and the top of viewport.
If you are talking about the gap between the first tiddler in story river 
and the top of viewport. It is caused by the `padding` of the story river, 
you can remove it:
```
.tc-story-river {
  padding-top: 0;
}
```


El miércoles, 6 de abril de 2022 a las 9:23:00 UTC+2, thyl...@gmail.com 
escribió:

> Hello,
> I am trying to find what the cause of the margin of the story river's top 
> margin. Can't find it in any stylesheet.
>
> This is what I have tried in a custom stylesheet.
> ```
> section.tc-story-river {
>   position: absolute; //position: fixed also has been tried.
>   top: 0px;
>   border: 1px solid black;
> }
> ```
> But the CSS is not behaving the way I would expect. I looked at the all 
> the parent containers and cannot find anything could causing the story 
> river being pushed down.
> 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/8de4bf1e-0339-483c-9ced-81a6846449a9n%40googlegroups.com.

[tw5] Re: TiddlyWiki documentation request: improve access to examples

[Álvaro]

Yes, I agree. The click is better solution for learners.

El viernes, 1 de abril de 2022 a las 9:35:17 UTC+2, PMario escribió:

> Go to Advanced search. Search for ".operator" (without the quotes) and 
> have a look at the *system tab*. There are 2 results. 
> You basically can find absolutely everything in TW with advanced search, 
> if you switch tabs.
> -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/9f636ae4-9373-4824-af7c-5fdd8c586b4cn%40googlegroups.com.

[tw5] Re: TiddlyWiki documentation request: improve access to examples

[Álvaro]

It's true. It is difficult to find if we don't know how do it. In tab 
System of AdvancedSearch, its tiddler can be found-> ` 
$:/editions/tw5.com/operator-macros 
`if you enter its name (`.operator-example`) 

Maybe it could be together the other macros in the tiddler `Documentation 
Macros` and we also say the tiddlers where are the macros.
El jueves, 31 de marzo de 2022 a las 16:55:12 UTC+2, cj.v...@gmail.com 
escribió:

> As part of the learning process, it is really handy to see all of the 
> TiddlyWiki goodness involved in any examples.
>
> That is frustratingly hard to do, because many examples are the result of 
> macro renderings.
>
> Take the "all Operator (Examples)" tiddler for, um, example (screenshot 
> further below):
>
> As I look at everything there, I am not only interested in how "all" 
> works, but I am also interested in how the "Try it" buttons work.
>
> When I edit that tiddler to see how things work, I see a whole bunch of 
> macro references.
>
> That's cool.  I also have an opportunity to see how macros work by 
> inspecting them.
>
> But I have no idea how to find these macros.
>
> So now I can't easily see how those "Try it" buttons are setup.
>
> These are roadblocks to learning TiddlyWiki things.
>
> I'd like to request that the documentation be setup such that learners can 
> easily discover things in that TiddlyWiki.  Either stop using macros as a 
> way to show examples (maybe replace them with transclusion templates, so 
> that there are tiddler titles available to find things), or add some 
> documentation to the documentation to make the macros easy to find.
>
> Something like that.
>
> [image: Screenshot 2022-03-31 11.41.49 AM.png]
>
>
>

-- 
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/557ec704-0656-49d7-aae5-ac5ccdbc0a6en%40googlegroups.com.

[tw5] Re: Method of using "nth-child(even)" with ""?

[Álvaro]

If you know the line-height in pre element you can use it to create your 
custom background with repeating-linear-gradient.
In the vanilla theme the (inherit) line-height is 20px, then you can use 
something like this
```
pre {
background: repeating-linear-gradient(#f5f5f5, #f5f5f5 20px, #e0e0e0 20px, 
#e0e0e0 40px);
}
```

El lunes, 21 de febrero de 2022 a las 6:27:09 UTC+1, Eric Shulman escribió:

> 1. `<__txt__>` is a *parameter reference* syntax that can only be used 
> within macro definitions.  It is similar to `$txt$`, which is a reference 
> to the value of the `txt` macro parameter passed into the macro.  However, 
> while occurances of `$txt$` are automatically replaced by the value passed 
> into the macro when the macro's content is returned, `<__txt__>` is handled 
> *as 
> if it was a variable*, and is only evaluated when the macro content is 
> subsequently parsed by within the calling syntax. It is a shorthand 
> equivalent to:
>
> ```
> \define macroname(param)
> <$vars param="$param$">
>... references to <> (or  if used within a filter) ...
>etc.
> 
> \end
> ```
>
> 2. `splitregexp[...]` is a *filter operator* and is similar to the 
> `split[...]` filter operator.  Note that both `split[..]` and 
> `splitregexp[...]` find and remove instances of the filter operand value, 
> producing multiple filter items as a result, which are then available for 
> further processing by the filter syntax.  The difference is that 
> `splitregexp[...]` accepts *regular expressions* as the value of the 
> filter operand, while `split[...]` only accepts *literal text*.  In this 
> instance, `splitregexp[\n]` is being used to "split the input (the value of 
> `<__txt__>`) into separate values by matching (and removing) any `newline` 
> characters.  Each resulting line of text is then assigned to the `line` 
> variable so it can be referenced in the body of the `<$list>...` 
> widget, where it is then output, enclosed within `...`, in order 
> to produce the final result of having separate child elements for each 
> line, so that the `nth-child(...)` CSS rule can be applied.
>
> -e
>
> On Sunday, February 20, 2022 at 5:44:29 PM UTC-8 justin.hu...@gmail.com 
> wrote:
>
>> That works! 
>>
>> I can generally grasp how this works, though I'm not familiar with 
>> <__txt__>splitregexp[\n]]
>>
>> the only time I've seen \n is to create a new line in python, is it doing 
>> the same here?
>>
>>
>>
>> On Sunday, February 20, 2022 at 8:15:49 PM UTC-5 Eric Shulman wrote:
>>
>>> If the content of your `` is stored in a separate tiddler or field, 
>>> you can force the creation of child `` elements, so that 
>>> `nth-child(even)` can be applied successfully.
>>>
>>> Give this a try:
>>> ```
>>> \define nthchild(txt,bg:"lightgray")
>>> \whitespace trim
>>>  .myClass div:nth-child(even) { background:$bg$; } 
>>> 
>>><$list filter="[<__txt__>splitregexp[\n]]" variable="line">
>>><$text text=<>/>
>>>
>>> 
>>> \end
>>>
>>> <$macrocall $name="nthchild" txt={{test}} bg="powderblue"/>
>>> ```
>>>
>>> where the text content is stored in a tiddler named "test".
>>>
>>> -e
>>> On Sunday, February 20, 2022 at 4:46:32 PM UTC-8 justin.hu...@gmail.com 
>>> wrote:
>>>
 Ah, well- that's a bummer haha

 Thank you!
 On Sunday, February 20, 2022 at 7:30:21 PM UTC-5 Eric Shulman wrote:

> Although HTML `` elements can display multiple lines of text, 
> each line is not a separate child element.
> Thus, a CSS rule such as `nth-child(even)` doesn't have any effect 
> within the `` element.
>
> -e
> On Sunday, February 20, 2022 at 4:13:04 PM UTC-8 
> justin.hu...@gmail.com wrote:
>
>> Hello all, title says it all.
>>
>> When trying to apply nth-child(even) to use a background color for 
>> each line when using  in my tiddlers, it doesn't seem to work, and 
>> I'm 
>> not entirely sure whats causing this.
>>
>> Any suggestions?
>>
>

-- 
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/16414c40-ae45-4165-94b2-5bd8ae1eaf76n%40googlegroups.com.

[tw5] Re: Changing tiddler on switch of sidebar tab

[Álvaro]

In the macrocall <https://tiddlywiki.com/#MacroCallWidget> widget you have 
to use the params of the macro. It would be *action=X* , where X is the 
your action-setfield widget, but I don't know if we can use the widget 
directly inside the triple doble quotes """ or we need create a macro for 
the action (something like documentation does in *Using action string 
attributes* in ActionWidgets <https://tiddlywiki.com/#ActionWidgets> but 
using the macrocall instead of button)

El miércoles, 8 de diciembre de 2021 a las 22:40:35 UTC+1, sc...@sauyet.com 
escribió:

> I guess I have the syntax wrong.  This isn't working:
>
>  <$macrocall $name="tabs" 
> tabsList="[all[shadows+tiddlers]tag[$:/tags/SideBar]!has[draft.of]]" 
> default={{$:/config/DefaultSidebarTab}} state="$:/state/tab/sidebar" 
> class="tc-sidebar-tabs-main" 
> explicitState="$:/state/tab/sidebar--595412856" $action-setfield="$tiddler= 
> $:/themes/tiddlywiki/vanilla/options/sidebarlayout text={{{ 
> [[$:/state/tab/sidebar--595412856]get[text]match[$:/core/ui/SideBar/Open]then[fluid-fixed]else[fixed-fluid]]
>  
> }}}"/> 
>
> I'm not sure how to embed the action-setfield inside the macrocall.  The 
> examples <https://tiddlywiki.com/#ActionSetFieldWidget> all have them 
> inside $button widgets.
>
> Any suggestions?
>
>   -- Scott
> On Monday, December 6, 2021 at 8:22:21 AM UTC-5 Scott Sauyet wrote:
>
>> Thank you very much.  I won't get back to this until midweek, but it does 
>> look as though it will work. 
>>
>> Cheer,
>>
>>   -- Scott
>> On Saturday, December 4, 2021 at 12:21:30 PM UTC-5 Álvaro wrote:
>>
>>> The conditional would be something like 
>>> *{{{ 
>>> [[$:/state/tab/sidebar--595412856]get[text]match[$:/core/ui/SideBar/Open]then[fluid-fixed]else[fixed-fluid]]
>>>  
>>> }}}*
>>>
>>> You can create a tiddler with the above filtered transclusion and then 
>>> you can view how the text changes depend on of current tab in sidebar  (
>>> *$:/core/ui/SideBar/Open*  *vs* the rest of tabs)
>>> El sábado, 4 de diciembre de 2021 a las 0:06:07 UTC+1, sc...@sauyet.com 
>>> escribió:
>>>
>>>> That looks like it might work.  I still have to figure out the 
>>>> conditional logic, but that should be doable.
>>>>
>>>> Thank you very much,  Álvaro!
>>>>
>>>> On Friday, December 3, 2021 at 7:50:55 AM UTC-5 Álvaro wrote:
>>>>
>>>>>
>>>>> I don't know if I understand you.
>>>>>
>>>>> In *$:/core/ui/SideBarSegments/tabs* you have the *tabs* macro, it 
>>>>> save the current tab in a tiddler and it has a optional parameter for 
>>>>> actions. Tabs macro documentation 
>>>>> <https://tiddlywiki.com/#tabs%20Macro> 
>>>>>
>>>>> Maybe you can use the action parameter to use an action-setfield 
>>>>> <https://tiddlywiki.com/#ActionSetFieldWidget> to change the text of 
>>>>> the tiddler *$:/themes/tiddlywiki/vanilla/options/sidebarlayout*  
>>>>> depends on the selected tab with a filtered transclusion 
>>>>> <https://tiddlywiki.com/#Transclusion%20in%20WikiText> 
>>>>> El lunes, 29 de noviembre de 2021 a las 22:08:22 UTC+1, 
>>>>> sc...@sauyet.com escribió:
>>>>>
>>>>>> I'm building a a documentation TW5 and was hoping to dynamically 
>>>>>> toggle the vanilla theme's ` 
>>>>>> $:/themes/tiddlywiki/vanilla/options/sidebarlayout` tiddler between 
>>>>>> `fluid-fixed` and `fixed-fluid` based upon which sidebar tab is loaded.  
>>>>>> Is 
>>>>>> there a straightforward way to do this?  It looks as though Actions will 
>>>>>> let me make the change, but I don't know how to capture the event.  Is 
>>>>>> there a simple mechanism.
>>>>>>
>>>>>> The broader picture is that I have lots of content including large 
>>>>>> diagrams and at least one Reveal presentation and much more, much of 
>>>>>> which 
>>>>>> is better shown in a wide story river, but I also want to include 
>>>>>> TiddlyMindMap and be able to easily edit and adjust the diagram, which 
>>>>>> seems to need a wide sidebar.  I thought that if I could simply change 
>>>>>> that 
>>>>>> tiddler before the new sidebar tab is shown, it would handle this.  But 
>>>>>> other suggestions for how to achieve this behavior would be gratefully 
>>>>>> accepted.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>   -- Scott
>>>>>>
>>>>>

-- 
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/5d20412d-9469-4da6-ae3c-b4717b64685dn%40googlegroups.com.

[tw5] Re: Automatically generating grocery list by clicking on cooking recipes ?

[Álvaro]

As they said, you have to think about how save the ingredients of the 
recipe in the tiddler, you can use the index of a data tiddler for recipe 
or simply the field of a tiddler for recipe. 

Then you would need to use the filters  
and their operators. You will need to retrieve the data for your grocery 
list.
El sábado, 4 de diciembre de 2021 a las 23:37:47 UTC+1, cj.v...@gmail.com 
escribió:

> Example of something to keep in mind: if a recipe calls for 100grams of 
> onion, you'll want to convert that into something useful for grocery 
> shopping.
>
> Probably good to instead talk about a measure of an onion for groceries.  
> You won't be buying a 100 g onion, so you'll want to have 1 onion, 
> regardless of size and know you'll have left-over onion for your omelette 
> the next day.  Because you need about 1/4 of a small onion, or whatever  of 
> a big onion.
>
> But if you need an amount of grams o' onion that requires a large onion, 
> then you'll want a way to say a large onion.  Or two small onions.  Or 
> whatever.  Knowing you'll be doing a little bit of rough math at the 
> grocery store.
>
> Your grocery list will get messy if you have 1 small onion and 1 large 
> onion when the onions are in a bag.
>
> All of that to say, don't be to quick to start building everything in TW 
> until you can visualize (spreadsheet or whatever) get a somewhat reasonable 
> amount of "stuff" for the big picture.
>
> This process will help you decide to what degree of complex you want, and 
> how/what/where to simplify when you don't want to get that bogged down in 
> complexity, yadda yadda.
>
> On Saturday, December 4, 2021 at 6:17:49 PM UTC-4 Télumire wrote:
>
>> You could do it like this : 
>>
>> Create a data tiddler for a recipe with a quantity associated to each 
>> ingredient. To make things easier the unit will be hardcoded in grams (or 
>> whatever you like, but always the same).
>>
>> Then you can select your recipe for the week with a select widget for 
>> example (https://tiddlywiki.com/#SelectWidget), use the data of the 
>> widget in a list widget (https://tiddlywiki.com/#ListWidget) which will 
>> sum the values of each unique index accross the data-tiddlers you selected.
>>
>> I think you will need the count Operator (
>> https://tiddlywiki.com/#count%20Operator),  getindex Operator (
>> https://tiddlywiki.com/#getindex%20Operator),  sum Operator  (
>> https://tiddlywiki.com/#sum%20Operator). Good luck and let me know if 
>> you need help to understand something :) 
>>
>> Le samedi 4 décembre 2021 à 22:50:32 UTC+1, cassandr...@gmail.com a 
>> écrit :
>>
>>> Hello everyone, 
>>>
>>> New here, using TW since a year ago but only for simple notekeeping 
>>> which didn't use a lot of in deep knowledge with it.
>>>
>>> I'm currently using the latest version available of TW (the v5.2.0 I 
>>> think ?).
>>>
>>> So here's my problem. As an effort to manage a bit more my money and my 
>>> time, I decided to invest in a batch cooking book which has proven great 
>>> overtime.
>>> My problem is that each week, I need to manually type the cooking list 
>>> on my phone/computer.
>>> I decided if I keep on doing it for a long time, I could as well 
>>> simplify the process. I thought about using TW but I am at loss as how to 
>>> do it.
>>>
>>> *What I would want ideally* : 
>>> - To click on or in the tiddler "Week 1" for example and have an 
>>> automatic generated list of all the ingredients I need to buy for this week
>>> - At the same time, I wish I could check/uncheck which recipe I would 
>>> want to in this week or not and have the adapted grocery list
>>> - As an add-on, it would be great if I could check multiples ingredients 
>>> and see recipe which contain them
>>>
>>> The first thing (in my mind) doesn't seem complicated as I can simply 
>>> write the grocery list in "hard".
>>> But I can't even begin to imagine how to "uncheck" a recipe of this week 
>>> and "decrease" the grocery list accordingly. 
>>> As a very very very basic knowledge (minimal), it would be like for 
>>> exemple creating a variable for "egg" which would contain "4" if all recipe 
>>> are checked but if I uncheck recipe for the tuesday which contain an egg, 
>>> the variable egg will be "3".
>>> And to do it for all ingredients / recipe.
>>>
>>> Is someone here has an idea how to begin or to do something similar, I'm 
>>> all ear !
>>>
>>> Thank for your answers
>>>
>>>
>>>

-- 
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/085e0f8b-f8e8-41dc-b5c5-b74a9c59ae5dn%40googlegroups.com.

[tw5] Re: Changing tiddler on switch of sidebar tab

[Álvaro]

The conditional would be something like 
*{{{ 
[[$:/state/tab/sidebar--595412856]get[text]match[$:/core/ui/SideBar/Open]then[fluid-fixed]else[fixed-fluid]]
 
}}}*

You can create a tiddler with the above filtered transclusion and then you 
can view how the text changes depend on of current tab in sidebar  (
*$:/core/ui/SideBar/Open*  *vs* the rest of tabs)
El sábado, 4 de diciembre de 2021 a las 0:06:07 UTC+1, sc...@sauyet.com 
escribió:

> That looks like it might work.  I still have to figure out the conditional 
> logic, but that should be doable.
>
> Thank you very much,  Álvaro!
>
> On Friday, December 3, 2021 at 7:50:55 AM UTC-5 Álvaro wrote:
>
>>
>> I don't know if I understand you.
>>
>> In *$:/core/ui/SideBarSegments/tabs* you have the *tabs* macro, it save 
>> the current tab in a tiddler and it has a optional parameter for actions. 
>> Tabs 
>> macro documentation <https://tiddlywiki.com/#tabs%20Macro> 
>>
>> Maybe you can use the action parameter to use an action-setfield 
>> <https://tiddlywiki.com/#ActionSetFieldWidget> to change the text of the 
>> tiddler *$:/themes/tiddlywiki/vanilla/options/sidebarlayout*  depends on 
>> the selected tab with a filtered transclusion 
>> <https://tiddlywiki.com/#Transclusion%20in%20WikiText> 
>> El lunes, 29 de noviembre de 2021 a las 22:08:22 UTC+1, sc...@sauyet.com 
>> escribió:
>>
>>> I'm building a a documentation TW5 and was hoping to dynamically toggle 
>>> the vanilla theme's ` $:/themes/tiddlywiki/vanilla/options/sidebarlayout` 
>>> tiddler between `fluid-fixed` and `fixed-fluid` based upon which sidebar 
>>> tab is loaded.  Is there a straightforward way to do this?  It looks as 
>>> though Actions will let me make the change, but I don't know how to capture 
>>> the event.  Is there a simple mechanism.
>>>
>>> The broader picture is that I have lots of content including large 
>>> diagrams and at least one Reveal presentation and much more, much of which 
>>> is better shown in a wide story river, but I also want to include 
>>> TiddlyMindMap and be able to easily edit and adjust the diagram, which 
>>> seems to need a wide sidebar.  I thought that if I could simply change that 
>>> tiddler before the new sidebar tab is shown, it would handle this.  But 
>>> other suggestions for how to achieve this behavior would be gratefully 
>>> accepted.
>>>
>>> Thanks,
>>>
>>>   -- Scott
>>>
>>

-- 
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/1fd9438e-4f01-4af9-93dc-7ae7315ebf8bn%40googlegroups.com.

[tw5] Re: Changing tiddler on switch of sidebar tab

[Álvaro]

I don't know if I understand you.

In *$:/core/ui/SideBarSegments/tabs* you have the *tabs* macro, it save the 
current tab in a tiddler and it has a optional parameter for actions. Tabs 
macro documentation  

Maybe you can use the action parameter to use an action-setfield 
 to change the text of the 
tiddler *$:/themes/tiddlywiki/vanilla/options/sidebarlayout*  depends on 
the selected tab with a filtered transclusion 
 
El lunes, 29 de noviembre de 2021 a las 22:08:22 UTC+1, sc...@sauyet.com 
escribió:

> I'm building a a documentation TW5 and was hoping to dynamically toggle 
> the vanilla theme's ` $:/themes/tiddlywiki/vanilla/options/sidebarlayout` 
> tiddler between `fluid-fixed` and `fixed-fluid` based upon which sidebar 
> tab is loaded.  Is there a straightforward way to do this?  It looks as 
> though Actions will let me make the change, but I don't know how to capture 
> the event.  Is there a simple mechanism.
>
> The broader picture is that I have lots of content including large 
> diagrams and at least one Reveal presentation and much more, much of which 
> is better shown in a wide story river, but I also want to include 
> TiddlyMindMap and be able to easily edit and adjust the diagram, which 
> seems to need a wide sidebar.  I thought that if I could simply change that 
> tiddler before the new sidebar tab is shown, it would handle this.  But 
> other suggestions for how to achieve this behavior would be gratefully 
> accepted.
>
> Thanks,
>
>   -- Scott
>

-- 
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/a4866338-06e2-450d-8437-26d1af7450d9n%40googlegroups.com.

[tw5] Re: Getting to know regular expressions

[Álvaro]

Hi,
There is a wiki for regexp in TW 
El martes, 19 de octubre de 2021 a las 22:07:29 UTC+2, cj.v...@gmail.com 
escribió:

> Rats.  I forgot to mention: I'll be studying the regular expression stuff 
> from grep that is common with javascript.
>
> (I want to learn common grep/javascript stuff first because it is useful 
> for both things I'm doing with the GNU nano text editor and applying in 
> TiddlyWiki.)
>
> At some point, I'll get into the javascript-specific regular expression 
> stuff.
>
> On Tuesday, October 19, 2021 at 4:52:07 PM UTC-3 PMario wrote:
>
>> Hi,
>> That's the source where I do get my info about regular expressions for 
>> javascript: https://www.regular-expressions.info/javascript.html
>> -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/10edfccd-60d9-44a1-a76f-fee6e8e75aden%40googlegroups.com.

[tw5] Re: Just a Filtering Code Pattern

[Álvaro]

I think that deleted reply was mine. I will copy and paste from Tiddlytalk

---
@Télumire . It’s true. They works like an OR. {{{ [tag[Tag 1],[Tag 2],[Tag 
3],[Tag 4]] }}} also return different result. This behaviour would be 
documented. 

El martes, 28 de septiembre de 2021 a las 2:41:03 UTC+2, TW Tones escribió:

> JP,
>
> One way of handling all tags on the current tiddler is not to use the 
> various tag operators but address the tags field directly.
>
> [all[current]get[tags]] returns the content of the tags field which 
> includes all tags.
>
> Does this meet with your requirement?
>
> On Monday, 27 September 2021 at 22:08:07 UTC+10 jn.pierr...@gmail.com 
> wrote:
>
>> Just a thought: it would be fine if the tagging operator could have a 
>> "all" parameter which would select tiddlers tagging all of the tags in 
>> input (currently, that's "any tag is enough").
>>
>> Thus we would have a simple and readable solution as:
>>
>> {{{ [tag1 tag2 tag3 tag4 +[tagging:all[]]] }}}
>>
>> Le lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>>
>>> Hello all ! 
>>> The filter syntax provided by @Álvaro  is very neat but doesnt match 
>>> the requirements of cj.v : counting the tiddlers with 4 specifics tags 
>>> and only those tiddlers.
>>>
>>> See this screenshot  :
>>>
>>> https://i.imgur.com/lVlsYZt.png
>>>
>>> I think it's because the commas imply an OR condition, but here we want 
>>> an AND :)
>>>
>>> So with a a tiny bit of tweaking the correct filter is : 
>>>
>>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]] 
>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>
>>> Here's a live demo : 
>>>
>>>
>>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>>
>>>> - In the fields cases we have a workaround with `fields` operator. It 
>>>> has suffixs (exclude, include)
>>>> - I think that there in't any tiddler with those tags. The search is 
>>>> the tiddler with all these tags (¿and any other?)
>>>>
>>>> In the case of titles, you find a issue, but I don't know its reason. I 
>>>> was trying to find a workaround but i wasn't lucky. I also found that the 
>>>> match operator doesn't support multiple parameters.
>>>>
>>>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones 
>>>> escribió:
>>>>
>>>>> Of even this {{{ [tag[Common 
>>>>> Operators],[HelloThere],[TableOfContents]] }}}
>>>>>
>>>>> On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:
>>>>>
>>>>>> Very interesting. 
>>>>>>
>>>>>> I think he documentation should be expanded to detail this. Multiple 
>>>>>> parameters to operators are only documented in a few operators, but if I 
>>>>>> read this correctly they can work on operators in *general*?
>>>>>>
>>>>>> If general you may expect this to work ```{{{ 
>>>>>> [title[tid1],[tid2],[tid3]] }}}``` it does not.
>>>>>> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
>>>>>> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>>>>>>
>>>>>>> I just tested this on both 5.1.23 and 5.2.0pre. I created one 
>>>>>>> tiddler containing
>>>>>>> ```
>>>>>>> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
>>>>>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>>>>> ```
>>>>>>>
>>>>>>> and another tiddler with the four tags (note capitalization and 
>>>>>>> spaces in the tag values).
>>>>>>>
>>>>>>> It *does* seem to work on both versions of TW
>>>>>>> -e
>>>>>>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>>>>>>
>>>>>>>> Alvaro;
>>>>>>>>
>>>>>>>> You suggested something like this
>>>>>>>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>>>

[tw5] Re: Just a Filtering Code Pattern

[Álvaro]

@Télumire . It's true. They works like an OR. `{{{ [tag[Tag 1],[Tag 2],[Tag 
3],[Tag 4]]  }}}` also return different result. This behaviour would be 
documented.

El lunes, 27 de septiembre de 2021 a las 14:08:07 UTC+2, 
jn.pierr...@gmail.com escribió:

> Just a thought: it would be fine if the tagging operator could have a 
> "all" parameter which would select tiddlers tagging all of the tags in 
> input (currently, that's "any tag is enough").
>
> Thus we would have a simple and readable solution as:
>
> {{{ [tag1 tag2 tag3 tag4 +[tagging:all[]]] }}}
>
> Le lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>
>> Hello all ! 
>> The filter syntax provided by @Álvaro  is very neat but doesnt match the 
>> requirements of cj.v : counting the tiddlers with 4 specifics tags and 
>> only those tiddlers.
>>
>> See this screenshot  :
>>
>> https://i.imgur.com/lVlsYZt.png
>>
>> I think it's because the commas imply an OR condition, but here we want 
>> an AND :)
>>
>> So with a a tiny bit of tweaking the correct filter is : 
>>
>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]] 
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Here's a live demo : 
>>
>>
>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>
>>> - In the fields cases we have a workaround with `fields` operator. It 
>>> has suffixs (exclude, include)
>>> - I think that there in't any tiddler with those tags. The search is the 
>>> tiddler with all these tags (¿and any other?)
>>>
>>> In the case of titles, you find a issue, but I don't know its reason. I 
>>> was trying to find a workaround but i wasn't lucky. I also found that the 
>>> match operator doesn't support multiple parameters.
>>>
>>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones 
>>> escribió:
>>>
>>>> Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] 
>>>> }}}
>>>>
>>>> On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:
>>>>
>>>>> Very interesting. 
>>>>>
>>>>> I think he documentation should be expanded to detail this. Multiple 
>>>>> parameters to operators are only documented in a few operators, but if I 
>>>>> read this correctly they can work on operators in *general*?
>>>>>
>>>>> If general you may expect this to work ```{{{ 
>>>>> [title[tid1],[tid2],[tid3]] }}}``` it does not.
>>>>> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
>>>>> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>>>>>
>>>>>> I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
>>>>>> containing
>>>>>> ```
>>>>>> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
>>>>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>>>> ```
>>>>>>
>>>>>> and another tiddler with the four tags (note capitalization and 
>>>>>> spaces in the tag values).
>>>>>>
>>>>>> It *does* seem to work on both versions of TW
>>>>>> -e
>>>>>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>>>>>
>>>>>>> Alvaro;
>>>>>>>
>>>>>>> You suggested something like this
>>>>>>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>>>>>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>>>>>
>>>>>>> As far as I can see this does not work on the pre-release and the 
>>>>>>> t6ag format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not 
>>>>>>> documented
>>>>>>>
>>>>>>> Does not work. So I asked if you tested this?
>>>>>>>
>>>>>>>
>>>>>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>>>>>
>>>>>>>> I don't know if I understand you.
>>>>>>>>
>>>>>>>>
>>>>>>>> El sábado, 25 de septiembre de

[tw5] Re: Just a Filtering Code Pattern

[Álvaro]

- In the fields cases we have a workaround with `fields` operator. It has 
suffixs (exclude, include)
- I think that there in't any tiddler with those tags. The search is the 
tiddler with all these tags (¿and any other?)

In the case of titles, you find a issue, but I don't know its reason. I was 
trying to find a workaround but i wasn't lucky. I also found that the match 
operator doesn't support multiple parameters.

El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones escribió:

> Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] }}}
>
> On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote:
>
>> Very interesting. 
>>
>> I think he documentation should be expanded to detail this. Multiple 
>> parameters to operators are only documented in a few operators, but if I 
>> read this correctly they can work on operators in *general*?
>>
>> If general you may expect this to work ```{{{ [title[tid1],[tid2],[tid3]] 
>> }}}``` it does not.
>> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
>> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>>
>>> I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler 
>>> containing
>>> ```
>>> {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] 
>>> :filter[tags[]count[]compare:eq[4]] }}}
>>> ```
>>>
>>> and another tiddler with the four tags (note capitalization and spaces 
>>> in the tag values).
>>>
>>> It *does* seem to work on both versions of TW
>>> -e
>>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>>
>>>> Alvaro;
>>>>
>>>> You suggested something like this
>>>> {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] 
>>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>>
>>>> As far as I can see this does not work on the pre-release and the t6ag 
>>>> format  [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified)  is not 
>>>> documented
>>>>
>>>> Does not work. So I asked if you tested this?
>>>>
>>>>
>>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>>
>>>>> I don't know if I understand you.
>>>>>
>>>>>
>>>>> El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones 
>>>>> escribió:
>>>>>
>>>>>> Alvaro;
>>>>>>
>>>>>> Have you tested this?
>>>>>>
>>>>>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>>>>>> :filter[tags[]count[]compare:eq[4]]  }}}
>>>>>>
>>>>>> I cant see it working. Here 
>>>>>> <https://tiddlywiki.com/#Filter%20Parameter> is says 
>>>>>>
>>>>>> * NEW IN: 5.1.23 Filter operators support multiple parameters which 
>>>>>> are separated by a  ,  character.*
>>>>>>
>>>>>> *For example: [param1],[param2] or ,{param2}*
>>>>>> However as far as I can see only if such multiple parameters are 
>>>>>> documented in the operator in question.
>>>>>>
>>>>>> Tones
>>>>>> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>>>>>>
>>>>>>> It works fine. I tried to find a alternative, but I wasn't lucky.
>>>>>>>
>>>>>>> When I resee your filter, I remember about the multiple parameters 
>>>>>>> in filter operator with commas (from last version, 5.1.23). And we can 
>>>>>>> add 
>>>>>>> a second filter run that it applies your filter to result of first run. 
>>>>>>> Then you can rewrite your filter something like this (in filtering 
>>>>>>> transclusion)
>>>>>>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>>>>>>> :filter[tags[]count[]compare:eq[4]]  }}}
>>>>>>>
>>>>>>> Although maybe it be less understandble for you.
>>>>>>>
>>>>>>>
>>>>>>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2, 
>>>>>>> jn.pierr...@gmail.com escribió:
>>>>>>>
>>>>>>>> That's fine by me.
>>>>>>>>
>>>>>>>> And yes filters are fun even if sometimes a bit tricky.
>>>>>>>>
>>>

[tw5] Re: Just a Filtering Code Pattern

[Álvaro]

I don't know if I understand you.


El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones escribió:

> Alvaro;
>
> Have you tested this?
>
> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
> :filter[tags[]count[]compare:eq[4]]  }}}
>
> I cant see it working. Here <https://tiddlywiki.com/#Filter%20Parameter> 
> is says 
>
> * NEW IN: 5.1.23 Filter operators support multiple parameters which are 
> separated by a  ,  character.*
>
> *For example: [param1],[param2] or ,{param2}*
> However as far as I can see only if such multiple parameters are 
> documented in the operator in question.
>
> Tones
> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>
>> It works fine. I tried to find a alternative, but I wasn't lucky.
>>
>> When I resee your filter, I remember about the multiple parameters in 
>> filter operator with commas (from last version, 5.1.23). And we can add a 
>> second filter run that it applies your filter to result of first run. Then 
>> you can rewrite your filter something like this (in filtering transclusion)
>> {{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
>> :filter[tags[]count[]compare:eq[4]]  }}}
>>
>> Although maybe it be less understandble for you.
>>
>>
>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2, 
>> jn.pierr...@gmail.com escribió:
>>
>>> That's fine by me.
>>>
>>> And yes filters are fun even if sometimes a bit tricky.
>>>
>>> So for the fun of it, you could arrange your filter so that the input 
>>> would be the 4 tags you want.
>>>
>>> something like that:
>>>
>>> \define fun(tags)
>>> <$set variable=occ filter="[[$tags]put your filter code 
>>> here...count[]]">Seen <> tiddlers with tags $tags$
>>> \end
>>>
>>> Sometimes, this fun has you coding javascript filter operator. Would 
>>> this be the case here? I have not thought about it yet.
>>>
>>> cheers,
>>>
>>>
>>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a 
>>> écrit :
>>>
>>>> Me and my interest in brain age games, I couldn't help but play around 
>>>> with a filter to find all tiddlers that have all four specified tags, but 
>>>> only those four tags.
>>>>
>>>> You'll find three tiddlers in the attached json.  Download the file, 
>>>> and drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander.
>>>>
>>>> There are all kinds of ways to go about doing this sort of thing, with 
>>>> some filter operators maybe better suited, but I find the result a bit 
>>>> easier for me to understand (more logical to me, or maybe more 
>>>> self-explanatory, because of the way my brain works, I suppose.)  Maybe 
>>>> just a difference between top-down view vs bottom-up view or something ...
>>>>
>>>> Yeah, I find filters fun.
>>>>
>>>

-- 
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/c84aa10e-ef9b-47d3-a90f-f4100f3ef1b5n%40googlegroups.com.

[tw5] Re: Just a Filtering Code Pattern

[Álvaro]

I don't know if they are loving that or not. The commas aren't easy to see 
between brackets (for me). If I begin on end of filter run, i also have 
this problem. But any can build his/her mental shorcuts to avoid it. If 
someone can't solve a problem, maybe he/she can create a "alternative way"

Yes, I tried with the tagging operator and I see that behaviour.

El viernes, 24 de septiembre de 2021 a las 18:52:36 UTC+2, 
jn.pierr...@gmail.com escribió:

> I was thinking that the tagging operator was the zay to get tiddlers that 
> all share all of the tags in input. That's what the dec say: "output: the 
> titles of any tiddlers that carry the input tags".
>
> So my function would be:
>
> \define fun(tags)
> <$vars four="[tags[]count[]match[4]]">
> <$set variable=occ filter="[[$tags$]tagging[] :filter]">Seen <> 
> tiddlers with tags $tags$
> 
> \end
>
>  But in fact the effect of tagging is "output: the titles of any tiddlers 
> that carry ANY OF the input tags". Too bad for the instance. But I think a 
> correction in the doc would be welcome.
>
>
> Le vendredi 24 septembre 2021 à 10:59:50 UTC+2, Jean-Pierre Rivière a 
> écrit :
>
>> That's fine by me.
>>
>> And yes filters are fun even if sometimes a bit tricky.
>>
>> So for the fun of it, you could arrange your filter so that the input 
>> would be the 4 tags you want.
>>
>> something like that:
>>
>> \define fun(tags)
>> <$set variable=occ filter="[[$tags]put your filter code 
>> here...count[]]">Seen <> tiddlers with tags $tags$
>> \end
>>
>> Sometimes, this fun has you coding javascript filter operator. Would this 
>> be the case here? I have not thought about it yet.
>>
>> cheers,
>>
>>
>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a 
>> écrit :
>>
>>> Me and my interest in brain age games, I couldn't help but play around 
>>> with a filter to find all tiddlers that have all four specified tags, but 
>>> only those four tags.
>>>
>>> You'll find three tiddlers in the attached json.  Download the file, and 
>>> drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander.
>>>
>>> There are all kinds of ways to go about doing this sort of thing, with 
>>> some filter operators maybe better suited, but I find the result a bit 
>>> easier for me to understand (more logical to me, or maybe more 
>>> self-explanatory, because of the way my brain works, I suppose.)  Maybe 
>>> just a difference between top-down view vs bottom-up view or something ...
>>>
>>> Yeah, I find filters fun.
>>>
>>

-- 
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/a7516220-72de-484d-adaf-b36aacd29c3cn%40googlegroups.com.

Re: [tw5] Re: Question about the TiddlyWiki GG

[Álvaro]

Sorry for this late reply, now i rarely visit GG (here or in TiddlyTalk)

I've seen your rejection to tiddlytalk and your reasons. I understand them 
but also I think that you could have made a hasty decision. I also think 
that the edit of posts was a hasty decision. In your analogy there are some 
point that, IMHo; you don't take into account. They are about how we learn: 
with lessons/errors and with time to understand well the situation. The 
errors can be similar but they necessarily are equal, although the origin 
of annoyance was the same. Jack didn't have time to learn about it. 
TiddlyTalk also is a forum in "construction". The new options avaible in 
TiddlyTalk need to be carefully evaluated, but with so many options the 
community need more time to use them "correctly".

About your problem with the UI, I don't know how much could be mitigated so 
that it would not be annoying for you. Maybe with more details the 
"experts" (I'm not one) in Discouse can help you. The admin team also is 
work hard to see how solve the requirement of community. 


El jueves, 16 de septiembre de 2021 a las 16:06:30 UTC+2, cj.v...@gmail.com 
escribió:

> Well, personal cognitive issues regarding TiddlyTalk aside, edit of posts 
> by moderators, in and of itself, is reason enough for me to not participate 
> in a forum.
>
> That kind of thing goes against my personal I.T. philosophies ("protect 
> the system", "protect the users from bad system behaviour", "don't mess 
> with the users data unless asked to mess with it", "don't break things", 
> "no surprises", "no hidden interfaces", yadda yadda yadda.)
>
> Deletion of any posts that are not in line with terms of use policies, 
> that I totally agree with.  Tagging posts to make them easy to find, that's 
> very cool.
>
> And views vary depending on the thing.  Forum vs Wiki vs Blog vs whatever.
>
> Doesn't matter.  I'll stop harping about it.
>
>
>
> On Thu, Sep 16, 2021 at 10:31 AM Jeremy Ruston  
> wrote:
>
>> Hi CJ
>>
>> Thanks for the confirmation, Jeremy.  That is the way I like things.
>>
>> And the push I needed to bail on TiddlyTalk completely.
>>
>>
>> I think the incident was a momentary misjudgement on the part of an 
>> individual. It has led to a healthy discussion about what users expect when 
>> they write a post, and I think the conclusion is that the power to edit 
>> should only be used in exceptional circumstances. The admins have always 
>> had the power to delete posts and avoided exercising it except for spam, 
>> and so I don't see a reason to think that the new power to edit posts would 
>> be abused either.
>>
>> But of course I understand from your comments elsewhere that you have 
>> other concerns with talk.tiddlywiki.org about usability and simplicity 
>> which may well be more significant factors in your decisions. I'd just like 
>> to say that it is an experiment; we're feeling our way to what is right for 
>> this community, and so necessarily it will take a little time for things to 
>> settle down.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> Re TiddlyTalk, I don't know which is worse:  that people's posts can be 
>> edited by moderators, or that there is no clear "Terms of Use" or other 
>> indicator that posts can be edited by moderators.  I recommend that 
>> TiddlyTalk make it very clear that moderators can and do edit posts, and 
>> make it very clear what the intent and related policies are.
>>
>> BTW, it isn't about trust.  Sure I trust the moderators.  I also trust 
>> that to err is human.  We are human
>>
>> An analogy:
>>
>> Jack arrives at the pub with two black eyes, and the lads ask: "What's 
>> with the black eyes?"
>>
>> Jack points at his left one and says:  "I was at the concert in the park 
>> last night.  In front of me is a lady in a summer dress, and she has a 
>> serious wedgie, the dress right up the crack of the bum and it looks 
>> ridiculously uncomfortable.  So I decided to help her out by gently tugging 
>> on the dress at bum level to remove the wedgie.  That's when she turned 
>> around and punched me right in the left eye."
>>
>> The lads:  "Oh man.  You moron.  Why the right black eye?"
>>
>> Jack:  "When I came to, I realized that I had really upset the lady, and 
>> I felt awful about it.  So after I got up off the ground, I stuck out these 
>> three fingers with my hand like so, and poked the dress back in."
>>
>> The intentions may be good, but are they appropriate?
>>
>> Just because one can do something, should one really do it?
>>
>> And if you have given yourself the right to do something, should that 
>> right be very well indicated and should there be an opportunity for 
>> consent?  (i.e. if the user does not give consent, then user cannot join.)
>>
>> Something like that.
>>
>> On Thursday, September 16, 2021 at 9:31:57 AM UTC-3 jeremy...@gmail.com 
>> wrote:
>>
>>> Hi CJ
>>>
>>> That's correct, Google Groups allows admins to delete posts and to reply 
>>> to the author, but nothing else.

[tw5] Re: Just a Filtering Code Pattern

[Álvaro]

It works fine. I tried to find a alternative, but I wasn't lucky.

When I resee your filter, I remember about the multiple parameters in 
filter operator with commas (from last version, 5.1.23). And we can add a 
second filter run that it applies your filter to result of first run. Then 
you can rewrite your filter something like this (in filtering transclusion)
{{{  [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]  
:filter[tags[]count[]compare:eq[4]]  }}}

Although maybe it be less understandble for you.


El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2, 
jn.pierr...@gmail.com escribió:

> That's fine by me.
>
> And yes filters are fun even if sometimes a bit tricky.
>
> So for the fun of it, you could arrange your filter so that the input 
> would be the 4 tags you want.
>
> something like that:
>
> \define fun(tags)
> <$set variable=occ filter="[[$tags]put your filter code 
> here...count[]]">Seen <> tiddlers with tags $tags$
> \end
>
> Sometimes, this fun has you coding javascript filter operator. Would this 
> be the case here? I have not thought about it yet.
>
> cheers,
>
>
> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a 
> écrit :
>
>> Me and my interest in brain age games, I couldn't help but play around 
>> with a filter to find all tiddlers that have all four specified tags, but 
>> only those four tags.
>>
>> You'll find three tiddlers in the attached json.  Download the file, and 
>> drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander.
>>
>> There are all kinds of ways to go about doing this sort of thing, with 
>> some filter operators maybe better suited, but I find the result a bit 
>> easier for me to understand (more logical to me, or maybe more 
>> self-explanatory, because of the way my brain works, I suppose.)  Maybe 
>> just a difference between top-down view vs bottom-up view or something ...
>>
>> Yeah, I find filters fun.
>>
>

-- 
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/42343ad0-6a2a-4b0f-a6d6-cc975235272fn%40googlegroups.com.

[tw5] Re: implementing external image path in shiraz image-card macro?

[Álvaro]

I think that you don't "see" the following text before your cited text:
" *The advantages of the widget formulation are: "* 

I think it is easier to understand by looking at the two codeblocks: In the 
first block 2 examples with normal syntax and In the second block 3 
examples with macro call *widget*.

You have to use de widget. In your case, something like the 2nd example of 
2nd codeblock. (But you don't have to use the same indirection in a 
macrocall (widget)
<$macrocall $name="image-card" img=<>  width="" 
align="left" *...*
 

El miércoles, 1 de septiembre de 2021 a las 12:51:12 UTC+2, 
rwi...@museum.vic.gov.au escribió:

> Hi all
>
> I have been using the very handy ximg macro of Tobias Beer [
> http://tobibeer.github.io/tb5/#External%20Image%20Path]  to provide a URL 
> where my images live.  Works great, except that I now wish to use  the 
> image-card macro from the shiraz plugin for more options to display 
> images.  According to https://tiddlywiki.com/#MacroCallWidget :  
> Macro parameters are specified as widget attributes, thus allowing 
> indirection via {{title!!field}}, <> or {{{filter}}}
>
> so i have tried including <> within the standard 
> syntax  
> < title:"" text:"" footer:"" pos:"top" alt:"">> 
>
> to get
>
> <>"  width:"" align:"left" 
> caption:"" title:"" text:"" footer:"" pos:"top" alt:"">>
>
> but having tried various modifications I now surmise that nesting 
> MacroCallWidgets is not allowed.  Nor could I find this addressed in the 
> group archives
>
> No doubt the solution is dead simple but not for beginners like me.  I'd 
> be grateful for help
>
> very many thanks, Robin
>
> [I would have posted this to the new Talk Tiddlywiki discourse but I'm 
> _still_ waiting for my confirmation email to complete registration]
>
>
>
>
>

-- 
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/1407c634-e44c-4521-8f09-ca5daba3a849n%40googlegroups.com.

Re: [tw5] Re: Tw-Themes: How to keep CSS so users can still (palette) tweak?

[Álvaro]

If you change "background" to green the tiddler background take it.

El viernes, 27 de agosto de 2021 a las 20:10:26 UTC+2, flanc...@gmail.com 
escribió:

> Everything seems to be starting to come together! I noticed in the Palette 
> that background and page-background are different, what does background 
> refer to?
>
> On Friday, August 27, 2021 at 8:47:31 AM UTC-4 Finn Lancaster wrote:
>
>> Thanks @Alvaro, I’ll take a look at those. Already, the TW-primer shows 
>> up in the themes tab based on my changes on my end, I tend not to push to 
>> GitHub until the product is able to be used. 
>>
>> On Fri, Aug 27, 2021 at 7:00 AM Álvaro  wrote:
>>
>>> You can include the paltte in the theme.
>>> Here you have two examples:
>>> - Mono theme 
>>> <http://j.d.mono.tiddlyspot.com/#%24%3A%2Fthemes%2Fjd%2FMono:%24%3A%2Fthemes%2Fjd%2FMono>
>>> - Notebook theme 
>>> <https://nicolas.petton.fr/tw/notebook.html#%24%3A%2Fthemes%2Fnico%2Fnotebook>
>>>
>>> There is another point that you can see, these themes start with 
>>> *$:/themes/ 
>>> *instead of  *$:/plugins/ . *They are a kind of plugin but you will see 
>>> them in ControlPanel > Appearance > Theme 
>>>
>>> El viernes, 27 de agosto de 2021 a las 2:45:01 UTC+2, flanc...@gmail.com 
>>> escribió:
>>>
>>>> Started working on it, and already another question! It seems that I 
>>>> can't include a palette inside the theme, but instead may have to do it 
>>>> differently ???
>>>>
>>>> My palette file looks like this:
>>>>
>>>> description: Sleek dark skin for tw5, based on primer.css!
>>>> name: tw5-primer
>>>> title: $:/palettes/tw5-primer
>>>> tags: $:/tags/Palette
>>>> type: application/x-tiddler-dictionary
>>>>
>>>> And palette code here...
>>>>
>>>> Any ideas for what's going on? I'm thinking maybe the palette may have 
>>>> to be defined inside the css file??
>>>>
>>>> Thanks for your (continued) help!
>>>> On Thursday, August 26, 2021 at 7:45:47 PM UTC-4 Finn Lancaster wrote:
>>>>
>>>>> Thanks, I'll look at doing this, and hopefully not run into any more 
>>>>> issues so that I don't have to bother you anymore :)
>>>>>
>>>>> On Thursday, August 26, 2021 at 7:36:55 PM UTC-4 Álvaro wrote:
>>>>>
>>>>>> A palette is basically a data tiddler, a dictionary that stores N 
>>>>>> key:value, with type application/x-tiddler-dictionary. Then you can use 
>>>>>> it 
>>>>>> with <> where keyName can be page-background or 
>>>>>> others. 
>>>>>>
>>>>>> You don´t need change the type, that is the default type (I think). 
>>>>>> If your file has the correct tag ( $:/tags/Stylesheet ) then it 
>>>>>> works like stylesheet file.
>>>>>>
>>>>>> you can see more of what was discussed here 
>>>>>> <https://tiddlywiki.com/#colour%20Macro:%5B%5Bcolour%20Macro%5D%5D%20%5B%5Bcolour%20Macro%20(Examples)%5D%5D%20%24%3A%2Fcore%2Fmacros%2FCSS%20ContentType%20%24%3A%2Fpalettes%2FVanilla>
>>>>>>
>>>>>> Do not be scared of the number of entries in the vanilla palette, 
>>>>>> many keys reuse values, there are palettes with fewer entries. It is 
>>>>>> also something that has already been discussed about how to reduce the 
>>>>>> palettes, but it would be part of the hard rework in the styles of 
>>>>>> TiddlyWiki. 
>>>>>> El viernes, 27 de agosto de 2021 a las 0:36:14 UTC+2, 
>>>>>> strikke...@gmail.com escribió:
>>>>>>
>>>>>>> <> gives you the color number from the palette - that 
>>>>>>> will be the colour the user of your theme has chosen as the active 
>>>>>>> palette 
>>>>>>> for their use of Tiddlywiki. 
>>>>>>> Sorry but I do not know much more about the subject.
>>>>>>>
>>>>>>> On Thursday, August 26, 2021 at 11:54:48 PM UTC+2 flanc...@gmail.com 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> that seems to have worked, @strikke..., I'm guessing I have to 
>>>>>>>> include it in my theme files now, and that I can change my css to a 
>>>>>>

[tw5] Re: Tw-Themes: How to keep CSS so users can still (palette) tweak?

[Álvaro]

You can include the paltte in the theme.
Here you have two examples:
- Mono theme 
<http://j.d.mono.tiddlyspot.com/#%24%3A%2Fthemes%2Fjd%2FMono:%24%3A%2Fthemes%2Fjd%2FMono>
- Notebook theme 
<https://nicolas.petton.fr/tw/notebook.html#%24%3A%2Fthemes%2Fnico%2Fnotebook>

There is another point that you can see, these themes start with *$:/themes/ 
*instead of  *$:/plugins/ . *They are a kind of plugin but you will see 
them in ControlPanel > Appearance > Theme 

El viernes, 27 de agosto de 2021 a las 2:45:01 UTC+2, flanc...@gmail.com 
escribió:

> Started working on it, and already another question! It seems that I can't 
> include a palette inside the theme, but instead may have to do it 
> differently ???
>
> My palette file looks like this:
>
> description: Sleek dark skin for tw5, based on primer.css!
> name: tw5-primer
> title: $:/palettes/tw5-primer
> tags: $:/tags/Palette
> type: application/x-tiddler-dictionary
>
> And palette code here...
>
> Any ideas for what's going on? I'm thinking maybe the palette may have to 
> be defined inside the css file??
>
> Thanks for your (continued) help!
> On Thursday, August 26, 2021 at 7:45:47 PM UTC-4 Finn Lancaster wrote:
>
>> Thanks, I'll look at doing this, and hopefully not run into any more 
>> issues so that I don't have to bother you anymore :)
>>
>> On Thursday, August 26, 2021 at 7:36:55 PM UTC-4 Álvaro wrote:
>>
>>> A palette is basically a data tiddler, a dictionary that stores N 
>>> key:value, with type application/x-tiddler-dictionary. Then you can use it 
>>> with <> where keyName can be page-background or others. 
>>>
>>> You don´t need change the type, that is the default type (I think). If 
>>> your file has the correct tag ( $:/tags/Stylesheet ) then it works like 
>>> stylesheet file.
>>>
>>> you can see more of what was discussed here 
>>> <https://tiddlywiki.com/#colour%20Macro:%5B%5Bcolour%20Macro%5D%5D%20%5B%5Bcolour%20Macro%20(Examples)%5D%5D%20%24%3A%2Fcore%2Fmacros%2FCSS%20ContentType%20%24%3A%2Fpalettes%2FVanilla>
>>>
>>> Do not be scared of the number of entries in the vanilla palette, many 
>>> keys reuse values, there are palettes with fewer entries. It is also 
>>> something that has already been discussed about how to reduce the palettes, 
>>> but it would be part of the hard rework in the styles of TiddlyWiki. 
>>> El viernes, 27 de agosto de 2021 a las 0:36:14 UTC+2, 
>>> strikke...@gmail.com escribió:
>>>
>>>> <> gives you the color number from the palette - that will 
>>>> be the colour the user of your theme has chosen as the active palette for 
>>>> their use of Tiddlywiki. 
>>>> Sorry but I do not know much more about the subject.
>>>>
>>>> On Thursday, August 26, 2021 at 11:54:48 PM UTC+2 flanc...@gmail.com 
>>>> wrote:
>>>>
>>>>> that seems to have worked, @strikke..., I'm guessing I have to include 
>>>>> it in my theme files now, and that I can change my css to a 
>>>>> text/vnd.tiddlywiki file, so that I can call colors such as 
>>>>> <> 
>>>>> ? Is this correct to assume?
>>>>>
>>>>> On Thursday, August 26, 2021 at 5:48:02 PM UTC-4 strikke...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> Sorry if I am being stupid, but could it not be done going to 
>>>>>> $:/ControlPanel  
>>>>>> select tab Appearance and then Palette. Go to the bottom of that and 
>>>>>> click 
>>>>>> the Show editor button. That will show the selected palette. Select 
>>>>>> clone 
>>>>>> palette. Then you can edit that. You will see how it is done and can 
>>>>>> choose 
>>>>>> the colours you prefer. That is at least a start. 
>>>>>> On Thursday, August 26, 2021 at 10:27:17 PM UTC+2 flanc...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks @Alvaro,
>>>>>>>
>>>>>>> Would you mind explaining how to make a palette? This is my first 
>>>>>>> theme, but I do have some experience creating plugins, so I just need 
>>>>>>> to be 
>>>>>>> pointed in the right direction :)
>>>>>>>
>>>>>>> Thanks again!
>>>>>>>
>>>>>>> On Thursday, August 26, 2021 at 2:59:39 PM UTC-4 Álvaro w

[tw5] Re: Tw-Themes: How to keep CSS so users can still (palette) tweak?

[Álvaro]

A palette is basically a data tiddler, a dictionary that stores N 
key:value, with type application/x-tiddler-dictionary. Then you can use it 
with <> where keyName can be page-background or others. 

You don´t need change the type, that is the default type (I think). If your 
file has the correct tag ( $:/tags/Stylesheet ) then it works like 
stylesheet file.

you can see more of what was discussed here 
<https://tiddlywiki.com/#colour%20Macro:%5B%5Bcolour%20Macro%5D%5D%20%5B%5Bcolour%20Macro%20(Examples)%5D%5D%20%24%3A%2Fcore%2Fmacros%2FCSS%20ContentType%20%24%3A%2Fpalettes%2FVanilla>

Do not be scared of the number of entries in the vanilla palette, many keys 
reuse values, there are palettes with fewer entries. It is also something 
that has already been discussed about how to reduce the palettes, but it 
would be part of the hard rework in the styles of TiddlyWiki. 
El viernes, 27 de agosto de 2021 a las 0:36:14 UTC+2, strikke...@gmail.com 
escribió:

> <> gives you the color number from the palette - that will be 
> the colour the user of your theme has chosen as the active palette for 
> their use of Tiddlywiki. 
> Sorry but I do not know much more about the subject.
>
> On Thursday, August 26, 2021 at 11:54:48 PM UTC+2 flanc...@gmail.com 
> wrote:
>
>> that seems to have worked, @strikke..., I'm guessing I have to include it 
>> in my theme files now, and that I can change my css to a 
>> text/vnd.tiddlywiki file, so that I can call colors such as <> 
>> ? Is this correct to assume?
>>
>> On Thursday, August 26, 2021 at 5:48:02 PM UTC-4 strikke...@gmail.com 
>> wrote:
>>
>>>
>>>
>>> Sorry if I am being stupid, but could it not be done going to 
>>> $:/ControlPanel  
>>> select tab Appearance and then Palette. Go to the bottom of that and click 
>>> the Show editor button. That will show the selected palette. Select clone 
>>> palette. Then you can edit that. You will see how it is done and can choose 
>>> the colours you prefer. That is at least a start. 
>>> On Thursday, August 26, 2021 at 10:27:17 PM UTC+2 flanc...@gmail.com 
>>> wrote:
>>>
>>>> Thanks @Alvaro,
>>>>
>>>> Would you mind explaining how to make a palette? This is my first 
>>>> theme, but I do have some experience creating plugins, so I just need to 
>>>> be 
>>>> pointed in the right direction :)
>>>>
>>>> Thanks again!
>>>>
>>>> On Thursday, August 26, 2021 at 2:59:39 PM UTC-4 Álvaro wrote:
>>>>
>>>>> The color values from palettes are used via colour(/color) macro.
>>>>>
>>>>> How you can see in $:/themes/tiddlywiki/vanilla/base  many values of 
>>>>> some properties are direcly transclude or with macro.
>>>>> For example, the selector mentioned by you:
>>>>>
>>>>> body.tc-body {
>>>>> font-size: {{$:/themes/tiddlywiki/vanilla/metrics/fontsize}};
>>>>> line-height: {{$:/themes/tiddlywiki/vanilla/metrics/lineheight}};
>>>>> word-wrap: break-word;
>>>>> <>
>>>>> color: <>;
>>>>> *background-color: <>;*
>>>>> fill: <>;
>>>>> }
>>>>>
>>>>> You will need create a palette for your theme
>>>>> El jueves, 26 de agosto de 2021 a las 16:18:46 UTC+2, 
>>>>> flanc...@gmail.com escribió:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Recently I have been working on my tw5-primer theme, and some 
>>>>>> feedback I have gotten suggests that the theme doesn't allow palette 
>>>>>> tweaking. Testing on my own, I was able to verify it, indeed, doesn't 
>>>>>> allow 
>>>>>> this behaviour, and I have begun to fix it.
>>>>>>
>>>>>> Here is the issue: even simplifying the CSS, the theme still 
>>>>>> overrides the palette changes. For example, if I am working on .tc-body, 
>>>>>> I 
>>>>>> add the following CSS to my theme
>>>>>>
>>>>>> body.tc-body {
>>>>>>  background-color: #000;
>>>>>> }
>>>>>>
>>>>>> , which changes the background to black. However, if a user goes to 
>>>>>> change the palette, which, say, changes the background to white, it 
>>>>>> doesn't 
>>>>>> work, because the palette call of
>>>>>>
>>>>>> body.tc-body {
>>>>>>  background-color: #fff;
>>>>>> }
>>>>>>
>>>>>> is still overridden. As far as I can tell, my theme CSS cannot be 
>>>>>> simplified further to where it is not override ALL the timer.
>>>>>>
>>>>>> Is any tw dev/experienced theme-maker able to help?
>>>>>>
>>>>>

-- 
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/8a8d1f6a-49a3-46ef-b0a2-e87bd3832f52n%40googlegroups.com.

[tw5] Re: Tw-Themes: How to keep CSS so users can still (palette) tweak?

[Álvaro]

The color values from palettes are used via colour(/color) macro.

How you can see in $:/themes/tiddlywiki/vanilla/base  many values of some 
properties are direcly transclude or with macro.
For example, the selector mentioned by you:

body.tc-body {
font-size: {{$:/themes/tiddlywiki/vanilla/metrics/fontsize}};
line-height: {{$:/themes/tiddlywiki/vanilla/metrics/lineheight}};
word-wrap: break-word;
<>
color: <>;
*background-color: <>;*
fill: <>;
}

You will need create a palette for your theme
El jueves, 26 de agosto de 2021 a las 16:18:46 UTC+2, flanc...@gmail.com 
escribió:

> Hi,
>
> Recently I have been working on my tw5-primer theme, and some feedback I 
> have gotten suggests that the theme doesn't allow palette tweaking. Testing 
> on my own, I was able to verify it, indeed, doesn't allow this behaviour, 
> and I have begun to fix it.
>
> Here is the issue: even simplifying the CSS, the theme still overrides the 
> palette changes. For example, if I am working on .tc-body, I add the 
> following CSS to my theme
>
> body.tc-body {
>  background-color: #000;
> }
>
> , which changes the background to black. However, if a user goes to change 
> the palette, which, say, changes the background to white, it doesn't work, 
> because the palette call of
>
> body.tc-body {
>  background-color: #fff;
> }
>
> is still overridden. As far as I can tell, my theme CSS cannot be 
> simplified further to where it is not override ALL the timer.
>
> Is any tw dev/experienced theme-maker able to help?
>

-- 
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/b234dd1d-7513-46cb-924f-e831756e01acn%40googlegroups.com.

[tw5] Re: seeing what the transfering of tiddlywiki to a more self-coded platform can look like

[Álvaro]

I don't know if I understand you.

Tiddlywiki is easy to use but this hides its complexity. You can use it in 
two version: single file and node version. The first is like a kind of 
bundle of the second. In the Node version you can render the tiddlers as 
static files, see this link 
.
 
This is the base of other publisher like jekill. And Jeremy is working in a 
publisher for Tiddlywiky.

El viernes, 20 de agosto de 2021 a las 2:23:04 UTC+2, TW Tones escribió:

> Jamm
>
> You can do a lot with tiddlywiki macros and widgets, perhaps an infinite 
> amount without any javascript, but if you choose to build complex solutions 
> you are also using html, css and Javascript technologies which are all 
> reusable skills and essential knowledge for the internet.  
>
> I would just make sure my data in tiddlywiki was logically arranged and 
> not worry about the future its structure, technologies, tools and more all 
> allow you to move your tiddlywiki data on to other places without any 
> problems. Tiddlywiki is not a proprietary trap.
>
> Tones
> On Friday, 20 August 2021 at 07:23:05 UTC+10 jamm...@gmail.com wrote:
>
>> Thanks for clarifying, Tones and Soren. I had the impression that 
>> TiddlyWiki was more cookie cutter, or could be if I didn't add or alter 
>> code. "A no-code personal wiki system," I heard TW called. But yes, I was 
>> seeing this as a future-proofing mechanism where I might want to migrate 
>> some- or everything stored in TiddlyWiki to a different platform in the 
>> future.
>>
>> For more context, I was trying to set myself up to be able to transfer my 
>> info from a digital garden on a more cookie cutter platform to a later less 
>> cookie-cutter one, once I learned to code a bit. Starting 
>> "non-technically," in the sense Maggie Appleton's articles  impressed on 
>> me. 
>>
>> https://github.com/MaggieAppleton/digital-gardeners
>> https://maggieappleton.com/nontechnical-gardening
>>
>> It seems I still misunderstand the question of going from a manageable 
>> Digital Garden to a more complex one, not having data transfer be an issue.
>> On Thursday, August 19, 2021 at 8:36:03 AM UTC-4 Soren Bjornstad wrote:
>>
>>> As Tones said, I think we need a bit more information about what you're 
>>> hoping to accomplish to give a complete answer. Are you seeing this as a 
>>> future-proofing mechanism where you *might* want to migrate something 
>>> stored in TiddlyWiki to a different platform in the future? Or you want to 
>>> use TiddlyWiki as a CMS and then publish using a different tool? Or 
>>> something else?
>>>
>>> On a straightforward level, it's possible to quickly render some or all 
>>> tiddlers to HTML, at which point you can post-process them using whatever 
>>> tooling you want. I've been using this to crosspost my sabbatical updates 
>>> from my Zettelkasten 
>>>  to my 
>>> Jekyll blog 
>>> , 
>>> using the following rule in my Makefile:
>>>
>>> sabbatical_updates := $(wildcard 
>>> zettelkasten_dir/tiddlers/SabbaticalUpdate*)
>>> sabbatical_files: $(sabbatical_updates)
>>> rm -rf /tmp/twout
>>> cd $(zettelkasten_dir) && tiddlywiki --output /tmp/twout --render 
>>> "[prefix[SabbaticalUpdate/]]" "[is[tiddler]addsuffix[.html]]" "text/html" 
>>> '$$:/sib/Templates/Export/SabbaticalUpdateCabCrosspost'
>>> python3 automation/crosspost-sabbatical-updates.py 
>>> /tmp/twout/SabbaticalUpdate/*
>>>
>>> The Python script is about 70 lines and primarily sets up a YAML header 
>>> with appropriate metadata so Jekyll understands what to do with the post. 
>>> This is also the purpose of the 
>>> $:/sib/Templates/Export/SabbaticalUpdateCabCrosspost template -- it embeds 
>>> certain fields in the HTML where this script can retrieve it. If you 
>>> preferred, I think you could use pandoc at this point to convert back to 
>>> Markdown or a similar format; since I'm keeping my source of record in 
>>> TiddlyWiki, I'm fine just leaving the posts as HTML in Jekyll.
>>>
>>> Of course, if you take advantage of dynamic features of TiddlyWiki that 
>>> can't be represented as HTML with 100% fidelity, e.g. dynamic lists based 
>>> on filters or displays of backlinks, you'll end up losing some 
>>> functionality when you do this.
>>>
>>> On Wednesday, August 18, 2021 at 2:31:10 PM UTC-5 jamm...@gmail.com 
>>> wrote:
>>>
 I'm looking to see what the transfering of tiddlywiki to a more 
 self-coded platform, such as jekyll, gatsby, or others, can look like. My 
 concern is the transition being difficult, long, etc. Any resources?

>>>

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

[tw5] Re: !!! ''foo'' does not appear as bold

[Álvaro]

It is a problem with font-weight that it fixed in the prerelease, the fix 

the heading elements have a font-weight of 300 and the ** element 
has font-weight bolder.
The bolder of 300 is 400 (=normal)
You can see the specification about this property here 


El lunes, 16 de agosto de 2021 a las 14:47:50 UTC+2, TW Tones escribió:

> Can you give an example?
>
> This works;
>
>  This is a heading with ''bold'' in it
>
> Tones
>
> On Saturday, 14 August 2021 at 20:03:47 UTC+10 Sapphireslinger wrote:
>
>> The heading wikitext cancels out the bold wikitext.
>>
>> I went to the control panel and looked through the palette editor but 
>> couldn't find anything to edit to keep the H1 and H2  and H3 (etc) buttons 
>> from interfering with the bold formatting. 
>>
>> I am using Vanilla theme.
>>
>> Thank you for any tips.
>>
>

-- 
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/6640865d-9be6-42d1-b3a9-cfa200f0b107n%40googlegroups.com.

Re: [tw5] Re: Just the UI of tiddlywiki

[Álvaro]

Joshua, there is the Fluid framework for collaborative web applications. 
Although you surely know it. https://github.com/microsoft/FluidFramework

El lunes, 19 de julio de 2021 a las 18:53:50 UTC+2, Stobot escribió:

> I'm excited to hear about any new efforts on multi-user Joshua! I'm sure 
> very hard, but game changing functionality for team TiddlyWiki usage!! I 
> continue to try and use BOB for this, but the reconnect process is so 
> spotty that it's difficult to get traction. 
>
> On Monday, July 19, 2021 at 7:14:25 AM UTC-4 ludwa6 wrote:
>
>> Hard problem indeed, @Joshua, in domains where there needs be one 
>> definitive source of truth... But in any problem space where there is room 
>> for different versions of truth (the case in many applications of TW tech), 
>> perhaps it needn't be so hard?  
>>
>> Without knowing which sub-species of the multiplayer problem you are busy 
>> solving, i will say that i for one am these days more interested in the 
>> problem-space where different versions of truth are respected & included 
>> (or TRANScluded, as the case may be) than i am in the space where one 
>> version must win out over all others.  
>>
>> For example: ii think Ward Cunningham was wise to sidestep all that 
>> backstage ugliness of Wikipedia's "Consensus Engine" in developing his 
>> Smallest 
>> Federated Wiki 
>> model.  
>> (THAT in fact is my dream for how this TW multiverse eventually develops 
>> some navigable wormholes between its many dimensions <8-)
>>
>> /walt
>>
>> On Monday, July 19, 2021 at 4:24:00 AM UTC+1 joshua@gmail.com wrote:
>>
>>> I am getting very close to a "multiplayer" solution. It's definitely one 
>>> of the "Hard Problems": 
>>> https://gigaom.com/2009/05/10/why-sync-is-so-difficult/
>>>
>>> Best,
>>> Joshua Fontany
>>>
>>> On Friday, July 16, 2021 at 5:59:57 AM UTC-7 ludwa6 wrote:
>>>
 @PMario: just to say thanks (again!) for sharing another treasure of 
 the TW world -TiddlyWeb API Explorer 
  in this case. 
 As per my post to this other thread 
 ,  it opened my 
 eyes to the possibility of an OpenAPI Explorer in TW -and i'd love to know 
 what you think about that, either in that other thread or via DM (this 
 one's really not about that).

 On this topic, i can only say: i share Xavier's interest in the idea of 
 connecting TW as front end to a backend server with muli-user / multi-edit 
 capability.  Of course that old problem of edit conflict avoidance/ 
 resolution would need to be solved, but i have trouble accepting that as a 
 real stopper in this day -although from what i gather (from email 
 exchange with dev Chris Dent), TiddlyWeb is not likely to be the place 
 where such functionality will emerge.   If there be some other place to 
 look for solutions, it'd be great if someone could share info about that 
 here!

 /walt


 On Wednesday, July 14, 2021 at 1:51:49 PM UTC+1 PMario wrote:

> On Wednesday, July 14, 2021 at 1:38:46 PM UTC+2 somen...@gmail.com 
> wrote:
> ...
>
>> I will look into the code but it's a pitty to be TW2. Perhaps someone 
>> could point to me where is the code of the UI in the code of official 
>> tiddlywiki5. 
>>
>
> Hi Xavier,
>
> I think there is a bit of a misunderstanding how TiddlyWiki works. ... 
> TiddlyWiki is a self-contained single file wiki. ... No server is needed 
> other than for serving a 
> single file resource. 
>
> TLDR;
> I think it would be good, if you explain a bit closer what you want to 
> do. 
>
> --
>
> If you open tiddlywiki.com it's served from a github page as a single 
> 6MByte index.html file. ... Since github does server side compression 
> only 
> about 2Mbyte are sent to the client. 
>
> Everything you see UI wise is rendered on the client. ... It would be 
> the same experience if I would send you myWiki.hmtl by e-mail. 
>
> If I "permalink" to eg: https://tiddlywiki.com/#HelloThere  the 
> browser will open the HelloThere tiddler, because the whole content is 
> already in the client. No server is involved, the core code "catches" the 
> URI fragment and displays the tiddler.
>
> -
>
> A TiddlyWeb server will also "only" create a single resource if you 
> request https: //your-uri/index.html ... It will build the html file 
> server 
> side and send it as 1 file, that contains code, UI and data to the 
> client. 
>
> The advantage of TiddlyWeb is, that you also have some API routes that 
> will let you request recipes, bags and single tiddlers, without any TW UI 
> as text or JSON. There is a 

[tw5] Re: How to make a default field for a new record?

[Álvaro]

Yes, you are right. I thought in the my usual way to create new records, I 
don't usualy use new journal or new image.

Then we can use a hack in $:/core/ui/EditTemplate/fields which displays a 
fake(/"empty") url field, we don't have a real url field until you type and 
save its value.

The hack would be:




<$list filter="[all[current]fields[]] +[sort[title]]" 
variable="currentField" storyview="pop">
to
<$list filter="[all[current]fields[]] *[[url]]* +[sort[title]]" 
variable="currentField" storyview="pop"> 


El viernes, 16 de julio de 2021 a las 6:04:57 UTC+2, Eric Shulman escribió:

> On Thursday, July 15, 2021 at 6:25:29 PM UTC-7 Álvaro wrote:
>
>> Yes, because I focused on explaining the problem. The base of the 
>> solution is  *<$action-sendmessage $message="tm-new-tiddler" url="" />*
>>
> The hard version is modifing the action-sendmessage in the tiddler 
>> *$:/core/ui/Actions/new-tiddler*
>> *<$action-sendmessage $message="tm-new-tiddler" tags=<>/>*
>> to
>> *<$action-sendmessage $message="tm-new-tiddler" tags=<> 
>> url=""/>*
>>
>
> Once again, I have to point out that this only changes the behavior of the 
> "New Tiddler" button and *does not fully address the OP goal* *(*"*the 
> url field to be always visible from the start for all new records.")*
>
> There are *at least 6 other ways* to interactively create another tiddler:
> * New Journal in the Sidebar
> * New Image in the Sidebar
> * New Here in the Tiddler Menu
> * New Journal Here in the Tiddler Menu
> * Follow a link to a missing tiddler, and then edit that tiddler
> * Any 3rd-party plugin or hand-written custom wikitext that contains a 
> $button using "tm-new-tiddler", 
>
> The only solution that handles all these cases (and any others that I 
> haven't thought of at the moment) is to modify the EditTemplate as 
> suggested by Brian Radspinner, with the small UI improvements suggested by 
> me to remove the duplicate appearance of the "url" field, position it above 
> the "create new field" interface in the tiddler editor, and enable use of 
> $:/config/EditTemplateFields/Visibility/URL
>
> respectfully,
> -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/e7ee0c28-6063-4c69-be21-e277ef7eee2en%40googlegroups.com.

[tw5] Re: How to make a default field for a new record?

[Álvaro]

Yes, because I focused on explaining the problem. The base of the solution 
is  *<$action-sendmessage $message="tm-new-tiddler" url="" />* 

The hard version is modifing the action-sendmessage in the tiddler 
*$:/core/ui/Actions/new-tiddler 
*
*<$action-sendmessage $message="tm-new-tiddler" tags=<>/>*
to
*<$action-sendmessage $message="tm-new-tiddler" tags=<> url=""/>*


El viernes, 16 de julio de 2021 a las 2:20:09 UTC+2, Eric Shulman escribió:

> On Thursday, July 15, 2021 at 5:00:33 PM UTC-7 Álvaro wrote:
>
>> I talk about two options: template tiddler or second action for create 
>> the url field, but there is a easier way:
>>
>
> While your $button definition works, it doesn't meet the goals of the OP.  
> Specifically: *I want the "url" field to be always visible from the start 
> for all new records. Can I add something to the system so that it always 
> appears on its own?  *The $button solution doesn't address the *other* 
> ways you can create a new tiddler, such as using the sidebar "New Tiddler" 
> button, or clicking on a link to a missing tiddler and then editing that 
> tiddler.  Only the EditTemplate solution will provide this behavior for 
> *all* interactive methods of creating new tiddlers.
>
> -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/c4f853bd-46b7-4f6e-a8e6-89ff5a7ba77an%40googlegroups.com.

[tw5] Re: How to make a default field for a new record?

[Álvaro]

Because you don't have a url field when you create with buttons with the 
basic "tm-new-tiddler". The created tiddlers have the tags field, but it 
doesn't have this url field, then it can't be displayed.

Only the usual fields (tags, title, text, ...) have this setting ( 
*$:/config/EditTemplateFields/Visibility/FIELD_NAME* ) by default.

For this you need that your button creates the url field. I talk about two 
options: template tiddler ord second action for create the url field, but 
there is a easier way:




*<$button><$action-sendmessage $message="tm-new-tiddler" url="" />New 
Tiddler with url field*

El viernes, 16 de julio de 2021 a las 0:43:07 UTC+2, Eric Shulman escribió:

> On Thursday, July 15, 2021 at 3:05:36 PM UTC-7 miket...@gmail.com wrote:
>
>> Brian, yes, but it looks bad and that's what I want to avoid.
>> https://i.imgur.com/Amptssc.jpg
>>
>
> The first problem is that the URL field will appear twice when the field 
> has a value:
> * once because it exists as a field in the current tiddler
> * and again because the input is tagged as $:/tags/EditTemplate 
>
> To fix this, you can wrap the URL EditTemplate definition in a $list 
> widget, like this:
> <$list filter="[!has:field[url]]" variable="no_url">
> 
> 
> 
> 
> url
> <$edit-text field="url" default="" 
> tag="input"/>
> 
> 
> 
> 
> 
>
> The second problem is that the custom URL EditTemplate definition is 
> placed *after* the "add new field" controls.
>
> To fix this, you can move the custom URL EditTemplate above the "add new 
> field" controls:
> * From the URL EditTemplate tiddler view, click on the 
> "$:/tags/EditTemplate" tag pill
> * In the list of EditTemplate definitions, drag-and-drop to move the URL 
> EditTemplate above "$:/core/ui/EditTemplate/fields"
>  
>
>> I can make the *tags *field visible right away 
>> *$:/config/EditTemplateFields/Visibility/tags*, why can't I do the same 
>> with the *url *field?
>>
>
> You can.  Add another $list widget wrapper to the URL EditTemplate 
> definition, like this:
> <$list filter="[[$:/config/EditTemplateFields/Visibility/URL]!text[hide]]" 
> variable="hide_url">
> <$list filter="[!has:field[url]]" variable="no_url">
> 
> 
> 
> 
> url
> <$edit-text field="url" default="" 
> tag="input"/>
> 
> 
> 
> 
> 
> 
>
> By default, the URL field will be shown.  If you want to hide the URL 
> field,
> just create a tiddler named *$:/config/EditTemplateFields/Visibility/URL *
> and set it's text field content to "hide"
>
> 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/2e810cf2-39ac-4cc7-b571-33eb5c1b895fn%40googlegroups.com.

[tw5] Re: How to make a default field for a new record?

[Álvaro]

I don't know if I understand you.
When you create a new (default) tiddler, it has the default fields. You can 
see them in the info panel (except the text field).

Then you can:
- Create a new tiddler and then add the url field (tm-add-field)
- Create a new tiddler from template tiddler (with url field)

El jueves, 15 de julio de 2021 a las 18:33:16 UTC+2, Brian Radspinner 
escribió:

> Try adding the following code to a new tiddler tagged with 
> "$:/tags/EditTemplate"
>
> 
> 
> 
> 
> url
> <$edit-text field="url" default="" 
> tag="input"/>
> 
> 
> 
> 
>
> This will put a table styled like the other fields list with the URL field 
> showing in the tiddler editor. 
>
>
> On Thursday, July 15, 2021 at 9:00:22 AM UTC-7 miket...@gmail.com wrote:
>
>> I want the "url" field to be always visible from the start for all new 
>> records. Can I add something to the system so that it always appears on its 
>> own?
>>
>> $:/config/EditTemplateFields/Visibility/url ?? 
>>
>> I already know about custom buttons "tm-new-tiddler", about templates 
>> param=, about $:/tags/EditTemplate
>> But all this requires additional actions one way or another.
>> I want everything to be as simple as it is now, only with the url field)
>>
>

-- 
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/389f9733-d0d8-422a-bb27-20d4bbfc744bn%40googlegroups.com.

[tw5] Re: Elements > Styles - All Classes are color black

[Álvaro]

I don't know if I understand you.

What is it a element (for you)? What is a "selected element"?

You are look in the Styles (CSS) there you see the applyed rules to a HTML 
element . You 
can find here  a 
basic explain of CSS and the parts of a rule. Only the overwrtiten 
declarations will be grayed out, not the selectors (¿yours elements?) used 
in the rules. 

El miércoles, 7 de julio de 2021 a las 8:00:03 UTC+2, TW Tones escribió:

> Janmarc,
>
>  A little more explanation of your images and details may help. TW5 
> Version, any particular themes, or dark mode active etc...
>
> I see in the image "#ff!importiant;" I would search for this if 
> possible in the wiki. Even in a text editor if unreadable in the browser.
>
> They say "avoid the use of the CSS important at all costs", perhaps this 
> is an example of why.
>
> If you have a custom stylesheet or two disable them by removing the 
> stylesheet tag. backup, but you can search for the tag and rename it in the 
> text file on custom tiddlers.
>
> There is more we can help with but way more info can come from you.
>
> Tones
>
> On Wednesday, 7 July 2021 at 13:06:00 UTC+10 janmarcqu...@gmail.com wrote:
>
>> Have you encountered this on your chrome? All the elements are black even 
>> they are not selected. It should be grayed out when the elements is not 
>> selected. I'm having hard time to do my styling. I tried to 
>> uninstall/reinstall, removed data, cookies, history and extensions, but 
>> still getting that issue.
>>
>>
>>

-- 
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/2695b089-2667-4afb-92fc-dc41bab53f82n%40googlegroups.com.

Re: [tw5] [Help] Color them icons and buttons.

[Álvaro]

Hi Tones

I think that the following CSS (in StyleSheet tiddler) could work for you 

.tc-tiddler-controls button svg{fill: inherit;}
.tc-tiddler-controls button{fill: <>;}


El jueves, 20 de mayo de 2021 a las 21:15:26 UTC+2, TiddlyTweeter escribió:

> Ciao Tones
>
> You may want to engage in discussion at 
> https://github.com/morosanuae/tw-icons/discussions
>
> Slowly we are beginning to work through multiple issues on SVG 
> opportunities opened up by  Morosanuae's TW Icons initiative ...
>
> I am myself particularly interested in understanding the of styling Icons 
> ...
>
> [image: Screenshot 2021-05-20 203000.jpg]
> Best wishes
> TT
>
> On Thursday, 20 May 2021 at 00:55:07 UTC+2 TW Tones wrote:
>
>> Heree is a simple example of how quickly coloring a button is confounded
>>
>> \define colour() #f00
>> <$button>
>> addsuffix[;]] 
>> }}}>{{$:/core/images/spiral}}
>> 
>>
>> in a tiddler tagged $:/tags/ViewToolbar all custom color is lost.
>>
>> Tones
>>
>

-- 
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/825cc35b-5205-42c0-88d6-4fa009838cc7n%40googlegroups.com.

[tw5] Re: Design trick discover classes and CSS in use?

[Álvaro]

TW Tones

I don't know if I am not understanding you, vice versa or both aren't 
understanding the other.

What is the standart CSS element in TW?

I agree If you talk about a explaining The CSS of general layout of TW. But 
in the decorative aspect, I think is more complex and hard to mantain due 
to a element can use different selectors and classes.

El jueves, 27 de mayo de 2021 a las 13:09:49 UTC+2, Stobot escribió:

> Tones, for what it's worth, I agree with a lot of things you're saying. At 
> my present state of learning TiddlyWiki (many years in the process now), 
> CSS & TiddlyWiki classes are one of the last frontiers for me, and probably 
> because there's no easy starting point. I'm not calling this out as a fault 
> of TiddlyWiki to be clear - just an opportunity to bring out / generate 
> more palette and layout developers! It strikes me that there's now a layout 
> chooser in the standard control panel, but no options yet. With my own 
> project of a layout that would be familiar to people who use Office every 
> day, it's been a struggle figuring that out, which makes me wonder what 
> we'd get from the user population if that were easier!
>
> I also however agree with others that building something going to explain 
> *everything* is probably too far, so in my head there's a dividing factor 
> where something could be provided by going part of the way, and leaving the 
> browser developer tools to go the rest of the way. If that sounds like a 
> "cop out", I'd suggest we're already there. For example as has been pointed 
> out, there's StoryTop and StoryLeft as tiddlers, but setting those to 0 
> doesn't actually move the story all the way to the top or left due to other 
> classes unknown. 
>
> You (Tones) may be focused on other parts like formatting colors etc. but 
> my own interest has primarily been positioning and layout as I'm sure is 
> evident :)  One thing on my todo list was to have a 1-page reference sheet 
> of all of the main classes I was able to deduce regarding layout. Showing a 
> picture of the whole standard screen layout, and marking the class or 
> tiddler that controls each of the spacing. Seems like most of the spacing 
> settings are all in the tc- .padding / .margin namespace. I have no way 
> of knowing how many of these tc- classes there are in regards to 
> layout, but if there are a limited number, this may still be doable. R 
> language for instance does a lot of their core documentation on these 
> 1-page printable pages (Cheatsheets) which are really handy. We could 
> produce something similar as a visual reference. RStudio Cheatsheets - 
> RStudio 
>
> Lastly just as commentary, my own (very possibly inaccurate) feel from 
> watching this community over many years is that most of the experts here 
> came in with some web development background first, and then are trying to 
> learn, and develop just about how TiddlyWiki does things. I conversely come 
> from nearly the opposite background of having played with TiddlyWiki and 
> other low-code programming languages for a long time, can make really 
> useful and powerful things (I build business apps for my corporation on the 
> side), but struggle the most on changing the look and feel. If I reflect, I 
> guess I interpret things that way because when the question is around say 
> generating a list of things, we see really great, detailed walkthroughs of 
> how it works, watchouts, step by step answers which are awesome, but to 
> your point Tones, when it's a formatting question, the answer is more like 
> - "It's easy, just use CSS!" or pointing to some other highly-customized 
> wiki somebody else has made. The implication is that we already know how to 
> reverse-engineer css and the TiddlyWiki classes. Again, not criticizing in 
> the slightest - we're all here voluntarily, just an observation that I feel 
> like I'm coming from a minority perspective. 
>
> On Thursday, May 27, 2021 at 4:08:47 AM UTC-4 TiddlyTweeter wrote:
>
>> TW Tones
>>
>> I think it would be pretty easy to provide a LIVE HIGHLIGHT tool that 
>> dynamically shows CSS in action in the wiki?
>> (For instance giving a coloured border to different div elements)?
>>
>> That might clarify the issues somewhat in a practical way?
>>
>> Thoughts
>> 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/d38b9507-29bc-4400-83ad-6520b374bdb3n%40googlegroups.com.

Re: [tw5] TiddlyWiki Documentation - Syntax

[Álvaro]

Thanks for the iniciative and the work.

- I think that put only name attribute could be confused for newcomers. 
They can think that widgets work like a macro, when (I think that) the 
widget works like a html tag.
- I am rethinking the idea of create a syntax example for each widget or 
macro. Maybe it is better try to do it in the widget documentation, in the 
tiddler *Widgets in WikiText*, and then create a line in each widget 
linking this tiddler. And the point "Widget attributes can be specified as:" 
will be more helpful. 

My idea would look something like this (Using some doc macro), but I was 
thinking in macros. 
\define tag-init() <
\define tag-end() >

<><<.wid Mywidget>> ''attribute1''="value1" 
//attribute1//="value1"<>
CONTENT
<>/<<.wid Mywidget>><>

But it doesn't look good (in color-contrast) in the name of widget/macro. 
And i don't know if it is cofused or not, maybe I need apply the style to 
all string of attribute ( attributeX="valueX"). Or Maybe we don't need if 
we use a table with column "type" as use Mohammad in their macros.
El jueves, 27 de mayo de 2021 a las 8:56:35 UTC+2, TiddlyTweeter escribió:

> Mohammad wrote:
>
>> I have attached a sample doc from Excel
>>
>> The same sequence: purpose, syntax, arguments (in/out parameters), 
>> remarks, examples
>>
>
> [image: Screenshot 2021-05-27 085252.jpg] 
>
> Ha. Very good example!
>
> And, YES. We are all Sinners, and especially Microsoft :-)
>
> 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/c0430e88-6358-4cdb-83fd-f401f73c83b3n%40googlegroups.com.

Re: [tw5] CSS / Single Page Layout / Hidden Classes

[Álvaro]

In your browser you have a excellent tool for it. Here 
 they explains how use it 
in chrome, it is similar in other browsers.

In the second panel with tab "Styles" (active) you can see the list of 
rules applied to the element. Those above overwrite the previous/below 
ones. The first is "element.style" and it refers to inline styles (when you 
give styles directly inside the html, without CSS). But you only need see 
where the padding/margin are applied to find the class (or selector). 
El miércoles, 26 de mayo de 2021 a las 12:33:40 UTC+2, Stobot escribió:

> Thanks Arunn, I can see some similarities in desired output there, so 
> thanks for passing along that link. At first glance though it looks like 
> I'm already in a similar place - with extra (for my purposes anyways) 
> spacing on the left and right
>
> My hope is that someone who's done this kind of thing before would say 
> something like - "For A, add a class for 'tc-tiddler-top-padding" and 
> change it to 0px to get rid of it" or something like that. 
>
> On Wednesday, May 26, 2021 at 2:14:37 AM UTC-4 arunn...@gmail.com wrote:
>
>> https://ibnishak.github.io/Timimi/
>>
>>  Will this be of any help?
>>
>>
>> On Wed, May 26, 2021 at 5:48 AM Stobot  wrote:
>>
>>> One of my side projects is to make a "version/edition" for my other 
>>> "corporate" folk who are used to things looking like programs they're used 
>>> to - primarily Microsoft (Teams / PowerBI / Office Online). There is a very 
>>> common pattern with a top bar, left bar, and then the documentation is 
>>> single page mode. 
>>>
>>> I've been able to get a leftbar and topbar started and starting to be 
>>> populated (far from done, but mostly know how to do the rest). I also 
>>> figured out the sticky-titles and z-index to layer things okay. I am stuck 
>>> on spacing (as I typically am) as I don't have a web/css background or know 
>>> all of the "hidden classes". If there's a good resource/guide for me to 
>>> self-teach, even better! 
>>>
>>> In the "before" picture, I have 5 red boxes I'm trying to reduce to get 
>>> me to the "after" picture. 
>>> A: I already have "story top" set to 0px, there's just extra padding 
>>> above the title line
>>> B: I can adjust this with "story left", so I don't really need help on 
>>> this one
>>> C: I think similar to A, there's got to be some tc-? that I can change 
>>> padding-left?
>>> D: Same as C, but on the right
>>> E: There's additional spacing to the right of the tiddler I can't get 
>>> rid of.
>>> Bonus: I think I'll keep it single-page mode, but if anyone knows how to 
>>> adjust the space between tiddlers, that'd be helpful too as I might expand 
>>> that way.
>>>
>>> Before (purposely put topbar in the back to illustrate better):
>>> [image: before.png]
>>>
>>> After:
>>> [image: after.png]
>>>
>>> *Thanks to the many contributors who've I've learned from to get this 
>>> far with the CSS I have learned - especially Ton Gerner / J.D. / David 
>>> Gifford / Eric / Soren / Jeremy and many others :)*
>>>
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/f0cb9894-9b58-4484-b6a3-4b07f0899832n%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/03e0d5bb-b769-40e4-9682-9084f294e7d2n%40googlegroups.com.

[tw5] Re: Design trick discover classes and CSS in use?

[Álvaro]

 
*Ideally all the standard css elements in a tiddlywiki would be documented.*

I don't understand it. ¿standard css elements? CSS is the tool and its use 
in TW is another way to use it. This use is shown in the style tag, in the 
case of TW. I agree that look in styles is tedious. It is easier use the 
inspector. But, IMHO, the problem isn't in the non-documentation, it is in 
its size. The CSS would need a hard reworked with great refactor. 
El miércoles, 26 de mayo de 2021 a las 3:14:33 UTC+2, TW Tones escribió:

> Gentlemen,
>
> Ideally all the standard css elements in a tiddlywiki would be documented. 
> eg I want to change the background of the tiddler title, the text color, 
> the icon . Many are documented in a defacto way in the palette settings. 
> you can see the class name that is set, but many elements are not. even 
> although one could say they are "hard coded" in tiddlywiki ie Tiddlywiki 
> has a whole set of classes for various elements on the screen, where are 
> they?
>
> Every time someone is looking we tell them (if we know) we use inspect and 
> find it for them, but its an an element at a time. What ever the answer I 
> want to improve this.
>
> I can imagine a custom edition of tiddlywiki (or content in a tiddler) in 
> which mouse over any element has A popup documenting the css used to style 
> the element would be a nice addition to the documentation.
>
> Jon - *Are talking here only about users who want to experiment with CSS 
> but are guaranteed never to want to progress past a certain point?*
> No, what we need to do document what tiddlywiki does and peoples hunger 
> for learning will prosper if it is not such a chore.
>
> Tones
> On Tuesday, 25 May 2021 at 23:28:41 UTC+10 jonligh...@gmail.com wrote:
>
>> Hi,
>>
>> I have used Mozilla developer tools for ages and have been using them to 
>> write my own custom CSS to over-ride defaults in Tiddlywiki.
>>
>> As soon as you get to CSS an informative tool needs to reflect the 
>> cascade otherwise it is not of much use and will probably frustrate users 
>> who do not 
>> understand the cascade and doggedly poke away unsure why their custom CSS 
>> is apparently being ignored - a simple version of a tool that does not
>> tell the whole story can possibly do more harm than good?
>>
>> In addition being able to click on a declaration and see where it was 
>> defined by which CSS file is very useful as is being able to test 
>> alternative values 
>> 'in browser' with those effects being blown away  as soon as you refresh 
>> is a great asset. I usually work out my proposed changes by this method 
>> before 
>> changing any real CSS files or tiddlers. 
>>
>> Unless browser developers expose the API for the code that interprets the 
>> CSS cascade and is able to display it within  their own developer tools 
>> then would it be 
>> necessary to write a CSS processor for this project with the inevitable 
>> updates and revisions on account of inevitable  discrepancies  with CSS 
>> standards 
>> and developments in CSS? 
>>
>> I assume that the Mozilla team work hard on developer tools - so I am 
>> guessing a lot of catch up unless large chunks of functionality are 
>> available open source, even
>> if catch up is possible then whats to guarantee an easier or more 
>> intuitive tool? Presumably the Mozilla ( or whatever browser ) developers 
>> are reasonably proficient at
>> usability and have done a reasonable job?
>>
>> I am dubious regards the value of a lesser tool for users who are open to 
>> the idea of learning more - eventually they may start asking for the 
>> sophistication of browser
>> developer tools and those are already available.  
>>
>> Are talking here only about users who want to experiment with CSS but are 
>> guaranteed never to want to progress past a certain point? 
>>
>> I guess you always run this risk when you develop a cut down  or 
>> simplified version of something that is already 'out there' - what 
>> parameters on project scope 
>> are to be put in place to ensure that the final product after much work 
>> is actually "wheel number 2" - project scope creep ? 
>>
>> Sorry to sound negative :-) 
>> On Tuesday, 25 May 2021 at 09:44:39 UTC+1 TiddlyTweeter wrote:
>>
>>> TW Tones wrote:
>>>
 ... Using the ... plugin Internals allows you to preview the html 
 generated inside a tiddler ...

>>>
>>> Right! 
>>>
>>> FYI I often use its as a quick way to copy and paste compliant HTML into 
>>> online discussions that will take raw HTML.
>>>
>>> It makes me think what if we provide some alternate tools to do the same 
 thing so we can see other elements of the whole page in rendered html as 
 insight.

>>>
>>> One aspect that I'm NOT sure any TW tool could do is show "Shadow DOM"? 
>>> I.E. stuff that you can see on-screen but is NOT in the HTML render code.
>>> That includes, for example, things that CSS can insert---and that can be 
>>> quite a lot (for instance: any CSS 

[tw5] Re: Filter operators: Official documentation

[Álvaro]

 I agree, it is confusing especially if you don´t know/remember the filter 
sintax, in this case the filter steps. And how you say input is confusing 
if you don't know/remember that this input is the output of other filter 
step (or filter run). If i don't understand bad the list of titles between 
square bracket is a step. I like the idea the "constructor example" in a 
list (or in filtering transclusión), I don't know if it is better do it 
with styles in font or in a table. I think that also differenciate the 
parts of constructor, necessary vs optional.

Also i agree with Stobot. "Example constructor" will be good point. I think 
also it happens with macro docs (for example in "toc" macro). I working in 
a macro and i doubt how write the optional parameters to do understandable 
to everyone.

TiddlyTweeter, I agree with you in that brevety is good, but with some 
reminders it would be better and not much longer.
El martes, 25 de mayo de 2021 a las 14:24:58 UTC+2, TiddlyTweeter escribió:

> Ciao Mohammad
>
> It is an interesting issue. 
>
>- I AGREE the base docs are not enough for working everything out. 
>
>
>- I DISAGREE that the solution to that problem should be in the main 
>documentation!
>
> WHY? 
>
> Because *IF *you added all possible combination examples it would inflate 
> the main reference site, tiddlywiki.com, to be SO vast it would become 
> unusable.
>
> IMO, Jeremy Ruston has done a very good job on documentation. 
>
> It is true his style is somewhat gnostic :-)
> The original minimalist! :-) 
> But it is also true that he has ASTUTE BREVITY.
>
> IMO this issue should be about SECONDARY documentation.
>
> At the moment everything focuses on tw.com. 
> I'm NOT convinced that is the right approach for final practical, fully 
> expanded, documentation.
>
> It seems to me that we need more DIFFERENTIATION.
> AND recognizing better SUPPLEMENTARY documentation that covers specific 
> aspects of TiddlyWiki in more detail would be best.
>
> I hope my points make sense, even if you don't agree.
> 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/6392aca0-770a-4ccc-9d3c-42f503e68d88n%40googlegroups.com.

[tw5] Re: [Help] Color them icons and buttons.

[Álvaro]

If the problem is in direct rule of svg ,that they are inside the tiddler 
controls, and it overwrite the inherited style. We can solve 
removing(/changing) de direct rule or declaration, or we solve playing with 
selector’s specificity, for example if we apply class or inline style in 
the svg tag.

You have to think in "how many color am I going to add?" "Will i reuse 
them? Or will i going to add different color each time?". If you look in 
the CSS framework (tailwind, bootstrap,...), they have clases for a numbers 
of colors and then they are reused.

The user customization is there. Yes, it is possible have a easier user 
customization but it requires a hard rework in the CSS.


P.S. I think that the following article could be helpful about these CSS 
"problems" 
https://www.smashingmagazine.com/2010/04/css-specificity-and-inheritance/
El miércoles, 19 de mayo de 2021 a las 0:46:25 UTC+2, TW Tones escribió:

> Álvaro,
>
> Thanks - I am now getting closer to a full understanding of this. In this 
> case I have the color value available in a variable or field value, I 
> wanted to find a way to pass the color to the button display 
> "programaticaly".
>
>- It supports my suspicion that button css is not as hackable as you 
>would expect from tiddlywiki, making this a harder than average to 
>customise this aspect of the User Interface, while making use of the CSS 
> to 
>define a button in the view toolbar (and elsewhere)
>
>
> Ideally the tiddlywiki designer can just supply a hex or named color, 
> rather than a need to define a range of classes (colors).
>
> Perhaps there is an argument that the tiddlywiki toolbar buttons css need 
> to be change to permit a programaticaly set color to be provided 
> (optionally). 
>
> Álvaro, can you think of a way to open this to user customisation? I think 
> it is important enough to consider some changes. 
>
> Regards
> Tones
>
> On Wednesday, 19 May 2021 at 03:25:50 UTC+10 Álvaro wrote:
>
>> The svg has two styles, one the inherited fron inline style in span and 
>> "direct rules" (*.tc-tiddler-controls button svg* ). When you apply 
>> direct rules the inherited rules are gone (they are overwritten by 
>> direct). You can see it in the inspector of your browser, "fill:red" is 
>> strikethrough.
>>
>> You need add inline style in svg or add new class, for example in button.
>> button.icon-blue svg{fill:blue;}
>>
>> and use it like
>> ...
>> <$button message="tm-add-tag" param="$tag$" tooltip="Toggle $tag$"  
>> class="tc-btn-invisible icon-blue">
>> <$transclude tiddler="$:/PSaT/check-tag/button/checked-icon" />
>> 
>> ...
>>
>> Then you don't need wikify and you have a reusable style for the icon in 
>> buttons. You can change/add class dynamically to button like tiddlywiki 
>> does with varible and filter in *$:/core/ui/ViewTemplate/title*
>> El martes, 18 de mayo de 2021 a las 17:33:21 UTC+2, TW Tones escribió:
>>
>>> Álvaro
>>> Thanks for you help
>>>
>>> So the fill in the css is forcing the button to  "fill: #cc;"
>>>
>>> The problem is I want to display it with a color provided to a macro and 
>>> use it instead. Meaning the button have multiple colors depending on the 
>>> value provided.
>>>
>>> This is the macro I want to display a colored button.
>>>
>>> \define check-tag-button(tag:"select" color:"blue" 
>>> display-filter:"[all[current]is[tiddler]]" )
>>> \whitespace trim
>>> <$list filter="$display-filter$" variable=display>
>>> <$wikify name=style text="""fill: $color$;""">
>>> <$fieldmangler>
>>><$list filter="[all[current]!tag[$tag$]]" variable=has-tag>
>>>     <$button message="tm-add-tag" param="$tag$" tooltip="Toggle 
>>> $tag$"  class="tc-btn-invisible">
>>>  > ><$transclude 
>>> tiddler="$:/PSaT/check-tag/button/unchecked-icon" /> 
>>> 
>>>   
>>><$list filter="[all[current]tag[$tag$]]" variable=not-tagged>
>>> <$button  message="tm-remove-tag" param="$tag$" tooltip="Toggle 
>>> OFF $tag$"  class="tc-btn-invisible">
>>>> ><$transclude 
>>> tiddler="$:/PSaT/check-tag/button/checked-icon" />
>>> 
&

[tw5] Re: [Help] Color them icons and buttons.

[Álvaro]

The svg has two styles, one the inherited fron inline style in span and 
"direct rules" (*.tc-tiddler-controls button svg* ). When you apply direct 
rules the inherited rules are gone (they are overwritten by direct). You 
can see it in the inspector of your browser, "fill:red" is strikethrough.

You need add inline style in svg or add new class, for example in button.
button.icon-blue svg{fill:blue;}

and use it like
...
<$button message="tm-add-tag" param="$tag$" tooltip="Toggle $tag$"  
class="tc-btn-invisible icon-blue">
<$transclude tiddler="$:/PSaT/check-tag/button/checked-icon" />

...

Then you don't need wikify and you have a reusable style for the icon in 
buttons. You can change/add class dynamically to button like tiddlywiki 
does with varible and filter in *$:/core/ui/ViewTemplate/title*
El martes, 18 de mayo de 2021 a las 17:33:21 UTC+2, TW Tones escribió:

> Álvaro
> Thanks for you help
>
> So the fill in the css is forcing the button to  "fill: #cc;"
>
> The problem is I want to display it with a color provided to a macro and 
> use it instead. Meaning the button have multiple colors depending on the 
> value provided.
>
> This is the macro I want to display a colored button.
>
> \define check-tag-button(tag:"select" color:"blue" 
> display-filter:"[all[current]is[tiddler]]" )
> \whitespace trim
> <$list filter="$display-filter$" variable=display>
> <$wikify name=style text="""fill: $color$;""">
> <$fieldmangler>
><$list filter="[all[current]!tag[$tag$]]" variable=has-tag>
> <$button message="tm-add-tag" param="$tag$" tooltip="Toggle 
> $tag$"  class="tc-btn-invisible">
>  > ><$transclude 
> tiddler="$:/PSaT/check-tag/button/unchecked-icon" /> 
> 
>   
><$list filter="[all[current]tag[$tag$]]" variable=not-tagged>
> <$button  message="tm-remove-tag" param="$tag$" tooltip="Toggle 
> OFF $tag$"  class="tc-btn-invisible">
>> ><$transclude 
> tiddler="$:/PSaT/check-tag/button/checked-icon" />
> 
>   
> 
> 
> 
> \end
> 
>
> Thanks
> Tones
>
>
> On Wednesday, 19 May 2021 at 00:31:04 UTC+10 Álvaro wrote:
>
>> When you put a button (with the svg) in the viewtoolbar, it take style 
>> from here
>> *.tc-tiddler-controls button svg*, .tc-tiddler-controls button img, 
>> .tc-search button svg, .tc-search a svg {
>> fill: #cc;
>> }
>>
>> You'll need add a class to the button
>>
>>
>> El martes, 18 de mayo de 2021 a las 14:36:44 UTC+2, TW Tones escribió:
>>
>>> Folks,
>>>
>>> I have 2 svg icons from https://morosanuae.github.io/tw-icons/
>>>
>>> I have created a button inside a macro and have used a number of methods 
>>> to get the colored  result in a tiddler, however when I add 
>>> the $:/tags/ViewToolbar to a tiddler to get it into the view tool bar the 
>>> color disappears.
>>>
>>> I want to use the same buttons again and again with only the tooltip, 
>>> actions and color changing. This save buttons and color coding is helpful.
>>>
>>> Can anyone tell me how to get past what ever styling is stopping the use 
>>> of the color?
>>>
>>> Thanks in advance for any hints.
>>> Tones
>>>
>>

-- 
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/7a4981e3-f935-40fe-8b81-87ca870a2eb9n%40googlegroups.com.

[tw5] Re: [Help] Color them icons and buttons.

[Álvaro]

PD: It is a idea because you give few information. Maybe there is/are other 
problems that they are hidden in your info.

El martes, 18 de mayo de 2021 a las 16:31:04 UTC+2, Álvaro escribió:

> When you put a button (with the svg) in the viewtoolbar, it take style 
> from here
> *.tc-tiddler-controls button svg*, .tc-tiddler-controls button img, 
> .tc-search button svg, .tc-search a svg {
> fill: #cc;
> }
>
> You'll need add a class to the button
>
>
> El martes, 18 de mayo de 2021 a las 14:36:44 UTC+2, TW Tones escribió:
>
>> Folks,
>>
>> I have 2 svg icons from https://morosanuae.github.io/tw-icons/
>>
>> I have created a button inside a macro and have used a number of methods 
>> to get the colored  result in a tiddler, however when I add 
>> the $:/tags/ViewToolbar to a tiddler to get it into the view tool bar the 
>> color disappears.
>>
>> I want to use the same buttons again and again with only the tooltip, 
>> actions and color changing. This save buttons and color coding is helpful.
>>
>> Can anyone tell me how to get past what ever styling is stopping the use 
>> of the color?
>>
>> Thanks in advance for any hints.
>> Tones
>>
>

-- 
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/9a7c6bf7-c450-48dd-90b7-6e3ac7672dfbn%40googlegroups.com.

[tw5] Re: [Help] Color them icons and buttons.

[Álvaro]

When you put a button (with the svg) in the viewtoolbar, it take style from 
here
*.tc-tiddler-controls button svg*, .tc-tiddler-controls button img, 
.tc-search button svg, .tc-search a svg {
fill: #cc;
}

You'll need add a class to the button


El martes, 18 de mayo de 2021 a las 14:36:44 UTC+2, TW Tones escribió:

> Folks,
>
> I have 2 svg icons from https://morosanuae.github.io/tw-icons/
>
> I have created a button inside a macro and have used a number of methods 
> to get the colored  result in a tiddler, however when I add 
> the $:/tags/ViewToolbar to a tiddler to get it into the view tool bar the 
> color disappears.
>
> I want to use the same buttons again and again with only the tooltip, 
> actions and color changing. This save buttons and color coding is helpful.
>
> Can anyone tell me how to get past what ever styling is stopping the use 
> of the color?
>
> Thanks in advance for any hints.
> Tones
>

-- 
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/a079ec44-9a2b-4def-b04a-251a936ec745n%40googlegroups.com.

[tw5] Re: Default Tiddler Configuration

[Álvaro]

 I don't know if I understand you.

When you click in a link you got the tiddler or the empty template of 
tiddler, that Mario has shown you.

I think that an alternative for it to work with the links, you would have 
to use the LinkCatcherWidget 
 but I don't have 
much idea how it works. Maybe it doesn't work. 

El sábado, 1 de mayo de 2021 a las 15:37:39 UTC+2, cj.v...@gmail.com 
escribió:

> Alternatively, you could add a new button to the tiddler "ViewToolbar" 
> that, when clicked after save of your tiddler, finds all links in the text 
> of the tiddler that are links to tiddlers that do not yet exist, and then 
> creates each one of those tiddlers with default values.  Assuming every 
> single new tiddler you ever create gets the same defaults.
>
> If different tiddlers get different defaults, then you would want the 
> links to have something in the tiddler titles to say what kind of tiddlers 
> they are.
>
> For example:
>
>- [[John Doe s]] to indicate student
>- [[John Doe t]] to indicate teacher
>- [[Physics 101 c]] to indicate class
>- [[D232 cr]] to indicate class room
>
> So the button goes through each link in the tiddler, determines whether or 
> not the tiddler related to the link exists.  If the link is to a tiddler 
> that does not exist, then get the last part of the tiddler title to 
> determine tiddler "type", and create that tiddler with all of the default 
> values for that type.
>
> On Saturday, May 1, 2021 at 10:28:23 AM UTC-3 Charlie Veniot wrote:
>
>> G'day Jax,
>>
>> Transclusion and transclusion templates might be your friend here.
>>
>> Instead of typing into a tiddler links [[like this]], type them in {{ 
>> like this || *setAsType* }}.
>>
>> Setup *setAsType* so that if the transcluded tiddler does not exist, the 
>> result: place a button to create that tiddler (*Tip*: Set class to 
>> tc-btn-invisible tc-tiddlylink to have a button look like an internal link) 
>> with whatever default values, and then open that tiddler.  If the tiddler 
>> does exist, then never mind the button and instead show a simple link to 
>> the tiddler.
>>
>> You could then have all sorts of tiddler templates to create tiddlers 
>> with default content.  setAsStudent, setAsTeacher, setAsClass, 
>> setAsClassRoom ...
>>
>> If access to backlinks is an issue, then consider Just a neat use of 
>> Relinks "References" feature 
>>  as 
>> an alternative way to get backlinks.
>>
>>
>> On Thursday, April 29, 2021 at 2:12:46 PM UTC-3 isd196...@gmail.com 
>> wrote:
>>
>>> Hello.
>>>
>>> Thanks to posts in this group I have been able to create new buttons 
>>> that are used to create various custom Tiddlers. These are simple and work 
>>> very well, however I would like to take this one stage further.
>>>
>>> The vast majority of my new Tiddlers are created via standard square 
>>> bracket links in text that are added on the fly and then clicked to create 
>>> the new Tiddler.
>>>
>>> What I want is for those new Tiddlers that are created by clicking on 
>>> links in text, to be created with some text already in them. I'm not 
>>> worried about adding tags at this stage.
>>>
>>> Is there a system default Tiddler (or some other mechanism) that I can 
>>> edit or create so that ALL Tiddlers created when clicking on a text link 
>>> will have my default text in them?
>>>
>>> Many thanks for your time
>>>
>>> Jax
>>>
>>>
>>>

-- 
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/ed7d5464-31f2-4dba-a2d9-5d64499f951bn%40googlegroups.com.

Re: [tw5] Re: Is this a bug? Uncompleted $list statement

[Álvaro]

Hi Charlie

I think we have the same issue ( 
https://github.com/Jermolene/TiddlyWiki5/issues/5396 ). Jeremy have fixed 
it for the prerelease version. You can fixed it in your wikis (5.1.23), I 
did it and my wikis work fine now.

El lunes, 26 de abril de 2021 a las 9:40:15 UTC+2, PMario escribió:

> On Monday, April 26, 2021 at 8:15:36 AM UTC+2 Mohammad wrote:
>
>> Thank you Mark!
>> So this is a default behaviour!
>>
>
> Yes, and it's also, what you told it to do. The algorithm, has no chance 
> to know, that you are not finished with editing yet.
>
> I've run into a similar problem yesterday, that caused an endless loop.
> In normal cases I just close the preview. 
>
> But the first time ever, I needed to "kill" the browser tab. Which 
> resulted in data loss of some changes.
>
> The good thing was, that reloading fixed the problem, since the erroneous 
> code wasn't saved.
> So I was lucky!
>
> -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/b0f53f88-4910-4be0-a567-e9dc0b25fe1fn%40googlegroups.com.

Re: [tw5] [LFF] [Discussion] Using the layout switching mecanism to host a landingpage on the tiddlywiki website.

[Álvaro]

Hi Odin

I think I explained really badly, for trying not to sound too blunt.

The file size is less important than clean html, IMHO. If we add many CSS 
classes, in the future it will do more difficult do changes, in a landing 
page maybe is irrelevant but it breaks some "consistency".
.
As I said " I am sometime too purist/perfectionist" but the reason is avoid 
extra work in the future.  

El lunes, 26 de abril de 2021 a las 5:59:17 UTC+2, joshua@gmail.com 
escribió:

> Really good work. I think that as we are now able to manage the Layout 
> dynamically, each layout should be aware of the $:/Storylist and render its 
> own story river, however that should look depending on the active layout.
>
> For example, an implementation of the Muuri view as a Layout would render 
> the Storylist out as a grid.
>
> An implementation of the Mentat "virtual HUD" plugin would have its own 
> drag-able window that renders the Storylist according the the current 
> setting (as a regular Storylist view, as a Muuri grid, etc).
>
> An implementation of the Landing Page layout would allow the storyview to 
> be collapsed sticky-notes, etc.
>
> Best,
> Joshua Fontany
>
> On Sunday, April 25, 2021 at 8:20:36 AM UTC-7 jeremy...@gmail.com wrote:
>
>> Hi Odin
>>
>> The use of TailWind might be a distraction. It’s a great framework, but 
>> if we went with this landing page approach I would want to take our usual 
>> approach to CSS. I don’t think that’s a problem, what matters is that it’s 
>> great to have a concrete, tangible prototype to play with.
>>
>> Best wishes
>>
>> Jeremy.
>>
>>
>> On 24 Apr 2021, at 14:01, Odin  wrote:
>>
>> Hi Alvaro,
>>
>> Thanks for replying! 
>> TailwindCSS includes a script that purges all unused CSS from the CSS 
>> file, which is really handy. So the extra CSS for this landing page is 
>> about 11kb. All in all, it adds 0,3MB to the TiddlyWiki website file. Which 
>> isn't that bad I think.
>>
>> "...   you add a lof of noise in html. You need add too many classes for 
>> each element, and it is very similar to use inline styles but with 
>> shortcuts. (I know it, I am sometime too purist/perfectionist)"
>>
>> This is off-topic, but I think it is just a difference in design 
>> philosophy. After a while, it is easy to read the classes, and this way you 
>> don't have to ever see the CSS file. (google object/component-orientated 
>> CSS vs utility-first CSS).
>>
>>
>>
>> -- 
>> 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+...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/5cac5806-c119-4a07-a6e9-8fb73c908e36n%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/2f681d2b-1f9a-4fab-b6ab-17aa6cd58c48n%40googlegroups.com.

Re: [tw5] New magic of $list widget in Tiddlywiki 5.1.24: The index attribute

[Álvaro]

It looks great feature.

I don't have any problem with the keyword "index", the keyword connect 
perfectly with its function, IMHO. I think that the Tones's proposal 
"list-index" is great alternative.

El lunes, 26 de abril de 2021 a las 2:39:43 UTC+2, TW Tones escribió:

> Folks,
>
> I penciled this working example (tiddlywiki.com) to test some of the 
> statements, and basically found much can be satisfied with a maro.
>
> Personally I am keen to see much of this incorporated in the list widget, 
> but a new widget "lister" or "report" would be fine.
>
>- stores the original filter for reuse
>- saves the list generated by the filter for reuse
>- provides before after and during (text of first and last)
>   - Perhaps later to transclude or exec macro
>- the macros before/after and each-item are to allow reformatting the 
>output.
>
>
> \define before() 
> ;before
> :Input filter <$text text=<>/>
> :Members: <>
> :Whole list in variable ''item-list''
> ;list with ordinal available with ''position'' variable
> \end
> \define after()
> ;after
>
> \end
> \define each-item() <> <$link/> __<> <>__ 
>
> \define position() {{{ 
> [enlistallbefore:includecount[]] }}}
> \define first()  {{{ [match[1]then[first]] }}}
> \define last()  {{{ [matchthen[last]] }}}
> \define list-ordinal(filter)
> <$set name=item-list filter="$filter$">
> <$set name=last-item filter="$filter$ +[count[]]">
> <$set name=filter value="$filter$">
>
> <$wikify name=result text="<>" output=html><>
>
> <$list filter=<> >
>  <$wikify name=position text="<>">
>   <>
>  
> 
>
> <$wikify name=result text="<>" output=html><>
>
> 
> \end
>
> <>
>
>
> Tones
> On Monday, 26 April 2021 at 10:08:09 UTC+10 Brian Radspinner wrote:
>
>> I like either "ordinal" or "number" rather than index
>>
>> On Sunday, April 25, 2021 at 4:12:15 PM UTC-7 PMario wrote:
>>
>>> On Sunday, April 25, 2021 at 5:03:52 PM UTC+2 Jeremy Ruston wrote:
>>>
 Does anyone have any thoughts on an alternative?

 Perhaps “counter”?

>>>
>>> I would prefer "*number*" instead of counter.
>>>
>>> -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/986f52e4-9a97-4cde-b645-82e377322f92n%40googlegroups.com.

Re: [tw5] [LFF] [Discussion] Using the layout switching mecanism to host a landingpage on the tiddlywiki website.

[Álvaro]

Hi Odin

Great work! It looks great.And the idea of use other layout is wonderful.

Tailwind (Bootstrap, ...) is a great tool for prototyping a webpage. But I 
don't like it because, as you said, you need add extra load to the webpage, 
and also you add a lof of noise in html. You need add too many classes for 
each element, and it is very similar to use inline styles but with 
shortcuts. (I know it, I am sometime too purist/perfectionist)

Regards,
Álvaro
El sábado, 24 de abril de 2021 a las 0:27:28 UTC+2, j.te...@gmail.com 
escribió:

> Hi there Odin,
>
> Oh wow!
> Classy and clever...that will certainly be nice to have 
> for the next version of TW. Hopefully you and Jeremy 
> can figure something out.
>
> There's nothing like an enticing landing page to attract 
> prospective new users.
>
> Beautiful stuff Odin!
>
> Best regards,
> Julio
>
> On Friday, April 23, 2021 at 3:23:53 PM UTC-4 Mohammad wrote:
>
>> Hi Odin,
>>  Great job! I hope we can have a great Tiddlywiki landing page!
>>  Go with Jeremy and hopefully TW 5.1.24 has such a landing page!
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Fri, Apr 23, 2021 at 5:12 PM Odin  wrote:
>>
>>>
>>> Hello everyone,
>>>
>>> I spent some time learning the Tailwind CSS framework 
>>> <https://tailwindcss.com/> and made a concept of a landing page for 
>>> TiddlyWiki. <https://landingpage-example.tiddlyhost.com/> A landing 
>>> page is something that has come up earlier in this forum as something that 
>>> could improve the new user experience (1) 
>>> <https://groups.google.com/g/tiddlywiki/c/gH7u07ar_KI/m/LzARDYqZAAAJ>. 
>>> PM mario has made a proposal earlier (2) 
>>> <https://groups.google.com/g/tiddlywiki/c/QW7QMfr0kA0/m/8Zq-xTxsBwAJ>, 
>>> but I couldn't find any follow-up on this.
>>>
>>> TiddlyWIki 5.1.23 introduced a page-layout switching mechanism that I 
>>> used to include the landing page inside TiddlyWiki. This allows visitors to 
>>> switch instantly from the landing page to the normal TiddlyWiki website. So 
>>> with this proposal, we keep all the documentation within a press of a 
>>> button. (Jeremy used this for the TiddlyWiki-on-fission project to make 
>>> a login screen <https://tiddlywiki.fission.app/>).
>>>
>>> Furthermore, I think having a landing page as a layout opens up the 
>>> possibility to use TiddlyWikis power to have content dynamically generated 
>>> on the landing page. It would also be really cool to showcase some widgets 
>>> and macros and have the user be able to interact with them inside the 
>>> landing page. For example the section 'get started' uses transclusion to 
>>> use the saving tiddler (the one that has the grid of cards with saving 
>>> options). 
>>>
>>> I am hoping to spark some discussion on this idea. Is it will be 
>>> feasible to use? If so, I am looking for feedback on the landing page. I 
>>> used a standard color scheme that comes with TailwindCSS, but it is of 
>>> course possible to insert another color scheme.
>>> What kind of sections do you think would help TiddlyWiki's visibility? 
>>> How can we include more complicated widgets and macros within HTML without 
>>> it breaking?
>>>
>>> I've hosted the file on tiddlyhost so you can take a look: 
>>> https://landingpage-example.tiddlyhost.com/
>>>
>>> pros:
>>> * A pretty landing page is a welcoming experience for new users. Other 
>>> 'competitors' have landing pages as well that look really aesthetically 
>>> pleasing. It could help grow the TiddlyWiki community grow.
>>> * It is built inside the TiddyWiki website. Pressing the `documentation` 
>>> button or the `try it out` button instantly switches the view to the normal 
>>> TiddlyWiki layout.
>>> * It may be possible to include content dynamically on the landing page 
>>> via list widgets. 
>>> * (if it works) We could showcase the powers of widgets, macros etc. 
>>> right on the landing page. Although I ran into some issues (see the 
>>> WikiText section) and haven't figured out how to work around this.
>>> * No worries about multiple URLs
>>> * Using tailwind CSS helps create a contemporary looking website
>>>
>>> Cons:
>>> * adds an extra 0.3 mb to the website going from 5.8 mb to 6.1 mb.
>>> * The navigation links in the navbar also open up non-existent tiddlers 
>>> in the background. After switching to the normal layout, these wi

[tw5] Re: Pipe | ruins filter. Alternatives?

[Álvaro]

I understand you. It is really hard achieve use one macro or declare all 
variable in unique varswidget, except when we write very long code.

You don´t need use three varswidget because label an link are not depend 
each other. You can declare in the same varswidget.

Regards


El viernes, 23 de abril de 2021 a las 16:54:39 UTC+2, Mat escribió:

> @Alvaro and @TT, your input inspired me to rework it. It now does use two 
> macros which I was trying to avoid, and it is annoying that vars can't 
> refer to one another within the same varswidget, but still I feel it is 
> better than before and much clearer:
>
> https://link-or-ext.tiddlyhost.com/
>
> Thank you.
>
> <:-)
>

-- 
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/3c89c92a-177b-483c-919b-41ff25e417fan%40googlegroups.com.

[tw5] Re: Pipe | ruins filter. Alternatives?

[Álvaro]

I don't understand some things in your macro.

Why are you using two different methods to create the links?


I am using something like the following snippet, but i use it with two 
"basic" macros. Maybe you can use the idea of snippet in your context.

\define basic-macro(z) x5 y3 $z$

\define complex-macro(x, y)
\whitespace trim 
<$set name="result" filter=" [<__y__>!match[]]" 
value="""<$macrocall $name="basic-macro" z=<<__x__>> />""" 
emptyValue="""<$macrocall $name="basic-macro" />""" > 
<>
 
\end


Examples:

`<>`=><>

`<>`=><> 

Maybe you don't need use macrocall widget and you can use basic macro call 
<> . It depends if you need call the parameters as variables or if 
it is enought the text sustitution of the parameter. Also in the filter you 
could use it the text sustitution, in the snippet [[$y$]!match[]]
El martes, 20 de abril de 2021 a las 15:15:26 UTC+2, Mat escribió:

> Thanks Alvaro. For some reason I don't get that to work in my context, 
> i.e:  https://link-or-ext.tiddlyhost.com/
>
> The workaround I use there is bad but maybe it'll have to do (breifly; the 
> user has to himself suffix the pipe character to the pretty title in the 
> macro call) 
>
> Thanks.
>
> <:-)
>
> On Tuesday, April 20, 2021 at 2:48:11 PM UTC+2 Álvaro wrote:
>
>> You can use a variable for pipe.
>>
>> This works
>> <$vars l="[[" r="]]" x="|">{{{ hi HelloThere 
>> +[joinaddprefixaddsuffix] }}}
>> El martes, 20 de abril de 2021 a las 14:18:13 UTC+2, Mat escribió:
>>
>>> I want to create a pretty title link in a filter. Unfortunately the pipe 
>>> character in hi| breaks the filter (ref1 
>>> <https://github.com/Jermolene/TiddlyWiki5/issues/4462>).
>>>
>>> E.g these attempts no worky:
>>>
>>> <$vars l="[[" r="]]">{{{ HelloThere 
>>> +[addprefix[hi*|*]addprefix[l]addsuffix[r]] 
>>> }}}
>>>
>>> <$vars l="[[" r="]]">{{{ hi HelloThere +[join[*|*]addprefix[l]addsuffix[r]] 
>>> }}}
>>>
>>> Any ideas what to do? Maybe some magic regepx is needed but I don't know 
>>> how to construct it in that case...
>>>
>>> <:-)
>>>
>>> ...Hm, that's like my fourth question today and I didn't even have lunch 
>>> yet. I have no idea why they all mount up at the same time. I typically 
>>> tiddle fiddle for days without questions.
>>>
>>

-- 
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/2f39899b-9cb7-4e95-84d3-1586885267c8n%40googlegroups.com.

[tw5] Re: Pipe | ruins filter. Alternatives?

[Álvaro]

You can use a variable for pipe.

This works
<$vars l="[[" r="]]" x="|">{{{ hi HelloThere 
+[joinaddprefixaddsuffix] }}}
El martes, 20 de abril de 2021 a las 14:18:13 UTC+2, Mat escribió:

> I want to create a pretty title link in a filter. Unfortunately the pipe 
> character in hi| breaks the filter (ref1 
> ).
>
> E.g these attempts no worky:
>
> <$vars l="[[" r="]]">{{{ HelloThere 
> +[addprefix[hi*|*]addprefix[l]addsuffix[r]] 
> }}}
>
> <$vars l="[[" r="]]">{{{ hi HelloThere +[join[*|*]addprefix[l]addsuffix[r]] 
> }}}
>
> Any ideas what to do? Maybe some magic regepx is needed but I don't know 
> how to construct it in that case...
>
> <:-)
>
> ...Hm, that's like my fourth question today and I didn't even have lunch 
> yet. I have no idea why they all mount up at the same time. I typically 
> tiddle fiddle for days without questions.
>

-- 
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/8ab6c712-6efa-4119-be40-714adbcc6c62n%40googlegroups.com.

Re: [tw5] Tiddlywiki Color Template: Too many colors to be set

[Álvaro]

Maybe we are dealing with this problem in the wrong way.  

   - 132 selectors are too many to group directly
   - It is also a headache to try to do it with 50-60 colors that there are 
   in Vanilla (this was the way that I tried long ago)
   

However there are 15-20 colors in ContrastLight palette. We could do the 
groups more easily and also separate selectors of "special categories" 
commented by Jeremy.

When I tried it I thought that TWCrosslinks 
 (by akhater) could be useful to 
move selectors between groups. 

El sábado, 13 de marzo de 2021 a las 22:19:22 UTC+1, thomas@gmail.com 
escribió:

> Is there any list to recognize the important elements?
>>
>
> Well, here are *some* elements I did consider important: 
> https://tid.li/tw5/apps/bricks.html#%24%3A%2Fapps%2Ftelmiger%2Fbricks%2Freadability
> But it depends both on the design and the usage. 
> Example for theme complexity: I found it really hard to style a theme with 
> bright colours (dark font on light background) in the story river and dark 
> mode (bright fonts on dark background) in the sidebar.
> Examples for usage importance: The saving confirmation popping up in the 
> top right corner is important for folks like me using the single page 
> version and a browser plugin. It might be less important for people working 
> on Node.js. 
>
> By the way, you can see that my solution is not working for all colour 
> definitions. In CSS and in TiddlyWiki you can define a colour value as 
> "inherit" – but it is impossible to test that with my macros. 
>
> Hovering over the test lines with the mouse will show you the macro input 
> (near the border) and the output colours tested. 
>
> All the best,
> Thomas
>

-- 
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/1ed51933-aadc-4ff1-adce-12646b7457cdn%40googlegroups.com.

[tw5] Re: [Feedback wanted] Tweakable colour palette

[Álvaro]

Maybe it helps but it compares the contrast ratio between one color and two 
others. In the palette, we will need evaluate the contrast ratio of eack 
possible combination and then they would be ordered. 
El viernes, 12 de marzo de 2021 a las 4:07:25 UTC+1, clutterstack escribió:

> Thanks Álvaro!
>
> if it succeeded it could be grouped again to simplify the palette or to 
>> assign the colors more easily.
>>
> Yes, that could be an approach.
>  
>
>> To assign the colors, I had thought of using the contrast ratio to 
>> suggest colors for the background once the foreground was chosen.
>>
>> I wonder if the the contrastcolour macro 
> <https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Fmacros%2Fcontrastcolour.js>
>  
> in core (for tag pills) might help with that in the short term. 
>
> Best,
> Chris
>
>
>

-- 
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/7b1686c3-b91e-4cba-a2d0-cf361d1f93b6n%40googlegroups.com.

[tw5] Re: [Feedback wanted] Tweakable colour palette

[Álvaro]

Great initiative!

A long time ago I was looking at how to easily make color palettes, but it 
became a headache for so many "components" and their parts where to assign 
colors. As you looked at grouping by "components" but it is complicated 
because they have different amounts of parts (2 to 4) in the palette and if 
it succeeded it could be grouped again to simplify the palette or to assign 
the colors more easily.

To assign the colors, I had thought of using the contrast ratio to suggest 
colors for the background once the foreground was chosen.

But I started to get stuck a lot ...

Best wishes!

El jueves, 11 de marzo de 2021 a las 15:45:05 UTC+1, clutterstack escribió:

> Further to my last post, I don't guarantee the palettes generated here are 
> fit for purpose! :D
>
> On Thursday, March 11, 2021 at 9:42:20 AM UTC-5 clutterstack wrote:
>
>> Thanks TT,
>>
>> The only thing I find confusing is HOW to save a new palette set?
>>> Obviously end-users will be looking to save to new names & activate new 
>>> palettes they make. 
>>> It is just not so clear how to do that I think??
>>>
>>
>> That's because I didn't build that yet. :D However, if you are using the 
>> Vanilla theme and want to keep a palette, putting a copy of the  
>> $:/plugins/can/moods/palettes/Omelette 
>> tiddler into your TW should work. The plugin provides this tiddler, and 
>> "overwrites" it as you change things.
>>
>>>
>>> Purely FYI, Telmiger some time ago attempted to make a "Color Action 
>>> "
>>>  
>>> thing that tries to deal with "colour harmony" issues that Jermolene refers 
>>> to.  
>>> It is somewhat obscure how it works but I mention it because you might 
>>> be able to benefit from seeing at least the concept behind it.
>>>
>>> This is full of good stuff, thanks for the heads-up. And I see David has 
>> it in the TW Toolmap, so it's discoverable (I hadn't looked until you 
>> mentioned it).
>>
>> Best wishes,
>> Chris
>>
>

-- 
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/8066035c-02e2-4de3-acc9-40ed8ea843e7n%40googlegroups.com.

Re: [tw5] Presenting: SheetsIN - Import from Google Sheets into TW

[Álvaro]

Great work! Thank you to you both!
El miércoles, 10 de marzo de 2021 a las 18:16:14 UTC+1, Mohammad escribió:

> Congrats Mark and Mat!
> Very useful indeed with many opportunities!
>
>
>
> Best wishes
> Mohammad
>
>
> On Wed, Mar 10, 2021 at 12:47 PM Mat  wrote:
>
>> There is (1) Good news (2) HUGE news and (3) Bad news!
>>
>> The good news is: Mark and I have made a TW plugin to import from Google 
>> Sheets. *Every row becomes a tiddler*!
>>
>> The HUGE news is that this is the *linchpin*, the *kingpin*, *the **Rosetta 
>> Stone*, to turn pretty much anything into tiddlers because Google Sheets 
>> can be made to import data from *other *services such as your Google 
>> Drive, your Gmail, Twitter, Facebook, your GCalendar, stock charts and 
>> hundreds (thousands?) of more services 
>> . Whatever you want 
>> as tiddlers, you can get it. OK, almost.
>>
>> The bad news is: The SheetsIN plugin is only HALF of the solution! We 
>> need a SheetsOUT plugin to get tiddlers *into* Google Sheets. If this 
>> were possible, Google Sheets can then be used as a full backend for TW... 
>> *and 
>> *tiddlers can be sent as email, tweets, calendar events, etc etc. 
>>
>> So, if you have knowledge about how to "export to Google Sheets" do 
>> please shout out.
>>
>> Thus, *Mark S *and I proudly give thee the first half of the *TiddlyGoo 
>> suite* ;-)
>>
>>- Demo and download site 
>>- Github repository for dev  
>>
>> We also hope people will share their Google scripts 
>>  (!) that connect Google 
>> Sheets with other services. This is only indirectly a TW matter but will 
>> benefit us all. I will soon share a script that imports file data from 
>> Drive to Sheets so you easily show images stored on Drive in TW.
>>
>> <:-)
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/314611a9-6e4e-4bad-b668-a7e3df90f324n%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/d34b43cc-6ddf-425b-8fff-ac20770a59e3n%40googlegroups.com.

Re: [tw5] FLOSS Weekly interview with Jeremy

[Álvaro]

Thanks for sharing!

It is very interesting how you see the zoomin story view. I didn't 
understand it. It is great but I think that I need something more, maybe a 
(mini)map or/and history/path of navigation. Maybe a intermediate point 
between roam nodes and the "open" tab. I would need it to be able to locate 
myself. 

El jueves, 11 de marzo de 2021 a las 6:59:26 UTC+1, Mohammad escribió:

> Lovely! Thank you Jeremy!
>
>
>
> Best wishes
> Mohammad
>
>
> On Thu, Mar 11, 2021 at 2:39 AM Jeremy Ruston  wrote:
>
>> I've just recorded an interview with Doc Searls' FLOSS Weekly podcast:
>>
>> https://twit.tv/shows/floss-weekly/episodes/620?autostart=false
>>
>> Doc and I have worked together years ago, but the other host Jonathan 
>> Bennet hadn't come across TiddlyWiki before, and had some nicely framed 
>> questions so we spent most of the time talking about TiddlyWiki stuff. It's 
>> probably all the same things that you may have heard me say in other 
>> interviewers, but I really enjoyed it, and hope it is interesting for 
>> others.
>>
>> Best wishes
>>
>> Jeremy
>>
>> --
>> Jeremy Ruston
>> jer...@jermolene.com
>> https://jermolene.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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/F981D3CB-8E1E-4897-A462-70997273F998%40gmail.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/b24b7d40-b95d-4af7-8183-618413ad40f0n%40googlegroups.com.

[tw5] Re: newbie help with lists

[Álvaro]

As Birthe shows you, TW needs a extra line break, even between paragraphs.



El miércoles, 10 de marzo de 2021 a las 14:09:22 UTC+1, 
strikke...@gmail.com escribió:

> Welcome!
>
>
> [image: Skærmbillede på 2021-03-10 14-02-58.png]
> I hope a screenshot will do.
>
> Birthe
>
> onsdag den 10. marts 2021 kl. 13.34.49 UTC+1 skrev chena...@gmail.com:
>
>> Hi all, TiddlyWiki first timer here.  I’m a librarian with close to no 
>> computer background.  I’m *super excited* to create a digital garden, and I 
>> really want to use TiddlyWiki but am also worried that I might not have the 
>> necessary technical knowledge.
>>
>> I’m only a few tiddlers deep in my experiment, but I’ve found that when I 
>> use the bullets and numbers buttons in the editor toolbar, they don’t 
>> render.  (When I manually add in the html list tags it renders ok, but I’m 
>> hoping there’s a way I don’t have to do that every time.)
>> For example when I make some lists using the buttons in the editor 
>> toolbar, the text looks like this:
>> [image: Screen Shot 2021-03-10 at 7.15.12 AM.png]
>> and it displays like this:
>> [image: Screen Shot 2021-03-10 at 7.15.33 AM.png]
>>
>> All I’ve done so far is download the empty copy of TiddlyWiki from the 
>> GettingStarted tiddler.  I have not installed any plugins. I’m working on a 
>> macbook and opening the file in an up to date version Firefox, (but I see 
>> the same problem in Chrome).
>>
>> I read a forum thread from October 3, where someone had a similar 
>> problem, but I don’t see a “Show Bullets & Numbers checkbox” anywhere in my 
>> control panel, and I tried creating the new tiddler suggested there to no 
>> avail.
>>
>> Thanks in advance for your kindness to a total newbie.
>>
>

-- 
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/dbe10224-61a2-4988-857e-3a305eec9ab9n%40googlegroups.com.

[tw5] Re: Filter help

[Álvaro]

I have remembered that is possible make it shorter because you don't need 
to know the output, you just need know if there is only one at least. The 
then operator is unnecesary but we need change the last operator in the* 
Filter Run*. We can do someting like this

{{{ [all[tiddlers]contains:tags[HelloThere]*limit[1]*] }}}

El domingo, 21 de febrero de 2021 a las 23:21:25 UTC+1, Mat escribió:

> Mark and Alvaro, your help is much appreciated, and you gave the clues 
> needed to make it work.
> Thank you!
> <:-)
> On Sunday, February 21, 2021 at 6:15:08 PM UTC+1 Álvaro wrote:
>
>> I think I do other typo
>>
>> If I don't missunderstand something
>>
>> <$list filter="[all[tiddlers]!contains:idthen[TRUE]unique[]]" > 
>>
>> El domingo, 21 de febrero de 2021 a las 18:04:55 UTC+1, Álvaro escribió:
>>
>>> Agggh! I wrote "*all[current]*" but I wanted to write "*all[tiddlers]*"
>>>
>>> Now i put a more simple example which works in tiddlywikiDOTcom , there 
>>> are 6 tiddler with tag "HelloThere", then filter return 6 times "TRUE" but 
>>> It was trimmed with (undocumented) unique operator.
>>>
>>> {{{ [all[tiddlers]contains:tags[HelloThere]then[TRUE]unique[]] }}}
>>>
>>> If change the field tags to tagss the output of filter is empty.
>>>
>>> Now you can put your action inside of a listwidget.
>>>
>>> <$list filter="[all[tiddlers]contains:idthen[TRUE]unique[]]" >
>>> *Do X*
>>> 
>>> El domingo, 21 de febrero de 2021 a las 16:11:35 UTC+1, Mark S. escribió:
>>>
>>>> Try 
>>>>
>>>> [idthen[yes]else[no]compare:string:eq[no]]
>>>>
>>>> On Sunday, February 21, 2021 at 1:47:35 AM UTC-8 Mat wrote:
>>>>
>>>>> Need some filter help. Pseudocode:
>>>>>
>>>>> <$vars value={{foo!!value}}>
>>>>> filter=Among all tiddlers with an id field, if there is no tiddler 
>>>>> with id: then do X but if there is a tiddler with id: then 
>>>>> do nothing
>>>>> 
>>>>>
>>>>> I assume it is some kind of then ... else construct but I can't quite 
>>>>> materialize it and I'm getting confused by how I loose the tiddler titles 
>>>>> if I look at their field values. Maybe I need something with the 
>>>>> subfilter operator but I'm not sure how... ?
>>>>>
>>>>> Thank you.
>>>>>
>>>>> <:-)
>>>>>
>>>>

-- 
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/4389ef9d-0c59-4e2a-80ed-a3504828e449n%40googlegroups.com.

[tw5] Re: Filter help

[Álvaro]

I think I do other typo

If I don't missunderstand something

<$list filter="[all[tiddlers]!contains:idthen[TRUE]unique[]]" > 

El domingo, 21 de febrero de 2021 a las 18:04:55 UTC+1, Álvaro escribió:

> Agggh! I wrote "*all[current]*" but I wanted to write "*all[tiddlers]*"
>
> Now i put a more simple example which works in tiddlywikiDOTcom , there 
> are 6 tiddler with tag "HelloThere", then filter return 6 times "TRUE" but 
> It was trimmed with (undocumented) unique operator.
>
> {{{ [all[tiddlers]contains:tags[HelloThere]then[TRUE]unique[]] }}}
>
> If change the field tags to tagss the output of filter is empty.
>
> Now you can put your action inside of a listwidget.
>
> <$list filter="[all[tiddlers]contains:idthen[TRUE]unique[]]" >
> *Do X*
> 
> El domingo, 21 de febrero de 2021 a las 16:11:35 UTC+1, Mark S. escribió:
>
>> Try 
>>
>> [idthen[yes]else[no]compare:string:eq[no]]
>>
>> On Sunday, February 21, 2021 at 1:47:35 AM UTC-8 Mat wrote:
>>
>>> Need some filter help. Pseudocode:
>>>
>>> <$vars value={{foo!!value}}>
>>> filter=Among all tiddlers with an id field, if there is no tiddler with 
>>> id: then do X but if there is a tiddler with id: then do 
>>> nothing
>>> 
>>>
>>> I assume it is some kind of then ... else construct but I can't quite 
>>> materialize it and I'm getting confused by how I loose the tiddler titles 
>>> if I look at their field values. Maybe I need something with the 
>>> subfilter operator but I'm not sure how... ?
>>>
>>> Thank you.
>>>
>>> <:-)
>>>
>>

-- 
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/50f9cc7a-e4e7-4015-8968-092246e1f348n%40googlegroups.com.

[tw5] Re: Filter help

[Álvaro]

Agggh! I wrote "*all[current]*" but I wanted to write "*all[tiddlers]*"

Now i put a more simple example which works in tiddlywikiDOTcom , there are 
6 tiddler with tag "HelloThere", then filter return 6 times "TRUE" but It 
was trimmed with (undocumented) unique operator.

{{{ [all[tiddlers]contains:tags[HelloThere]then[TRUE]unique[]] }}}

If change the field tags to tagss the output of filter is empty.

Now you can put your action inside of a listwidget.

<$list filter="[all[tiddlers]contains:idthen[TRUE]unique[]]" >
*Do X*

El domingo, 21 de febrero de 2021 a las 16:11:35 UTC+1, Mark S. escribió:

> Try 
>
> [idthen[yes]else[no]compare:string:eq[no]]
>
> On Sunday, February 21, 2021 at 1:47:35 AM UTC-8 Mat wrote:
>
>> Need some filter help. Pseudocode:
>>
>> <$vars value={{foo!!value}}>
>> filter=Among all tiddlers with an id field, if there is no tiddler with 
>> id: then do X but if there is a tiddler with id: then do 
>> nothing
>> 
>>
>> I assume it is some kind of then ... else construct but I can't quite 
>> materialize it and I'm getting confused by how I loose the tiddler titles 
>> if I look at their field values. Maybe I need something with the 
>> subfilter operator but I'm not sure how... ?
>>
>> Thank you.
>>
>> <:-)
>>
>

-- 
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/fa2461f5-afa2-4c16-9763-7d22835e89f3n%40googlegroups.com.

[tw5] Re: Filter help

[Álvaro]

Have you tried with contains operator?

In direct filter transclusion you can use something like that
{{{ [all[current]!contains:idthen[I have to do X]else[] }}}

Then you can use the filter in a listwidget and use the variable created by 
the listwidget.

El domingo, 21 de febrero de 2021 a las 10:47:35 UTC+1, Mat escribió:

> Need some filter help. Pseudocode:
>
> <$vars value={{foo!!value}}>
> filter=Among all tiddlers with an id field, if there is no tiddler with 
> id: then do X but if there is a tiddler with id: then do 
> nothing
> 
>
> I assume it is some kind of then ... else construct but I can't quite 
> materialize it and I'm getting confused by how I loose the tiddler titles 
> if I look at their field values. Maybe I need something with the subfilter 
> operator but I'm not sure how... ?
>
> Thank you.
>
> <:-)
>

-- 
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/d59560a3-193f-48d2-9662-284cca980b89n%40googlegroups.com.

[tw5] Re: question: sorting index:value in a dataTiddler by values

[Álvaro]

I also want to work with indes and values.  But I did not know how to do it 
combining filters like you. Then i created a new filter cloning  * 
$:/core/modules/filters/indexes.js *and I modified it for obtain values, 
the important changes are in bold.
  
/*\
values.js
type: application/javascript
module-type: filteroperator

Filter operator for returning the values of a data tiddler

\*/
(function(){
"use strict";

/*
Export our filter function
*/
exports.*values* = function(source,operator,options) {
var results = [];
source(function(tiddler,title) {
var data = options.wiki.getTiddlerDataCached(title);
if(data) {
$tw.utils.pushTop(results,Object.*values*(data));
}
});
return results;
};

})();

Now you can use it. [values[]] instead the *populate* macro 
which is filtering the output of other filter.
El jueves, 18 de febrero de 2021 a las 20:30:23 UTC+1, Mohammad escribió:

> when using nsort on new values (e.g. value::index note :: is a character 
> used to create new entries) it fails.
> One solution is as below, but for large number index - value (e.g 200 or 
> more) the solution is very slow
>
> This solution contains
>
> 1. a populate macro to list all values
> 2. a wikify and list widget let sort values
> 3. a lookup macro to find index(s) for a value
>
> \define  dataTiddler() myData  
> \define myfilter() [indexes[]] 
>
> \define populate()
> <$list filter="[subfilter]">
> <$text text={{{[getindex]}}}/>
> 
> \end
>
> \define lookup-index(val)
> <$list filter="[subfilter]" variable=idx>
> <$list filter="[getindex] +[match[$val$]]">
> 
> <$link to=<> /> $val$ 
> 
> 
> 
> \end
>
>
> 
> <$wikify name=u text=<> >
> <$list filter="[enlistnsort[]]">
> <$macrocall $name=lookup-index val=<> />
> 
> 
> 
>
>
> The above can be tested in https://tiddlywiki.com/ if one creates a data 
> tiddler with the myData title containing the data of the previous post.
>
> Question: as stated above this solution is very slow for large numbers of 
> data (index-value pairs). What alternative solution do you propose?
>
> Best wishes
> Mohammad
>
>
> On Thu, Feb 18, 2021 at 10:07 PM Mohammad Rahmani  
> wrote:
>
>> This is an old question and there are several solution for that, but not 
>> for the case I explain here
>>
>> Assume you have a dataTiddler or JSON tiddler with data like below
>>
>> nella: -1
>> rita: 1
>> villa: 0
>> lola: -7
>> sina: 3
>> cobra: 2
>> fifa: -2
>> zila: 3
>> afra: 1
>>
>>
>> I want to list data in this dictionary table sorted by value, so I should 
>> have
>>
>>   lola: -7  
>>   fifa: -2 
>>   nella: -1  
>>   villa: 0  
>>   afra: 1  
>>   rita: 1  
>>   cobra: 2 
>>   sina: 3  
>>   zila: 3 
>>
>> Note, there are duplicated values. The solution is that new entries 
>> created from appending value to index like value::index do not work here!
>> As you need to use nsort
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>

-- 
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/65d562c5-88e4-49b1-aa5f-e399ca397a81n%40googlegroups.com.

[tw5] Re: Has anyone noticed that the "delete" button is off-center in the "more" dropdown list?

[Álvaro]

You could do it in the repository, but it was already reported time ago.

The issue
https://github.com/Jermolene/TiddlyWiki5/issues/5319

El miércoles, 3 de febrero de 2021 a las 16:12:15 UTC+1, si escribió:

> Should it be pointed out somewhere so that it can be fixed in the next 
> release?
> On Tuesday, 2 February 2021 at 01:50:05 UTC strikke...@gmail.com wrote:
>
>> Yes and it looked okay in the prerelease.
>> The difference is:
>>
>> \whitespace trim
>>
>> In tiddler:$:/core/ui/Buttons/delete
>>
>> Birthe
>>
>> mandag den 1. februar 2021 kl. 23.17.26 UTC+1 skrev si:
>>
>>>
>>> Since the new version, if you click on the "more" button on the View 
>>> Toolbar the "delete" button is out of line with the rest.
>>>
>>> It seems unlikely that I am the only person to have noticed, but I 
>>> thought I'd mention it just in case.
>>>
>>

-- 
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/199ed99e-cf92-4380-8bb1-f6677b862a4an%40googlegroups.com.

[tw5] Re: New to Tiddlywiki and I need help (.html ??)

[Álvaro]

Hi, 

This type of information is usually in tiddlywiki.com/dev/

I think that you need this-> https://tiddlywiki.com/dev/#Data-Storage

El miércoles, 27 de enero de 2021 a las 0:42:19 UTC+1, TW Tones escribió:

> Hi,
>
> I am not totally clear on the objective of the task, but tiddlywiki itself 
> uses a process to save an empty file. If you follow how this works on 
> Tiddlywiki.com starting with the download empty button you can see it uses 
> a template and within that a filter determines which tiddlers to download 
> and their format, any tiddlywiki can generate an empty.html file. This can 
> also be done via commands in NodeJS. One feature exports the Javascript 
> separately rather than a single file. This template effectively encodes the 
> way to save a whole wiki, thus arguably contains all the logic needed. 
>
> It is best to use tiddlywiki itself to load tiddlers into it, be it the 
> node or single file wikis importing tiddlers.  If you take the completely 
> manual approach to edit the html you need to understand precisely the 
> tiddler format (that's trivial)  and where entries are to be stored in the 
> html file. You will also see in the html file the tiddlers are stored in 
> one place but they are often referenced by name in other parts only detail 
> knowledge of the tiddlywiki structure can answer how and if you need to do 
> more to add tiddlers directly.
>
> I hope others can provide more info, but I hope this helps somewhat.
>
> Tones
> On Wednesday, 27 January 2021 at 08:10:48 UTC+11 mmes...@gmail.com wrote:
>
>> So i started Working with my professor on Tiddlywiki and i found it quite 
>> interesting. Now i m working on an automatic generated Tiddlywiki project 
>> from  a Java project . So all the informations i need to build my 
>> Tiddlywiki is in the Java File and my professor told me he wants all those 
>> informations to be generated automatically in a Tiddlywiki at first i just 
>> make .tid files for each tiddler and i thought i was done but he wanted me 
>> to write on an Empty tiddlywiki file (Empty.html) that way when the java 
>> program is executed it writes on the the File Empty.html  (as if it is a 
>> .txt file )but it didn't work and i only write at the end of the html code 
>> .i can't find anything to help me out or where exactly should i write or 
>> how to write it  other than that i have no knowledge of html or js which 
>> made this one near impossible task  , please guys i need your help i'm 
>> already running late and i have no idea what to do .
>>
>

-- 
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/0a2a6849-7c50-48d9-bb6f-8483f19195fan%40googlegroups.com.

Re: [tw5] [ANN] Notebook theme v1.3.6 is out!

[Álvaro]

Thank you Nicolas. 

This theme is great. I had thought to make myself one very similar. 
El domingo, 24 de enero de 2021 a las 4:11:59 UTC+1, Mohammad escribió:

> Hi again,
>  It seems the issue is with Tiddlywiki itself and not the Notebook theme. 
> The tag pill has a poor css design.
>
> Best wishes
> Mohammad
>
>
> On Sun, Jan 24, 2021 at 6:34 AM Mohammad Rahmani  
> wrote:
>
>> Thank you Nico,
>>
>> I just notice the tag pill has an extra right margin. See 
>> https://nicolas.petton.fr/tw/notebook.html#Customizing
>> and edit the tiddler content  <>, next words
>> Note to the comma I put after > save and see the extra space.
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Sat, Jan 23, 2021 at 11:25 PM Nicolas Petton  wrote:
>>
>>> Hi!
>>>
>>> I'm happy to announce the release of Notebook v1.3.6!
>>>
>>> You can install/upgrade from
>>>
>>>   https://nicolas.petton.fr/tw/notebook.html
>>>
>>> This is a minor release, here the changelog:
>>>
>>> Improvements
>>>
>>> * New animation for drop-downs
>>> * Tab styling improvements
>>> * Use a lighter page background colour in the beige palette
>>>
>>> Fixes
>>>
>>> * Fix the default ctrl+shift+F shortcut for focusing the search input
>>>
>>> Cheers,
>>> Nico
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/87mtwzqvh1.fsf%40petton.fr.
>>>
>>

-- 
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/7a611419-75b7-423d-9175-3c6c12715e1bn%40googlegroups.com.

[tw5] Re: White background behind tiddles.

[Álvaro]

With this information i am also lost.

I don't know how you started to create this dark palette. But you can start 
cloning a dark palette like *Twilight*, maybe you can avoid some color 
changes. Do you know how to clone one?

El domingo, 24 de enero de 2021 a las 1:49:47 UTC+1, clutterstack escribió:

> Wow, I'm really not sure what's happening there, sorry, unless you have a 
> custom stylesheet tiddler (or a plugin containing one) overriding the 
> palette tiddler.
>
> Best,
> Chris
> On Saturday, January 23, 2021 at 7:13:48 PM UTC-5 Mark 3000 wrote:
>
>> Page-background under the palette tiddler simply changes the background 
>> of the side bar, and the tiddler. The white space does not change no matter 
>> what, unless I manually adjust that tc.story-river variable that I 
>> mentioned. As a matter of fact, I've experimented by changing the all of 
>> the colors under palette, and exactly zero of them change that white 
>> background color. I'm at a loss.
>>
>> On Saturday, January 23, 2021 at 5:06:32 PM UTC-7 clutterstack wrote:
>>
>>> Hi Mark,
>>>
>>> Sorry for not checking back here. Did you figure out your problem? I 
>>> think I'm missing some information on what you did to change the colour. If 
>>> you changed the colour for *page-background* in the palette tiddler, 
>>> I'd have thought that would do the trick.
>>>
>>> If you by any chance are changing css rules within developer tools in 
>>> your browser, that will definitely get undone on reload. It's great for 
>>> figuring out what's happening in the browser, testing rules, etc. Then you 
>>> go back to your source file(s) and change what you want changed; in this 
>>> case a palette tiddler in the tiddlywiki.
>>>
>>> Best,
>>> Chris
>>>
>>> On Monday, January 18, 2021 at 12:39:57 AM UTC-5 Mark 3000 wrote:
>>>
 Thanks for the help clutterstack. I managed to change the white 
 background to my preferred color using your suggestion. The variable for 
 the background color is under tc.story-river. However, if I change any of 
 the other colors for any other element, it automatically switches the 
 story 
 river color back to white. Also, if I close the wiki and reload it, it 
 goes 
 back to white. Any ideas what I should do to make the change permanent?

 On Sunday, January 17, 2021 at 1:28:49 PM UTC-7 clutterstack wrote:

> Hi Mark, 
>
> It looks to me as if that light background corresponds to 
> page-background in the colour palette, but hard to tell without being 
> able 
> to use developer tools to look at the elements.
>
> In-browser developer tools are invaluable in figuring out which 
> element is which on the page, and which css rules are being applied. I'd 
> suggest checking them out if you haven't.
>
> Best,
> Chris
>
> On Saturday, January 16, 2021 at 7:52:37 PM UTC-5 Mark 3000 wrote:
>
>> I'm a complete tiddlywiki newbie. I don't have any advanced 
>> requirements or anything at this time. My only issue is that no matter 
>> what 
>> colors I choose inside the palette section, I always have this 
>> persistent 
>> white background color behind the tiddles. See the attached image.
>>
>> I'm trying to create a dark/night-themed wiki, and this bright white 
>> background is bugging the heck out of me. Also, a lot of fields are 
>> white 
>> in color as well, and I can't figure out how to fix that either.
>>
>> Any help would be appreciated, thanks!
>>
>> [image: wikiissues.jpg]
>>
>

-- 
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/41346a03-62d5-4c3b-bffa-251b924c9729n%40googlegroups.com.

Re: [tw5] Re: TiddlyWiki Project Name

[Álvaro]

Hi community! Happy new year!

I think that we are all clear that TW has a basic unit, the tiddler. We can 
build our TW with them. We can rename them as *card *, *record*, ..., and 
then we can rename the project.
For example, with tiddler rename as *tile* we can rename TW as *kaleido* or 
*mosaic*. But then we lose the term of tiddler, the most reconocible part 
of Tiddlywiki.

Maybe we can rethink about the conexión between our least element (tiddler) 
and the whole (Tiddlywiki). A shoal is made up of many fish. Is *Shoal *good 
name? It sound good to me, but i'm not a English-speaking/anglophone.
El sábado, 2 de enero de 2021 a las 11:05:22 UTC+1, TiddlyTweeter escribió:

> Regarding ideas of CARD or RECORD or variants thereof like "AtomCards" 
> (i.e. that emphasise the atomistic nature of the "unit").
>
> Well. Not sure. I still prefer Tiddler as FRAGMENT. A bit more. 
>
> Why? The problem with "Record" and "Card" is both imply 
> self-contained-wholeness. Basically echoing database structural units.
>
> I'd need convincing our "Atomic Units" should be conceptualized that way. 
> That is NOT how I experience the "fragment" in TW/XEMEMEX.
>
> It is actually NOT so self-contained or self-substituent.
>
> Just thoughts
> 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/a07877ae-072c-4d6e-8092-6bf14d5fafeen%40googlegroups.com.

[tw] Re: Unable to transclude

[Álvaro]

What is it "Notes"? Tiddler? Created field? ??

If it is a tiddler, you are building a filter with the title that is result 
of join the title of current tiddler and tiddler with title "Note". For 
example, if "New tiddler" is title of the current tiddler, you obtain link 
to tiddler with the title "New tiddler Note". When you do click in link, TW 
opens a missing tiddler if there wasn't any tiddler with this title.

http://tiddlywiki.com/#Introduction%20to%20filter%20notation

Sorry for my english.

Álvaro 



El miércoles, 25 de enero de 2017, 3:32:25 (UTC+1), Cully escribió:
>
> I have defined macro named ThisContactNotes with:
>
> \define ThisContactNotes() [[$(currentTiddler)$ Notes]]
>
> If I use the macro to link <> it generates the correct 
> link and I can click through to the Tiddler.
>
> If I attempt to transclude the Tiddler nothing is returned. 
>
> I have tried to use:
>
> {{ThisContactNotes}}
>
> and
>
> {{||ThisContactNotes}}
>
> Any help would be great!
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1f4832f3-5a3b-4840-b424-a15be2b6fe93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Very strange behavior bug report

[Álvaro]

Upss sorry.

I see it. I don't know if it is a bug or not. But if you create two new 
tiddler ("New Tiddler" and "New Tiddler 1") and you try to modify the title 
of "New Tiddler 1" to "New Tiddler ", when you save it, TW shows popup 

*Do you wish to overwrite the tiddler "New Tiddler"? *When you save a 
tiddler in the editor, it removes the spaces at the end of the tittle.

The conflict appears because "$action-setfield" allows add a field with 
space at the end of its value. When you edit and save the tiddler, TW 
create new tiddler because TW doesn't match any tiddler with that title.

Sorry for my english.



El viernes, 20 de enero de 2017, 16:58:42 (UTC+1), CL escribió:
>
> Hi Alvaro
>
> 'Test:first' works fine as I described in the instruction.
> 'Test:second(space)' is the buggy part.
>
> Have you tried to change the title of 'Test:second(space)'?
>
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b9ef0c57-f15b-42e8-bb1b-bf2dbdc1dd4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Very strange behavior bug report

[Álvaro]

Hi CL,

It works fine. I don't see any bug. In both cases, you have two part in 
text: *variable part* and *invariable part*. You cut the variable part and 
you change its content and its position, but there isn't any change in 
content of invariable part.

*first**Test* ->*Test:**first*
*second(space)**Test* ->*Test:*

*second(space)*Is it the bug?

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5f84e284-2d0a-471b-8c1e-593b981858ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Lighter MGSD or migration to tbGTD

[Álvaro Tejero Cantero]

Dear list,

My MGSD has become quite heavy and all the pull-down menus and
checkboxes don't help. I think I could live without them. So here come
my two questions

a) anybody has tried to get MGSD 'stripped bare'? I also use my
monitor vertically and 1200px of width don't provide for very nice
three-column lists - that is something I would also like to
deactivate.

b) I want to try and see if tbGTD solves my problems - it seems
promising. Does anybody here have experience with a MGSD-tbGTD
migration? Any tips? I could write a Python script to do it if I can
collect a list of required renames and retags.

Thanks,

-Álvaro.

-- 
You received this message because you are subscribed to the Google Groups GTD 
TiddlyWiki group.
To post to this group, send email to gtd-tiddlyw...@googlegroups.com.
To unsubscribe from this group, send email to 
gtd-tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/gtd-tiddlywiki?hl=en.