date:20210628

Saq,

The breadcrumbs in Stream are nice. As I understand it the breadcrumbs find 
the parents to the given node. In this case using parent and streams-list 
fields.

I thought of the following because I expect streams includes 90% of the 
code to do as follows.

Mario's TopP plugin Allows new here on a nominated tiddler and creates the 
Parent field. 

It seems the *breadcrumbs feature* could be split out into a generic plugin 
itself the simple specifications would be;

   - Using the currentTiddler (or a supplied one) as the node in a 
   breadcrumb trail
   - Provide the parent fieldname
   - Provide the children's list field.
   - If there is no parent or child list field (but the other is present) 
   indicate top or Bottom
  - If neither do not display at all
   - Allow horizontal (default) or vertical breadcrumbs (in side bar)

Ways to display such breadcrumbs could be in the above and below story, a 
menu bar second row or floating bar. One trick I have used for a tool I 
call "focus tiddler" is to access {{$:/HistoryList!!current-tiddler}} which 
contains the last edited or navigated to tiddler, and a simple viewToolbar 
button can set this to the set tiddler. Thus the breadcrumbs will be 
displayed for the current tiddler with focus (on screen but optionally 
outside the tiddler). It may also look nice in the subtitle in small text.

Just some ideas to leverage your existing work.

Tonesza

On Tuesday, 29 June 2021 at 09:42:47 UTC+10 Saq Imtiaz wrote:

> Thank you Stan and Steph. 
> I'll post a link here and on reddit once the questionnaire is ready. 
>
>
> On Tuesday, June 29, 2021 at 1:07:37 AM UTC+2 stan...@gmail.com wrote:
>
>> You can add me to the list for the questionaire.  Streams is an excellent 
>> addition to TW.
>> Stan
>>
>> On Monday, June 28, 2021 at 1:44:26 PM UTC-4 saq.i...@gmail.com wrote:
>>
>>> @si
>>>  
>>>
 I've also been considering asking for volunteers for a small group of 
> regular users of Streams for testing new features..

 I'm happy to test stuff out as required.  

>>>
>>> I think I will start out with a questionnaire and also use that as an 
>>> opportunity to ask for volunteers for testing.
>>>
>>> I will give some more thought to the breadcrumbs.
>>>
>>> Regards,
>>> Saq
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9aff4845-83d4-4eca-8427-8d6d9f55e124n%40googlegroups.com.

[tw5] Re: protected macros

Have a closer look at: 
https://tiddlywiki.com/#dumpvariables%20Macro:%5B%5Bdumpvariables%20Macro%5D%5D%20%5B%5Bdumpvariables%20Macro%20(Examples)%5D%5D

and: https://tiddlywiki.com/#LogWidget:LogWidget%20ActionLogWidget

They may help you to see what's going on. .. The later 2 can only be seen 
in the browser dev console. 

-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/23ae7f68-2e7c-4707-8fae-1b2bf9e3bf13n%40googlegroups.com.

[tw5] Re: protected macros

On Tuesday, June 29, 2021 at 1:43:23 AM UTC+2 jn.pierr...@gmail.com wrote:

> In a tiddlers tagged as #:/tags/Macro there is a public macro. It requires 
> other macros to achieve its goals, but these macros have no business being 
> used elsewhere.
>
> If I declare these macros in the same tiddler, they are exported. Bad :-( 
> To mitigate that, I have their name beginning with an underscore, meaning 
> to me not to use them elsewhere.
>
> But if two differentss macros tiddler both define their own _subMacro, 
> what _subMacro would be called? the one in the same tiddler or maybe yes, 
> maybe not, we can't say. This is the real problem.
>

No. That's a feature. This behaviour allows the core to define sensible 
defaults, that can be overwritten by the user at any time. As I wrote in 
the other thread. 

\define xx() xx

is a shortcut for 

<$set name=xx value=xx>
tiddler content

So *the local macro with the same name will always win!*If there is no 
local macro the predefined one will be used.

Global macros have an order. Typically they are initializes in alphabetical 
order by the tag. So if you have

title: a
tags: $:/tags/Macro 
text: \define me() a

and

title: b
tags: $:/tags/Macro 
text: \define me() b

For global macros the rule is:* The last one wins*

So yes. Your naming convention will influence the order, who macros are 
initialized. .. BUT since you know that now, you can *use it for your 
advantage* ;)

> A suggestion: could we say that any macro whose name starts by _ or even 
__ for compatibility's sake, is not exported even within a macro tiddler? 

*No*, because this would be not backwards compatible. But you can use this 
convention if you like, but the system won't enforce it. 

The way it is designed is consistent but not always obvious.

-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/bede2e6d-7723-441f-ad26-c79300dca3dcn%40googlegroups.com.

[tw5] Re: using negative values

2021-06-28 Thread paulgilbert2000

Thank you tones

it was indeed the space

On Monday, June 28, 2021 at 3:43:56 PM UTC+2 TW Tones wrote:

> Mohamed,
>
> Negative values may not always be valid but you example has a space 
> between the sigh + or - and the number. Make it part of the number with no 
> gap. -4 NOT - 4
>
> Regards
> Tones
>
> On Monday, 28 June 2021 at 23:12:26 UTC+10 mohamed...@hotmail.com wrote:
>
>>
>> Hi ,
>>
>> i have a field that has a number value  referenced in a mathematical 
>> operation
>>
>> now I need to use a negative number  , like say - 4  
>>
>> if i write the number  like that ,the mathematical operation does not 
>> work and does not pick up on the number 
>>
>> is there a specific format for using negative values ?
>>
>>
>>

-- 
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/44f14047-a736-4163-9ec0-935f7651de01n%40googlegroups.com.

[tw5] Re: template: where is the widget???

On Tuesday, June 29, 2021 at 1:15:35 AM UTC+2 jn.pierr...@gmail.com wrote:

Here are some things that *change the current tiddler*:
>
>- Transcluding another tiddler with the {{curly braces}} syntax.
>- Using a $list widget to enumerate the outputs of a filter.
>- Directly setting currentTiddler with a $set or $vars widget.
>
> Does it mean that you can change the content of a var or that you stack up 
> vars, getting only the values from the top var?
>

You "stack up vars". So variables have a scope. That's the reason why we 
sometimse need a construction like this:

title: myTemplate

\define concat() $(currentTiddler)$-$(title)$

<$list filter="a b c" variable=title>
<>

Since the list-widget would "overwrite" the currentTiddler with the default 
setting we can provide a new variable name. In this case "title"
The currentTiddler is the tiddler, the code lives in. 

If you create a new tiddler named: test ... You can play with templates. 

title: test

{{myTemplate}}

---

{{||myTemplate}}

> Could it be used to have some kind of recursion in a safe way?
>

Yes. We use recursion a lot. eg: the toc-macros. 

> I was thinking of vars as immutable stuff because of the syntax that 
> declare them but no syntax to alter them otherwise.
>

As I wrote. Variables have a scope. They are valid inside the widget they 
are defined in . 

\define test() abc
\define test() xyz

<>  ... Will be xyz 

So the last one wins. The above code is a "*shortcut *of" 

<$set name=test value=abc>
<$set name=test value=xyz>

<>

Try this: 

<$set name=test value=abc>

<>

<$set name=test value=xyz>

<>

> And finnally, in a number of my templates, the template content is only 
> <>. It seems a bit out of touch with what your telling me with 
> what template are. In effect, myMacro is only used there. Would it b a 
> better idea to ditch the macro and have the macro body directly into the 
> template text? (yes, myMacro has no params.)
>

It depends. When your code is finished, it is probably more efficient that 
the template only contains the template text. 
But for testing the following makes sense. 

title: xTemplate

\define  myMacro() 
this code works but looks odd
\end

\define myMacro()
this code is  WIP but might look better in the end. 
\end

<>

This gives you the possibility to easily test new code, without overwriting 
your "old but working" code. ... BUT BUT BUT ... 
Once the new code works and is cleaner. You need to remove the old code. .. 
There should be only 1 "source of truth"

Otherwise you will have a nightmare to maintain your code .. trust me ;)

-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/609a6264-8676-45a5-ac1d-5820fb1f33fcn%40googlegroups.com.

[tw5] Re: Discussion: Tiddler titles for sources

2021-06-28 Thread Charlie Veniot



On Monday, June 28, 2021 at 1:51:05 PM UTC-3 Si wrote:

>
> I have been thinking about this and two possible advantages occur to me:
>
>- Shorter titles are quicker to type when linking from other tiddlers.
>- More importantly, perhaps they are easier to remember, or 'lock 
>onto'? For example I will probably more easily be able to pull 
>"DeliberatePractice1993" from my brain than I would "The Role of 
> Deliberate 
>Practice..." This relates to titles functioning like APIs 
>.
>
>
>
If you do want something to make it easy to find titles while creating 
links, you might find the Edit-CompText 
 plugin really helpful.

 

-- 
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/17bcc5ee-42a2-4010-86b8-470761b64e69n%40googlegroups.com.

[tw5] protected macros

In a tiddlers tagged as #:/tags/Macro there is a public macro. It requires 
other macros to achieve its goals, but these macros have no business being 
used elsewhere.

If I declare these macros in the same tiddler, they are exported. Bad :-( 
To mitigate that, I have their name beginning with an underscore, meaning 
to me not to use them elsewhere.

But if two differentss macros tiddler both define their own _subMacro, what 
_subMacro would be called? the one in the same tiddler or maybe yes, maybe 
not, we can't say. This is the real problem.

same question if my macro tiddler has _myStuff macro and a non macro 
tiddler define a macro also called _myStuff and use it: which one would be 
called? That's a variation from the previous question.

I know I can have _mySuff macro into a separate non macro tiddler, and 
\import it within my macro tiddler. That way my macro tiddler is 100% 
functionaal and _myStuff is not exported but creating another tiddler is a 
problem in itself: it's yet another tiddler, it's not that a good idea 
because it's only there for a single tiddler, and I would need to have a 
name for it. It would complexify my naming convention which is already a 
lengthy paper... and I would have to decide which idea is the one I shall 
get. to be honest, my macro fubar for the foo matter is in 
$:/user/foo/macros/fubar. So where should _sub4fubar be ? 
$:/user/foo/macros/fubar/private would do but then $:/user/foo/macros/fubar 
would both be a file and a directory, whis is a no go. So no way to store 
anything below the macro name. $:/user/foo/privateMacros/fubar perhaps? 
or  $:/user/foo/private/macros/fubar ? I could have some macro for a bar 
filter in $:/user/foo/private/filters/fubar but then I don't have the same 
meaning for macros there than in the $:/user/foo/macros/fubar where 
"macros" tells that here are macros but in $:/user/foo/private/macros/fubar 
"macros" tells that this concerns a macro tiddler  named fubar but could be 
whatever, not especially macros (altgough very likely macros). And when the 
macro has no sub macros, the naming convention shouuld be the same: do not 
complexify 100% for the 10%. This rules out a scheme like 
$:/user/foo/macros/fubar/fubar and $:/user/foo/macros/fubar/_sub4fubar 
which would otherwise answer the question (but being a very ugly beast).

A suggestion: could we say that any macro whose name starts by _ or even __ 
for compatibility's sake, is not exported even within a macro tiddler?

-- 
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/fd8f1a78-196c-4508-837e-7c53580563e0n%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

2021-06-28 Thread Saq Imtiaz

Thank you Stan and Steph. 
I'll post a link here and on reddit once the questionnaire is ready. 


On Tuesday, June 29, 2021 at 1:07:37 AM UTC+2 stan...@gmail.com wrote:

> You can add me to the list for the questionaire.  Streams is an excellent 
> addition to TW.
> Stan
>
> On Monday, June 28, 2021 at 1:44:26 PM UTC-4 saq.i...@gmail.com wrote:
>
>> @si
>>  
>>
>>> I've also been considering asking for volunteers for a small group of 
 regular users of Streams for testing new features..
>>>
>>>
>>> I'm happy to test stuff out as required.  
>>>
>>
>> I think I will start out with a questionnaire and also use that as an 
>> opportunity to ask for volunteers for testing.
>>
>> I will give some more thought to the breadcrumbs.
>>
>> Regards,
>> Saq
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3d0dde82-8027-45e6-9b1f-cb227ed0534fn%40googlegroups.com.

[tw5] Re: template: where is the widget???

Thank you to both of you for your explanation. The information on the 
system tag was very helpful.

@Soren: you write tgis in your textbook:

Here are some things that *change the current tiddler*:

   - Transcluding another tiddler with the {{curly braces}} syntax.
   - Using a $list widget to enumerate the outputs of a filter.
   - Directly setting currentTiddler with a $set or $vars widget.

Does it mean that you can change the content of a var or that you stack up 
vars, getting only the values from the top var?

Could it be used to have some kind of recursion in a safe way? I was 
thinking of vars as immutable stuff because of the syntax that declare them 
but no syntax to alter them otherwise.

And finnally, in a number of my templates, the template content is only 
<>. It seems a bit out of touch with what your telling me with 
what template are. In effect, myMacro is only used there. Would it b a 
better idea to ditch the macro and have the macro body directly into the 
template text? (yes, myMacro has no params.)

regards,

-- 
Jean-Pierre
Le lundi 28 juin 2021 à 16:18:20 UTC+2, Soren Bjornstad a écrit :

> I've read in the doc that widgets are the fundamental part of tiddlywiki 
>> and that all wiki syntax sugar is finally resolved as a number of widgets.
>>
>> Use of template is only described with transclusion as {{||template}} 
>> (with tiddler or field or index before ||).
>>
>> the transclude widget has no template attribute.
>>
>> How then is done the transclusion? Shouldn't the transclude widget have a 
>> template attribute?
>>
>
> Actually, the *template *is what's being transcluded during a 
> transclusion, not the tiddler. When you transclude a tiddler through a 
> template, the current tiddler is set to that tiddler and then the template 
> is transcluded.
>
> {{Tiddler||Template}} evaluates to:
>
> <$tiddler tiddler=Tiddler>
>   <$transclude tiddler=Template/>
> 
>
> {{||Template}} doesn't change the current tiddler and so evaluates to 
> simply:
>
> <$transclude tiddler=Template/>
>
> {{Tiddler1}} is shorthand for {{Tiddler1||Tiddler1}}, and evaluates to:
>
> <$tiddler tiddler=Tiddler1>
>   <$transclude tiddler=Tiddler1/>
> 
>
> More on templates and current tiddlers 
>  
> from 
> my TiddlyWiki textbook.
>  
>
>> Also, I've come across $:/tags/ViewTemplate which is only described as: 
>> "The system tag  
>> $:/tags/ViewTemplate marks the view template." which is not very telling.
>>
> I've done tenplates tgat work fine. They are not 
>> tagged $:/tags/ViewTemplate. If I tag them as scuch, they act aout as if 
>> their content was twice included. What does $:/tags/ViewTemplate really do? 
>> How should it be used?
>>
>
> Haha, some of those tag explanations could use some work. TiddlyWiki just 
> transcludes all the tiddlers with that tag in sequence when it is rendering 
> each tiddler:
>
> <$list
>  filter="[all[shadows+tiddlers]tag[$:/tags/ViewTemplate]!has[draft.of]]" 
> variable="listItem">
>   <$transclude tiddler=<>/>
> 
>
> So the view template is essentially a list of templates that get 
> *automatically* transcluded for every tiddler without mentioning them in 
> your wikitext. This includes things like the title, the tags bar, and so on.
>
> More on the view template 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dec36e17-504d-4b05-9e10-c7884c13b836n%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

2021-06-28 Thread stan...@gmail.com

You can add me to the list for the questionaire.  Streams is an excellent 
addition to TW.
Stan

On Monday, June 28, 2021 at 1:44:26 PM UTC-4 saq.i...@gmail.com wrote:

> @si
>  
>
>> I've also been considering asking for volunteers for a small group of 
>>> regular users of Streams for testing new features..
>>
>>
>> I'm happy to test stuff out as required.  
>>
>
> I think I will start out with a questionnaire and also use that as an 
> opportunity to ask for volunteers for testing.
>
> I will give some more thought to the breadcrumbs.
>
> Regards,
> Saq
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/eac0e923-ce9a-4590-ad49-a1a95d06ce74n%40googlegroups.com.

Re: [tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

2021-06-28 Thread Si

Ahh OK that shouldn't have confused me as much as it did...

>>> The problem is, that I would need to add a generic way. It may work for 
your, but an other user would probably have fun to link to [[foot]] ;) ... 

IMO this isn't that much of a problem. If the filter was added by the user, 
they would understand the limitations of it.

On Monday, 28 June 2021 at 23:41:39 UTC+1 PMario wrote:

> On Monday, June 28, 2021 at 9:13:16 PM UTC+2 Si wrote:
>
>> >>> The problem is, that I would need to add a generic way. It may work 
>> for your, but an other user would probably have fun to link to [[foot]] ;) 
>> ... 
>>
>> I'm not sure I understand what you are saying here! Is "[[foot]]" an 
>> autocorrect error?
>>
>
> foot -> feet ... It was just an example where a "hack" breaks down. 
>
> I was thinking about the "irregular" forms that are easy for humans but 
> problematic for algorithms. 
>
> -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/017cbcfb-c431-4b7c-8776-d9fd80a5e394n%40googlegroups.com.

Re: [tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

On Monday, June 28, 2021 at 9:13:16 PM UTC+2 Si wrote:

> >>> The problem is, that I would need to add a generic way. It may work 
> for your, but an other user would probably have fun to link to [[foot]] ;) 
> ... 
>
> I'm not sure I understand what you are saying here! Is "[[foot]]" an 
> autocorrect error?
>

foot -> feet ... It was just an example where a "hack" breaks down. 

I was thinking about the "irregular" forms that are easy for humans but 
problematic for algorithms. 

-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/b2e715f7-d342-4ec6-9395-abd2e53c03f4n%40googlegroups.com.

[tw5] Re: Discussion: Tiddler titles for sources

2021-06-28 Thread TiddlyTweeter

Interesting discussion.

Tiddler titles could be a problem, or not, depending on how you organise 
stuff. Take the case of William Empsom's SEVEN TYPES OF AMBIGUITY. There is 
the original 1930 edition, the 1947 2nd edition, the 1953 revised 2nd 
edition. There was also an American 1947 edition.

I am not fully sure this a TW issue, so much as a WHAT IS MY CITATION 
scheme? issue :-)

Just for fun it is worth noting that I could happily cite, via TW title 
"*{{EMP-30}} 
differs from {{EMP-47}}* "...

Isn't this just about getting to a convention and sticking to it? :-)

Happy scholar thoughts!
TT

On Monday, 28 June 2021 at 21:16:45 UTC+2 springer wrote:

> Si,
>
> Field name usage for bibliographic data is also a "live" problem for me. 
>
> I've recently gravitated toward approaching the title field with 
> author-date brevity, as is used in interlinear citation: *Beauvoir 1962* 
> (or *Beauvoir 1962b* in the rare case of multiple sources published from 
> same year).
>
> This pattern is easy to type, not terribly difficult to remember, and 
> generally steers clear of confusion for my purposes.
>
> On the other hand, if you like using the off-the-shelf sidebar search 
> function (as I do, especially if I publish for students), that may give you 
> a reason to stick with a longer concatenation: if the title field holds 
> *Beauvoir, 
> Ethics of Ambiguity (1962)* you can always easily find it even if you 
> only remember that the source has "ambiguity" in it. ;) 
>
> Either way, then I end up modifying various templates (including the 
> sidebar tabs) to show the caption field. Usually this will hold a version 
> of the author surname plus full primary title (omitting subtitle), *but* I 
> have the freedom to custom-abbreviate titles that are inconveniently long. 
> It's convenient to build filters that fetch one field value *if* it exists, 
> and to pull from a default field if not.)
>
> It's awkward that the fieldname "title" is not really workable for the 
> full title of the bibliographic source, since I like to use intuitive field 
> names. Using fieldnames like bibtex-title bibtex-year (etc) works ok when 
> field names are all hidden under the hood and handled through automated 
> imports and forms, etc. But they're a nuisance to type repeatedly, and 
> (worse for my purposes) they are bulky, and this becomes a problem in 
> dynamic tables (which auto-sizes columns so that the bibtex-year column is 
> twice as wide as the data needs).
>
> I actually wonder whether there already is -- or could be -- something 
> like an efficient sub-forum for people who are using TiddlyWiki in an 
> extensive way for bibliographic purposes. It's not always easy to go 
> searching through the google groups for relevant past posts, and I know 
> there have been a ton of them. There's great benefit to converging on 
> conventions together, since that way plugins, specialized ViewTemplates, 
> macros (etc.) can be shared easily.
>
> -Springer
> On Monday, June 28, 2021 at 12:51:05 PM UTC-4 Si wrote:
>
>> Hi all,
>>
>> I've been rethinking how I should name tiddlers that represent sources, 
>> and I'm interested in hearing the thoughts of other TiddlyWiki users.
>>
>> By sources I mean books, articles, movies etc. The crucial point here is 
>> that I am talking about things that have an 'official' name.
>>
>> Currently I use the 'official' title of the source, plus any extra 
>> information required to make it unique. For example:
>>
>> Books: The Fellowship of the Ring - J.R.R. Tolkien
>> Movies: The Lord of the Rings: The Fellowship of the Ring (2001)
>> Articles: The Role of Deliberate Practice in the Acquisition of Expert 
>> Performance (1993)
>>
>> In addition to this I might use a caption which displays a truncated 
>> version of the title when I cite the source in another tiddler, for example 
>> Ericsson-1993 or DeliberatePractice1993. 
>>
>> I was browsing Soren's Zettelkasten 
>>  and I noticed that he does 
>> things the opposite way around. He gives (usually) short CamelCase titles 
>> and relies on the caption field for the official name.
>>
>> I have been thinking about this and two possible advantages occur to me:
>>
>>- Shorter titles are quicker to type when linking from other tiddlers.
>>- More importantly, perhaps they are easier to remember, or 'lock 
>>onto'? For example I will probably more easily be able to pull 
>>"DeliberatePractice1993" from my brain than I would "The Role of 
>> Deliberate 
>>Practice..." This relates to titles functioning like APIs 
>>.
>>
>> Possible disadvantages:
>>
>>- They are likely harder to generate automatically from source 
>>metadata. This may not be a disadvantage, as perhaps there is a benefit 
>> to 
>>thinking up titles yourself.
>>- Even when coming up with titles yourself, it may be tricky to 
>>figure

Re: [tw5] NoteTaking in Streams

2021-06-28 Thread Steph Butera

Hi Saq, I'd also be happy to take part in the questionnaire. I use Streams 
daily and appreciate it very much.

All best,
Steph

On Monday, June 28, 2021 at 1:44:26 PM UTC-4 saq.i...@gmail.com wrote:

> @si
>  
>
>> I've also been considering asking for volunteers for a small group of 
>>> regular users of Streams for testing new features..
>>
>>
>> I'm happy to test stuff out as required.  
>>
>
> I think I will start out with a questionnaire and also use that as an 
> opportunity to ask for volunteers for testing.
>
> I will give some more thought to the breadcrumbs.
>
> Regards,
> Saq
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fc81fdea-f71a-48aa-8da4-aa9d01a12f76n%40googlegroups.com.

[tw5] Re: Discussion: Tiddler titles for sources

Si,

Field name usage for bibliographic data is also a "live" problem for me. 

I've recently gravitated toward approaching the title field with 
author-date brevity, as is used in interlinear citation: *Beauvoir 1962* 
(or *Beauvoir 1962b* in the rare case of multiple sources published from 
same year).

This pattern is easy to type, not terribly difficult to remember, and 
generally steers clear of confusion for my purposes.

On the other hand, if you like using the off-the-shelf sidebar search 
function (as I do, especially if I publish for students), that may give you 
a reason to stick with a longer concatenation: if the title field holds 
*Beauvoir, 
Ethics of Ambiguity (1962)* you can always easily find it even if you only 
remember that the source has "ambiguity" in it. ;) 

Either way, then I end up modifying various templates (including the 
sidebar tabs) to show the caption field. Usually this will hold a version 
of the author surname plus full primary title (omitting subtitle), *but* I 
have the freedom to custom-abbreviate titles that are inconveniently long. 
It's convenient to build filters that fetch one field value *if* it exists, 
and to pull from a default field if not.)

It's awkward that the fieldname "title" is not really workable for the full 
title of the bibliographic source, since I like to use intuitive field 
names. Using fieldnames like bibtex-title bibtex-year (etc) works ok when 
field names are all hidden under the hood and handled through automated 
imports and forms, etc. But they're a nuisance to type repeatedly, and 
(worse for my purposes) they are bulky, and this becomes a problem in 
dynamic tables (which auto-sizes columns so that the bibtex-year column is 
twice as wide as the data needs).

I actually wonder whether there already is -- or could be -- something like 
an efficient sub-forum for people who are using TiddlyWiki in an extensive 
way for bibliographic purposes. It's not always easy to go searching 
through the google groups for relevant past posts, and I know there have 
been a ton of them. There's great benefit to converging on conventions 
together, since that way plugins, specialized ViewTemplates, macros (etc.) 
can be shared easily.

-Springer
On Monday, June 28, 2021 at 12:51:05 PM UTC-4 Si wrote:

> Hi all,
>
> I've been rethinking how I should name tiddlers that represent sources, 
> and I'm interested in hearing the thoughts of other TiddlyWiki users.
>
> By sources I mean books, articles, movies etc. The crucial point here is 
> that I am talking about things that have an 'official' name.
>
> Currently I use the 'official' title of the source, plus any extra 
> information required to make it unique. For example:
>
> Books: The Fellowship of the Ring - J.R.R. Tolkien
> Movies: The Lord of the Rings: The Fellowship of the Ring (2001)
> Articles: The Role of Deliberate Practice in the Acquisition of Expert 
> Performance (1993)
>
> In addition to this I might use a caption which displays a truncated 
> version of the title when I cite the source in another tiddler, for example 
> Ericsson-1993 or DeliberatePractice1993. 
>
> I was browsing Soren's Zettelkasten 
>  and I noticed that he does 
> things the opposite way around. He gives (usually) short CamelCase titles 
> and relies on the caption field for the official name.
>
> I have been thinking about this and two possible advantages occur to me:
>
>- Shorter titles are quicker to type when linking from other tiddlers.
>- More importantly, perhaps they are easier to remember, or 'lock 
>onto'? For example I will probably more easily be able to pull 
>"DeliberatePractice1993" from my brain than I would "The Role of 
> Deliberate 
>Practice..." This relates to titles functioning like APIs 
>.
>
> Possible disadvantages:
>
>- They are likely harder to generate automatically from source 
>metadata. This may not be a disadvantage, as perhaps there is a benefit to 
>thinking up titles yourself.
>- Even when coming up with titles yourself, it may be tricky to figure 
>out a succinct way to represent sources with very long and complex titles, 
>for example these scientific papers 
>
> 
>.
>
> Anyway this is a fairly open ended post, but I'm wondering how people 
> approach naming sources in TiddlyWiki?
> How do you name source tiddlers, and why?
> Do you prefer to use 'official' names or to come up with your own?
>
> Please be free to comment with any thoughts you have relating this topic, 
> no matter how divergent!
>
>

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

Re: [tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

2021-06-28 Thread Si

>>> I did add a github issue: https://github.com/wikilabs/plugins/issues/101 
.. so it's not forgotten. 

Cool, thanks!

>>> The problem is, that I would need to add a generic way. It may work for 
your, but an other user would probably have fun to link to [[foot]] ;) ... 

I'm not sure I understand what you are saying here! Is "[[foot]]" an 
autocorrect error?

On Monday, 28 June 2021 at 17:37:35 UTC+1 PMario wrote:

> On Monday, June 28, 2021 at 5:49:48 PM UTC+2 Si wrote:
>
> For example take [[books|??]]. By default this will work as it currently 
>> does, but from a global config the user could add the filter 
>> trim:suffix[s]. This would be applied to [[books]] and then the result 
>> used as the search term. 
>>
>
> The problem is, that I would need to add a generic way. It may work for 
> your, but an other user would probably have fun to link to [[foot]] ;) ... 
>
> I AM thinking about the possibility to implement the link-search as a 
> macro. So it would be possible for users to modify the macro. And there 
> they can do what ever they want. .. It's their wiki ;) 
>
> But I think this won't be implemented in the near future, since it will 
> need a new "backlink" handling function, which I need to think about. 
>
> -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/01d8075c-fad1-4028-b686-b28b92337509n%40googlegroups.com.

Re: [tw5] Re: Artwork for v5.2.0

Jeremy,

I think your diagnosis is spot on: we have a collective surplus of 
enthusiastic creative energy from folks who would like to contribute to 
making TiddlyWiki intuitive, visible, and attractive. 

Those of us who have a deeper toolkit/skillset for graphics than for coding 
are especially eager to step up when there's a call for graphic design. The 
result is a level of detail-wrangling over a banner image that has a 
relatively limited role.

Something like a set of public ads would be a more substantive project. 
Presumably there should be at least something like thematic and stylistic 
coherence (which helps people recognize multiple ads as being about the 
same thing), but there are many possible ways to develop such coherence.

-Springer

On Monday, June 28, 2021 at 11:10:18 AM UTC-4 jeremy...@gmail.com wrote:

> Hi Springer
>
> One thing I find myself thinking when I look at the entries is that the 
> new release banner is a frustratingly constrained canvas for the creativity 
> that we see here. The purpose of the new release banner is just to brand 
> each released version, so that visitors to tiddlywiki.com can see the 
> version number at a glance in the splash screen and "HelloThere". So 
> really, the only requirement is that it displays the version number 
> clearly, and is visually distinctive from previous banners.
>
> Nonetheless, I think we'll continue to need a new release banner for each 
> version, but I wonder if we might have the bandwidth for another, ongoing 
> competition that gives contributors a bit more to get their teeth into. 
> Instead of posters, perhaps the designs could be banner advertisements of a 
> specified size: we could have fun imagining how we would advertise 
> TiddlyWiki in big media outlets like the New York Times, Instagram, Reddit 
> or Wired.
>
> We could also host the banner ads on tiddlywiki.com in such a way that 
> anyone who wanted to could add an iframe to their site to add a rotating 
> gallery of TiddlyWiki advertisements. (We would obviously do that without 
> any tracking).
>
> Best wishes
>
> Jeremy
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 28 Jun 2021, at 15:53, springer  wrote:
>
> 
>
> Dear all,
>
> The gallery  is now up to date 
> including James' latest submission with emoji. Of course, multi-submission 
> authors will need to winnow our offerings. 
>
> I'd love to hear more feedback in the spirit of what Télumire offered over 
> the weekend. 
>
> For what it's worth, the images chosen for version banners, up to now, are 
> remarkably heterogeneous -- there's no history of sticking to the fonts 
> used on tiddlywiki.com, nor to any particular palette, and even the 
> TiddlyWiki name was never part of the banner image until 5.1.23 (and 
> invoking a precedent for not using masks seems odd given the heterogeneity 
> of version banners, though I respect individual aesthetic reactions). If 
> there's some emerging consensus around any of these points, then I think 
> we'd all welcome reflections on such things.
>
> There's a delicate balance, in this open-source world between 
> volunteer/amateur enthusiasm and expertise. I love the spirit of this 
> banner image competition, and yet I also recognize that designers (such as 
> Duarte Farrajota Ramos, who won the poster competition 
> ) really do bring skills to the challenge 
> of communicating clearly and efficiently through images.
>
> In this spirit, it's worth reflecting further on the audience for this 
> (and other) TiddlyWiki imagery and publicity. Are we looking for images 
> that will feel accessible to those who know little about TiddlyWiki and its 
> innards, or are we aiming primarily to communicate with those who already 
> recognize JSON or curly brackets as familiar reference-points? 
>
> Both the puzzle-piece logo of 5.1.22 and the modular shape in Atro's 
> 5.1.23 image presuppose no programming-literacy. The JSON file-icon gesture 
> in Mohammad's entry seems to be at the other end of the spectrum: it surely 
> speaks clearly and elegantly to many users who are at home in code, but 
> perhaps at the risk of intimidating someone who is browsing for a free, 
> flexible, publishable and future-proof alternative to bloatware like 
> evernote, and who would be only slowly tempted to peek under the hood (or 
> "bonnet" for you Brits;) ).  
>
> What do you all think?
>
> -Springer
>
> On Saturday, June 26, 2021 at 11:45:11 AM UTC-4 Télumire wrote:
>
>> Hi everyone, here's my honest feedback, I hope it will be useful :
>>
>> springer 
>>  : 
>> love the simplicity of it. ... Color wise, I think it would be best to use 
>> the color palette of the vanilla TW... the font you used too... looks like 
>> it's not the default font used by TW. ... I personally don't like the 
>> masked versions. This makes

[tw5] Re: butlast filter operator

2021-06-28 Thread History Buff

Thanks!

On Monday, June 28, 2021 at 10:45:52 AM UTC-7 saq.i...@gmail.com wrote:

> This is essentially an oversight and will be fixed. Thank you for bringing 
> this up.
>
> https://github.com/Jermolene/TiddlyWiki5/issues/5833
>
> On Sunday, June 27, 2021 at 8:28:50 PM UTC+2 History Buff wrote:
>
>> All,
>>
>> I have a general question about the butlast filter operator. I had a 
>> filter where I had the butlast operator as the last item with a variable 
>> for the parameter. All worked fine until the variable was 0.  I expected 
>> that it wouldn't remove any of the last items, but what I got was no 
>> results at all. I fixed it be making sure that the variable was never 0, 
>> but I don't understand why a 0 in the butlast operator would yield no 
>> results. Can anyone explain that to me? 
>>
>> Thanks so much!
>>
>

-- 
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/c1368ed3-e471-42cb-a778-e21728c05be3n%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

2021-06-28 Thread Soren Bjornstad

Probably did, but right now that one is more or less just <> -- there's no special functionality for 
selecting questions out of the tiddlers. That's something I'd like to 
improve in the future.

On Monday, June 28, 2021 at 12:12:30 PM UTC-5 mark.cu...@gmail.com wrote:

> Is there any chance your filter missed the OpenQuestions tiddler as well?
>
> On Sunday, April 18, 2021 at 11:55:35 AM UTC-4 Soren Bjornstad wrote:
>
>> Looks like my filter missed the TODO tiddler, which should contain:
>>
>> \define todore() \[\[TODO\]\]:
>> \define splitre() [\.\?!]
>>
>> To add a TODO item to this list, simply link to [[TODO]].
>>
>> 
>> <$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer>
>>   <$list 
>> filter="[get[text]splitregexplast[]splitregexpfirst[]]"
>>  
>> variable=inner>
>>   <$link to=<>/>
>> ''TODO:'' <>.
>> 
>> 
>> 
>>
>> On Sunday, April 18, 2021 at 10:23:28 AM UTC-5 ludwa6 wrote:
>>
>>> Good to know, Soren, but first i have to get the basics under control, 
>>> like: TODO items!  
>>>
>>> About that, you say in your video at 28'47" 
>>>  : "*Anywhere that i write the 
>>> word todo in square brackets, so link to the tiddler todo, gets 
>>> automatically pulled in here"* -here being presumably TODO tab of 
>>> "Write" feature, since that is the context.  I have tried this a number of 
>>> ways -with square brackets of both types: single (would have to be by some 
>>> magic i don't see, but since you didn't say "DOUBLE"...) and double 
>>> (creating a missing tiddler, which i then activated, tagged "Stub"), 
>>> whether as TODO uppercase or lower... Nothing shows up as expected in that 
>>> tab, at all.
>>>
>>> So what am i missing here, i wonder?
>>>
>>> /walt
>>>
>>> On Sunday, April 18, 2021 at 3:31:11 PM UTC+1 Soren Bjornstad wrote:
>>>
 Oh, to convert a single-file wiki to Node.js, all you need is:

 tiddlywiki --load path/to/single/file.html --savewikifolder 
 path/to/output/folder

 You could even do this as a first step in the script above, if you 
 wanted to normally edit in single-file mode but use the automated build.

 On Sunday, April 18, 2021 at 9:02:28 AM UTC-5 ludwa6 wrote:

> Thank-you Soren, but to be clear: I'm working in single-file mode, 
> since i was unable to find a way to convert your file to node.js, though 
> that would probably make for a more elegant solution [*]... But the 
> "manual" method you propose below (with slight adaptation, see below) is 
> sufficiently well-automated, it makes my workflow relatively painless, as 
> follows:
>
>1. In TiddlyDesktop (where i am managing a fair mitt-full of TW5 
>instances), finish my days edits with a review to ensure tag "Public" 
> is on 
>all the right tiddlers, and none other;
>2. In $:/AdvancedSearch, run the filter-  
>[tag[Public]!is[system]]  -and upload the result set as .json, to...
>3. Drag & drop that .json file into the my local PUBLIC instance 
>(subset of the above), which is they synced to...
>4. My github.io repo  : pull from there 
>(just to ensure there are no conflicting edits), then 
> commit/comment/push 
>changes online.
>
> NB: I'm using Atom text editor (on Mac, b/t/w, not Windows) for the 
> last step, just because i like its change management workflow, but 
> there's 
> a desktop app for Github that is probably the most intuitive GuI app for 
> this purpose.
>
> [*] As to that more elegant solution: if it were a node.js instance i 
> had in github, then i can see how it might be easier to manage a dataflow 
> based on individual tiddlers, instead of one big .html file -especially 
> if 
> others were to be engaged in collaborative editing (via Github Pull 
> Request)... But that's a bridge too far for me to even think about at 
> this 
> point.  Gotta play with this for a while first IMCST (In My Copious Spare 
> Time -ha!), in the hope that it will at some point save me more time than 
> it costs me to manage it -the most important question to ask of any 
> database app, i guess, yes?
>
> /walt
>
>
> On Sunday, April 18, 2021 at 1:35:05 PM UTC+1 Soren Bjornstad wrote:
>
>> A manual option would be to go to $:/AdvancedSearch, type in the 
>> filter you want to export (e.g., [tag[Public]] [is[system]]), use the 
>> export button to the right of the search box to export as JSON, and then 
>> import that JSON file into a fresh empty.html and publish that HTML file.
>>
>> That said, since you are already using Node.js, automating this with 
>> "command-line voodoo" isn't that hard, and then it will do everything 
>> for 
>> you with one command, without a chance of making mistakes. Here's a 
>> simplified version of what I use. I'm guessing you're

[tw5] Re: butlast filter operator

2021-06-28 Thread Saq Imtiaz

This is essentially an oversight and will be fixed. Thank you for bringing 
this up.

https://github.com/Jermolene/TiddlyWiki5/issues/5833

On Sunday, June 27, 2021 at 8:28:50 PM UTC+2 History Buff wrote:

> All,
>
> I have a general question about the butlast filter operator. I had a 
> filter where I had the butlast operator as the last item with a variable 
> for the parameter. All worked fine until the variable was 0.  I expected 
> that it wouldn't remove any of the last items, but what I got was no 
> results at all. I fixed it be making sure that the variable was never 0, 
> but I don't understand why a 0 in the butlast operator would yield no 
> results. Can anyone explain that to me? 
>
> Thanks so much!
>

-- 
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/8671095c-6891-47c0-b2b9-979149a4af46n%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

2021-06-28 Thread Saq Imtiaz

@si
 

> I've also been considering asking for volunteers for a small group of 
>> regular users of Streams for testing new features..
>
>
> I'm happy to test stuff out as required.  
>

I think I will start out with a questionnaire and also use that as an 
opportunity to ask for volunteers for testing.

I will give some more thought to the breadcrumbs.

Regards,
Saq

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5d07bccc-60ad-4725-8d4b-fc1c1e7e2000n%40googlegroups.com.

Re: [tw5] Artwork for v5.2.0

2021-06-28 Thread Mohammad Rahmani

Hi Springer,
 Everything looks great! Thank you!



Best wishes
Mohammad


On Mon, Jun 28, 2021 at 6:51 PM springer  wrote:

> Mohammad,
>
> Thanks! Let me know, of course, if you'd prefer any tweaks to color,
> opacity, etc., or font choices within the icon part.
>
> -Springer
>
>
> On Sunday, June 27, 2021 at 11:27:52 PM UTC-4 Mohammad wrote:
>
>> Springer,
>>
>>  Many thanks! Your mockup is now great! I appreciate all your efforts
>> both for this mockup and also for hosting the competition art works!
>>  Kudos gos to you!
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Sun, Jun 27, 2021 at 9:32 PM springer  wrote:
>>
>>> I've tweaked a *bit* more, and added Mohammad's submission to our
>>> gallery at:
>>>
>>> https://tw-logo-contest.tiddlyhost.com/
>>>
>>> -Springer
>>>
>>> On Sunday, June 27, 2021 at 12:49:06 PM UTC-4 springer wrote:
>>>
 Hi all, I had an exchange with Mohammad about the actual graphic file,
 to which he does not have access.

 But the work was based on his own sketches, and it's not too hard to
 replicate after discovering that the font is open-source Saira (google
 font), apart from the curly brackets, whose font isn't yet clear to me. So
 here's a rough mockup of Mohammad's design, though I admit I haven't
 obsessed about replicating all the details:

 [image: Mohammad's JSON logo mockup.png]

 On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:

> Just to have a little fun in this competition!
>
> These are my designs, but I'm not sure if they are suitable for the
> new release logo!
>
> [image: image.png]
>
>
>
> [image: img_342_chrome.png]
>
>
> and also!
>
> [image: img_341_chrome.png]
>
>
>
>
> Best wishes
> Mohammad
>
>
> On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston 
> wrote:
>
>> This is to announce our regular competition for the artwork for the
>> next release of TiddlyWiki 5. The next release is planned to be called
>> v5.2.0, which requires a little explanation.
>>
>> We've bumped the minor version number because of a single very
>> important change: for the first time in a decade, we're changing the 
>> format
>> used to encode tiddlers into the HTML file.
>>
>> The new format is based on JSON, making it much easier to develop
>> tools that produce or consume TW5 standalone HTML files. While there is
>> some limited backwards compatibility, the developers of many existing 
>> tools
>> will need to make modifications to keep things working with v5.2.0.
>>
>> Hence the version number change: it's intended to make every
>> developer ask "Gosh, what could have changed to warrant such a big jump",
>> and helps us to make sure that the news of the change is promulgated as
>> widely and prominently as possible.
>>
>> The change also brings one big improvement for all users: field names
>> now have no restrictions on which characters can be used, and are
>> case-sensitive so that "MyField" is a valid fieldname, and refers to a
>> different field than "myfield" (just like tiddler titles). Finally, we 
>> can
>> have fields called "⛄️".
>>
>> These changes will be merged shortly, but in the meantime can be
>> inspected here:
>>
>> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>>
>> So, with that, back to the artwork competition. The task is to design
>> the banner image that is shown on the splash screen and within the 
>> opening
>> HelloThere tiddler. It is traditional for the artwork to reflect some of
>> the changes in the new version.
>>
>> The rules for the competition are:
>>
>> * The version number (with the correct punctuation) must be clear and
>> readable even when the banner is shown at a reduced size
>> * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
>> * The bottom 46 pixels will be obscured by the banner text “What’s
>> new in 5.2.0” when it is displayed within HelloThere
>> * Feel free to enter an updated version of artwork that was a
>> runner-up in a previous competition
>> * Reply to this message with your entry, or any questions
>>
>> Here are the posts about previous artwork competitions:
>>
>> v5.1.23 -
>> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>> v5.1.22 -
>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>> v5.1.21 -
>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>
>> If you’ve got a great idea for the banner image, but don’t have the
>> skills to produce finished artwork, do feel free to share your ideas in
>> case somebody else would like to work on the artwork.
>>
>> The competition will be open for a week, at which point if there is
>> more

[tw5] Re: A tour through my Zettelkasten

2021-06-28 Thread Mark Cubberley

Is there any chance your filter missed the OpenQuestions tiddler as well?

On Sunday, April 18, 2021 at 11:55:35 AM UTC-4 Soren Bjornstad wrote:

> Looks like my filter missed the TODO tiddler, which should contain:
>
> \define todore() \[\[TODO\]\]:
> \define splitre() [\.\?!]
>
> To add a TODO item to this list, simply link to [[TODO]].
>
> 
> <$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer>
>   <$list 
> filter="[get[text]splitregexplast[]splitregexpfirst[]]"
>  
> variable=inner>
>   <$link to=<>/>
> ''TODO:'' <>.
> 
> 
> 
>
> On Sunday, April 18, 2021 at 10:23:28 AM UTC-5 ludwa6 wrote:
>
>> Good to know, Soren, but first i have to get the basics under control, 
>> like: TODO items!  
>>
>> About that, you say in your video at 28'47" 
>>  : "*Anywhere that i write the word 
>> todo in square brackets, so link to the tiddler todo, gets automatically 
>> pulled in here"* -here being presumably TODO tab of "Write" feature, 
>> since that is the context.  I have tried this a number of ways -with square 
>> brackets of both types: single (would have to be by some magic i don't see, 
>> but since you didn't say "DOUBLE"...) and double (creating a missing 
>> tiddler, which i then activated, tagged "Stub"), whether as TODO uppercase 
>> or lower... Nothing shows up as expected in that tab, at all.
>>
>> So what am i missing here, i wonder?
>>
>> /walt
>>
>> On Sunday, April 18, 2021 at 3:31:11 PM UTC+1 Soren Bjornstad wrote:
>>
>>> Oh, to convert a single-file wiki to Node.js, all you need is:
>>>
>>> tiddlywiki --load path/to/single/file.html --savewikifolder 
>>> path/to/output/folder
>>>
>>> You could even do this as a first step in the script above, if you 
>>> wanted to normally edit in single-file mode but use the automated build.
>>>
>>> On Sunday, April 18, 2021 at 9:02:28 AM UTC-5 ludwa6 wrote:
>>>
 Thank-you Soren, but to be clear: I'm working in single-file mode, 
 since i was unable to find a way to convert your file to node.js, though 
 that would probably make for a more elegant solution [*]... But the 
 "manual" method you propose below (with slight adaptation, see below) is 
 sufficiently well-automated, it makes my workflow relatively painless, as 
 follows:

1. In TiddlyDesktop (where i am managing a fair mitt-full of TW5 
instances), finish my days edits with a review to ensure tag "Public" 
 is on 
all the right tiddlers, and none other;
2. In $:/AdvancedSearch, run the filter-  [tag[Public]!is[system]]  
-and upload the result set as .json, to...
3. Drag & drop that .json file into the my local PUBLIC instance 
(subset of the above), which is they synced to...
4. My github.io repo  : pull from there 
(just to ensure there are no conflicting edits), then 
 commit/comment/push 
changes online.

 NB: I'm using Atom text editor (on Mac, b/t/w, not Windows) for the 
 last step, just because i like its change management workflow, but there's 
 a desktop app for Github that is probably the most intuitive GuI app for 
 this purpose.

 [*] As to that more elegant solution: if it were a node.js instance i 
 had in github, then i can see how it might be easier to manage a dataflow 
 based on individual tiddlers, instead of one big .html file -especially if 
 others were to be engaged in collaborative editing (via Github Pull 
 Request)... But that's a bridge too far for me to even think about at this 
 point.  Gotta play with this for a while first IMCST (In My Copious Spare 
 Time -ha!), in the hope that it will at some point save me more time than 
 it costs me to manage it -the most important question to ask of any 
 database app, i guess, yes?

 /walt


 On Sunday, April 18, 2021 at 1:35:05 PM UTC+1 Soren Bjornstad wrote:

> A manual option would be to go to $:/AdvancedSearch, type in the 
> filter you want to export (e.g., [tag[Public]] [is[system]]), use the 
> export button to the right of the search box to export as JSON, and then 
> import that JSON file into a fresh empty.html and publish that HTML file.
>
> That said, since you are already using Node.js, automating this with 
> "command-line voodoo" isn't that hard, and then it will do everything for 
> you with one command, without a chance of making mistakes. Here's a 
> simplified version of what I use. I'm guessing you're using Windows, but 
> if 
> so and you have github.io set up, you probably already have Git for 
> Windows installed, which will be enough to run a Bash script like the one 
> below. Mac/Linux will run this script out of the box
>


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving

[tw5] Discussion: Tiddler titles for sources

2021-06-28 Thread Si

Hi all,

I've been rethinking how I should name tiddlers that represent sources, and
I'm interested in hearing the thoughts of other TiddlyWiki users.

By sources I mean books, articles, movies etc. The crucial point here is
that I am talking about things that have an 'official' name.

Currently I use the 'official' title of the source, plus any extra
information required to make it unique. For example:

Books: The Fellowship of the Ring - J.R.R. Tolkien
Movies: The Lord of the Rings: The Fellowship of the Ring (2001)
Articles: The Role of Deliberate Practice in the Acquisition of Expert
Performance (1993)

In addition to this I might use a caption which displays a truncated
version of the title when I cite the source in another tiddler, for example
Ericsson-1993 or DeliberatePractice1993.

I was browsing Soren's Zettelkasten
and I noticed that he does
things the opposite way around. He gives (usually) short CamelCase titles
and relies on the caption field for the official name.

I have been thinking about this and two possible advantages occur to me:

- Shorter titles are quicker to type when linking from other tiddlers.
- More importantly, perhaps they are easier to remember, or 'lock onto'?
For example I will probably more easily be able to pull
"DeliberatePractice1993" from my brain than I would "The Role of Deliberate
Practice..." This relates to titles functioning like APIs
.

Possible disadvantages:

- They are likely harder to generate automatically from source metadata.
This may not be a disadvantage, as perhaps there is a benefit to thinking
up titles yourself.
- Even when coming up with titles yourself, it may be tricky to figure
out a succinct way to represent sources with very long and complex titles,
for example these scientific papers

Anyway this is a fairly open ended post, but I'm wondering how people
approach naming sources in TiddlyWiki?
How do you name source tiddlers, and why?
Do you prefer to use 'official' names or to come up with your own?

Please be free to comment with any thoughts you have relating this topic,
no matter how divergent!

--
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/46b663d3-01b8-4abf-9e25-940dd681b466n%40googlegroups.com.

Re: [tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

I did add a github issue: https://github.com/wikilabs/plugins/issues/101 .. 
so it's not forgotten. 
-m
On Monday, June 28, 2021 at 6:37:35 PM UTC+2 PMario wrote:

> On Monday, June 28, 2021 at 5:49:48 PM UTC+2 Si wrote:
>
> For example take [[books|??]]. By default this will work as it currently 
>> does, but from a global config the user could add the filter 
>> trim:suffix[s]. This would be applied to [[books]] and then the result 
>> used as the search term. 
>>
>
> The problem is, that I would need to add a generic way. It may work for 
> your, but an other user would probably have fun to link to [[foot]] ;) ... 
>
> I AM thinking about the possibility to implement the link-search as a 
> macro. So it would be possible for users to modify the macro. And there 
> they can do what ever they want. .. It's their wiki ;) 
>
> But I think this won't be implemented in the near future, since it will 
> need a new "backlink" handling function, which I need to think about. 
>
> -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/955485e2-2a25-4aec-b24e-7c377be0c73en%40googlegroups.com.

Re: [tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

On Monday, June 28, 2021 at 5:49:48 PM UTC+2 Si wrote:

For example take [[books|??]]. By default this will work as it currently 
> does, but from a global config the user could add the filter 
> trim:suffix[s]. This would be applied to [[books]] and then the result 
> used as the search term. 
>

The problem is, that I would need to add a generic way. It may work for 
your, but an other user would probably have fun to link to [[foot]] ;) ... 

I AM thinking about the possibility to implement the link-search as a 
macro. So it would be possible for users to modify the macro. And there 
they can do what ever they want. .. It's their wiki ;) 

But I think this won't be implemented in the near future, since it will 
need a new "backlink" handling function, which I need to think about. 

-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/4e26e04b-72c8-4080-b97e-2deb6a3eb84cn%40googlegroups.com.

Re: [tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

2021-06-28 Thread Si Si

Hi Mario, thanks for the response.

There is a little work around, that looks a bit strange. eg: I found some
> [[book|??]]s.   So the link will only cover the book text. I know that's
> not pretty but it creates valid sentences.


Thanks, this is probably the best workaround.

The question is interesting and valid, and it seems to be an easy change.
> .. But due to its language specific nature, it isn't. Implementing it will
> probably double the actual complexity of the plugin.


Of course - I was not expecting there to be an easy way to build this into
the plugin. I just wondered if there was an easy way to hack it.

Having said that, I did have an idea. Not sure if it makes sense or not,
but I'll put it out there: You could allow users to add an optional filter
expression to be applied to the search term before it is used.

For example take [[books|??]]. By default this will work as it currently
does, but from a global config the user could add the filter trim:suffix[s].
This would be applied to [[books]] and then the result used as the search
term.

Although I think this would largely solve my problem, I'm not sure how
useful it would be in general, but I thought I'd put it out there.

On Mon, 28 Jun 2021 at 07:37, PMario  wrote:

> On Sunday, June 27, 2021 at 10:58:41 PM UTC+2 Si wrote:
> ...
>
>> I only just noticed your Uni-link Search feature! Very handy -  I have
>> been frequently writing things like [[really good idea|Really Good Ideas]],
>> so this will save me a lot of time.
>>
>
> There is a little work around, that looks a bit strange. eg: I found some
> [[book|??]]s.   So the link will only cover the book text. I know that's
> not pretty but it creates valid sentences.
>
> The second workflow that works immediately is: *using aliases* eg: The
> "Books" tiddler gets 2 of them "book" and "books" may be [[new books]] and
> so on  Use *[[book|?]] or [[books|?]]* problem solved.
>
>
>> I have a question however: Is there any way to customise exactly how the
>> search is applied?
>>
>
> At the moment - no. ... The function is executed directly in javascript.
>
>
>> I'm wondering if there is a way to use Uni-link search, but tweak it so
>> it will ignore the final "s"? So [[books|??]] would automatically link to
>> [[Book]].
>>
>
> The main problem is, that singular / plural rules depend on the language.
> book - books in German is Buch - Bücher
> So a hardcoded rule won't help the plugin.
>
> The second problem is, that it has to work in both directions. So imo a
> link like [[books|??]] needs to search for "book" and "books"  ...
> [[book|??]] has to do the same thing. ... This will make the search
> function 50% slower :/
>
> It would be possible to implement "plural" / "singular" filter rules. But
> they will be language specific. Some 3rd party libraries will be needed. So
> there would be an additional plugin per language.
>
> UNI-LINK alias already uses macros instead of hardcoded links. ... but at
> the moment link-search outputs a "link", so the built-in "backlinks"
> handling works. If link-search would output a macro, a new "backlinks"
> handling will be needed. :/  I know how to do it, but it would add extra
> complexity.
>
> The re-link plugin is very popular and I try to keep uni-link compatible
> with it. IMO the singular / plural links will definitely be out of the
> scope, what re-link should handle. ...
>
> The question is interesting and valid, and it seems to be an easy change.
> .. But due to its language specific nature, it isn't. Implementing it will
> probably double the actual complexity of the plugin.
>
> So all in all using aliases instead of link-search will win in terms of
> simplicity. .. And aliases don't need language specific plugins ..
>
> hope that helps
> mario
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/35_6ltCXEvs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/a68737d8-c2ab-457d-91c8-d0942d696133n%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/CAKKx7WYXyz8YA3JZeZt5%3DwRnPhh-JWeybSAZYGqRVmEWxvsxxA%40mail.gmail.com.

Re: [tw5] Re: Artwork for v5.2.0

2021-06-28 Thread Jeremy Ruston

Hi Springer

One thing I find myself thinking when I look at the entries is that the new 
release banner is a frustratingly constrained canvas for the creativity that we 
see here. The purpose of the new release banner is just to brand each released 
version, so that visitors to tiddlywiki.com can see the version number at a 
glance in the splash screen and "HelloThere". So really, the only requirement 
is that it displays the version number clearly, and is visually distinctive 
from previous banners.

Nonetheless, I think we'll continue to need a new release banner for each 
version, but I wonder if we might have the bandwidth for another, ongoing 
competition that gives contributors a bit more to get their teeth into. Instead 
of posters, perhaps the designs could be banner advertisements of a specified 
size: we could have fun imagining how we would advertise TiddlyWiki in big 
media outlets like the New York Times, Instagram, Reddit or Wired.

We could also host the banner ads on tiddlywiki.com in such a way that anyone 
who wanted to could add an iframe to their site to add a rotating gallery of 
TiddlyWiki advertisements. (We would obviously do that without any tracking).

Best wishes

Jeremy

--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 28 Jun 2021, at 15:53, springer  wrote:
> 
> 
> Dear all,
> 
> The gallery is now up to date including James' latest submission with emoji. 
> Of course, multi-submission authors will need to winnow our offerings. 
> 
> I'd love to hear more feedback in the spirit of what Télumire offered over 
> the weekend. 
> 
> For what it's worth, the images chosen for version banners, up to now, are 
> remarkably heterogeneous -- there's no history of sticking to the fonts used 
> on tiddlywiki.com, nor to any particular palette, and even the TiddlyWiki 
> name was never part of the banner image until 5.1.23 (and invoking a 
> precedent for not using masks seems odd given the heterogeneity of version 
> banners, though I respect individual aesthetic reactions). If there's some 
> emerging consensus around any of these points, then I think we'd all welcome 
> reflections on such things.
> 
> There's a delicate balance, in this open-source world between 
> volunteer/amateur enthusiasm and expertise. I love the spirit of this banner 
> image competition, and yet I also recognize that designers (such as Duarte 
> Farrajota Ramos, who won the poster competition) really do bring skills to 
> the challenge of communicating clearly and efficiently through images.
> 
> In this spirit, it's worth reflecting further on the audience for this (and 
> other) TiddlyWiki imagery and publicity. Are we looking for images that will 
> feel accessible to those who know little about TiddlyWiki and its innards, or 
> are we aiming primarily to communicate with those who already recognize JSON 
> or curly brackets as familiar reference-points? 
> 
> Both the puzzle-piece logo of 5.1.22 and the modular shape in Atro's 5.1.23 
> image presuppose no programming-literacy. The JSON file-icon gesture in 
> Mohammad's entry seems to be at the other end of the spectrum: it surely 
> speaks clearly and elegantly to many users who are at home in code, but 
> perhaps at the risk of intimidating someone who is browsing for a free, 
> flexible, publishable and future-proof alternative to bloatware like 
> evernote, and who would be only slowly tempted to peek under the hood (or 
> "bonnet" for you Brits;) ).  
> 
> What do you all think?
> 
> -Springer
> 
>> On Saturday, June 26, 2021 at 11:45:11 AM UTC-4 Télumire wrote:
>> Hi everyone, here's my honest feedback, I hope it will be useful :
>> 
>> springer : love the simplicity of it. ... Color wise, I think it would be 
>> best to use the color palette of the vanilla TW... the font you used too... 
>> looks like it's not the default font used by TW. ... I personally don't like 
>> the masked versions. This makes the logo trapped into a shape, while all the 
>> previous splash screens (that I know of) were either rectangular or open. ...
>> 
 
> 
> -- 
> 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/2a2c04a5-4276-4544-bd68-fadf307b1b89n%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/500F65E6-3E2E-42FE-BB7F-3E96C85E85C9%40gmail.com.

Re: [tw5] Re: Artwork for v5.2.0

Dear all,

The gallery  is now up to date 
including James' latest submission with emoji. Of course, multi-submission 
authors will need to winnow our offerings. 

I'd love to hear more feedback in the spirit of what Télumire offered over 
the weekend. 

For what it's worth, the images chosen for version banners, up to now, are 
remarkably heterogeneous -- there's no history of sticking to the fonts 
used on tiddlywiki.com, nor to any particular palette, and even the 
TiddlyWiki name was never part of the banner image until 5.1.23 (and 
invoking a precedent for not using masks seems odd given the heterogeneity 
of version banners, though I respect individual aesthetic reactions). If 
there's some emerging consensus around any of these points, then I think 
we'd all welcome reflections on such things.

There's a delicate balance, in this open-source world between 
volunteer/amateur enthusiasm and expertise. I love the spirit of this 
banner image competition, and yet I also recognize that designers (such as 
Duarte Farrajota Ramos, who won the poster competition 
) really do bring skills to the challenge 
of communicating clearly and efficiently through images.

In this spirit, it's worth reflecting further on the audience for this (and 
other) TiddlyWiki imagery and publicity. Are we looking for images that 
will feel accessible to those who know little about TiddlyWiki and its 
innards, or are we aiming primarily to communicate with those who already 
recognize JSON or curly brackets as familiar reference-points? 

Both the puzzle-piece logo of 5.1.22 and the modular shape in Atro's 5.1.23 
image presuppose no programming-literacy. The JSON file-icon gesture in 
Mohammad's entry seems to be at the other end of the spectrum: it surely 
speaks clearly and elegantly to many users who are at home in code, but 
perhaps at the risk of intimidating someone who is browsing for a free, 
flexible, publishable and future-proof alternative to bloatware like 
evernote, and who would be only slowly tempted to peek under the hood (or 
"bonnet" for you Brits;) ).  

What do you all think?

-Springer

On Saturday, June 26, 2021 at 11:45:11 AM UTC-4 Télumire wrote:

> Hi everyone, here's my honest feedback, I hope it will be useful :
>
> springer 
>  : 
> love the simplicity of it. ... Color wise, I think it would be best to use 
> the color palette of the vanilla TW... the font you used too... looks like 
> it's not the default font used by TW. ... I personally don't like the 
> masked versions. This makes the logo trapped into a shape, while all the 
> previous splash screens (that I know of) were either rectangular or open. 
> ...
>
>>
>>>

-- 
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/2a2c04a5-4276-4544-bd68-fadf307b1b89n%40googlegroups.com.

Re: [tw5] Re: butlast filter operator

2021-06-28 Thread Damon Pritchett

Hey Tony,

Yeah that’s what I eventually realized so I changed what happens when I
reach zero. I was just wanting to understand the inner workings better.

On Mon, Jun 28, 2021 at 7:34 AM TW Tones  wrote:

> Another way to look at it ;
> Butlast purpose discard the last N input title(s)
>
> So saying  "discard the last 0 input titles" is non sensical
> If you actually want to discard 3, then 2 then 1 perhaps you filter needs
> find another way once it reaches 0
>
> Tones
> On Monday, 28 June 2021 at 13:07:37 UTC+10 History Buff wrote:
>
>> Thanks Eric,
>>
>> I appreciate that. I looked at it, but I really don’t know JavaScript.
>> Makes me want to learn though.
>>
>>
>>
>> On Sun, Jun 27, 2021 at 12:07 PM Eric Shulman  wrote:
>>
>>> On Sunday, June 27, 2021 at 11:28:50 AM UTC-7 History Buff wrote:
>>>
 I don't understand why a 0 in the butlast operator would yield no
 results

>>>
>>> The butlast[] operator is defined in this shadow tiddler:
>>> https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Ffilters%2Flistops.js
>>>
>>> Here's the javascript code from that tiddler:
>>> exports.butlast = function(source,operator,options) {
>>> var count = $tw.utils.getInt(operator.operand,1),
>>> results = [];
>>> source(function(tiddler,title) {
>>> results.push(title);
>>> });
>>> return results.slice(0,-count);
>>> };
>>>
>>> The first line gets the operand value, defaulting to 1.
>>> The next 4 lines copy the entire list of items into a results array
>>> The last line uses the javascript slice() function to remove items from
>>> the results array and then return that array
>>>
>>> Here's the documentation for the javascript slice() function:
>>>
>>> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/slice
>>>
>>> Note the description of the "end" parameter:
>>> Zero-based index before which to end extraction. slice extracts up to *but
>>> not including* end.
>>>
>>> Thus, when you used butlast[0], the filter code invokes slice(0,-0),
>>> i.e., "*starting from the first item up to but not including the first
>>> item*"
>>> which results in *no items* being returned.
>>>
>>> enjoy,
>>> -e
>>>
>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "TiddlyWiki" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/tiddlywiki/lROJc--2xFI/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> tiddlywiki+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/c1f40a73-746d-4c39-89b9-6786c9caee0fn%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/lROJc--2xFI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/faaa280d-a866-47d3-abef-5ec8e51e5d5dn%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/CAD1WRcbRkWRSjCp3Wi6Zjpq_q8Y8ZoVGU%2BoQ9DW%3D_9Fa%2Bjq%3D4w%40mail.gmail.com.

Re: [tw5] Re: butlast filter operator

Another way to look at it ;  
Butlast purpose discard the last N input title(s)

So saying  "discard the last 0 input titles" is non sensical 
If you actually want to discard 3, then 2 then 1 perhaps you filter needs 
find another way once it reaches 0

Tones
On Monday, 28 June 2021 at 13:07:37 UTC+10 History Buff wrote:

> Thanks Eric,
>
> I appreciate that. I looked at it, but I really don’t know JavaScript. 
> Makes me want to learn though. 
>
>
>
> On Sun, Jun 27, 2021 at 12:07 PM Eric Shulman  wrote:
>
>> On Sunday, June 27, 2021 at 11:28:50 AM UTC-7 History Buff wrote:
>>
>>> I don't understand why a 0 in the butlast operator would yield no results
>>>
>>
>> The butlast[] operator is defined in this shadow tiddler:
>> https://tiddlywiki.com/#%24%3A%2Fcore%2Fmodules%2Ffilters%2Flistops.js
>>
>> Here's the javascript code from that tiddler:
>> exports.butlast = function(source,operator,options) {
>> var count = $tw.utils.getInt(operator.operand,1),
>> results = [];
>> source(function(tiddler,title) {
>> results.push(title);
>> });
>> return results.slice(0,-count);
>> };
>>
>> The first line gets the operand value, defaulting to 1.
>> The next 4 lines copy the entire list of items into a results array
>> The last line uses the javascript slice() function to remove items from 
>> the results array and then return that array
>>
>> Here's the documentation for the javascript slice() function:
>>
>> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/slice
>>
>> Note the description of the "end" parameter:
>> Zero-based index before which to end extraction. slice extracts up to *but 
>> not including* end.
>>
>> Thus, when you used butlast[0], the filter code invokes slice(0,-0),
>> i.e., "*starting from the first item up to but not including the first 
>> item*"
>> which results in *no items* being returned.
>>
>> enjoy,
>> -e
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/lROJc--2xFI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/c1f40a73-746d-4c39-89b9-6786c9caee0fn%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/faaa280d-a866-47d3-abef-5ec8e51e5d5dn%40googlegroups.com.

[tw5] Re: details tag and wiki interpretation

Eric,

I noticed this today, and wonder if a behaviour has changed;

Never the less we can add a style to the div like this;

Quick Access


* one of many 
* two of many
...



Which helps save space
Tones
On Monday, 28 June 2021 at 22:02:21 UTC+10 Eric Shulman wrote:

> On Monday, June 28, 2021 at 4:49:46 AM UTC-7 jn.pierr...@gmail.com wrote:
>
>> I've got a perfectly all right tiddler content with something like an 
>> ordered list in wiki syntax.
>> Then I've decided to have that part within a html details markup. The 
>> problem is, the wiki syntax is no more producing a list.
>>
>
> The  element seems to be "eating" the newline that is required to 
> precede the wikitext ordered list syntax.
> To work around this, wrap your ordered list within a ... 
> element, like this:
>
> 
> fubaring
> 
>
> # foo
> # bar
> 
>  
>
> Note that the newline preceding the first # item is necessary to ensure 
> "block mode" parsing of the ordered list.
>
> 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/8de78b58-ee2f-4494-ae43-8a2d09462709n%40googlegroups.com.

Re: [tw5] Artwork for v5.2.0

Mohammad,

Thanks! Let me know, of course, if you'd prefer any tweaks to color, 
opacity, etc., or font choices within the icon part.

-Springer


On Sunday, June 27, 2021 at 11:27:52 PM UTC-4 Mohammad wrote:

> Springer,
>
>  Many thanks! Your mockup is now great! I appreciate all your efforts both 
> for this mockup and also for hosting the competition art works!
>  Kudos gos to you!
>
>
> Best wishes
> Mohammad
>
>
> On Sun, Jun 27, 2021 at 9:32 PM springer  wrote:
>
>> I've tweaked a *bit* more, and added Mohammad's submission to our gallery 
>> at:
>>
>> https://tw-logo-contest.tiddlyhost.com/
>>
>> -Springer
>>
>> On Sunday, June 27, 2021 at 12:49:06 PM UTC-4 springer wrote:
>>
>>> Hi all, I had an exchange with Mohammad about the actual graphic file, 
>>> to which he does not have access.
>>>
>>> But the work was based on his own sketches, and it's not too hard to 
>>> replicate after discovering that the font is open-source Saira (google 
>>> font), apart from the curly brackets, whose font isn't yet clear to me. So 
>>> here's a rough mockup of Mohammad's design, though I admit I haven't 
>>> obsessed about replicating all the details:
>>>
>>> [image: Mohammad's JSON logo mockup.png]
>>>
>>> On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:
>>>
 Just to have a little fun in this competition!

 These are my designs, but I'm not sure if they are suitable for the new 
 release logo! 

 [image: image.png]



 [image: img_342_chrome.png]


 and also!

 [image: img_341_chrome.png]




 Best wishes
 Mohammad


 On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston  
 wrote:

> This is to announce our regular competition for the artwork for the 
> next release of TiddlyWiki 5. The next release is planned to be called 
> v5.2.0, which requires a little explanation.
>
> We've bumped the minor version number because of a single very 
> important change: for the first time in a decade, we're changing the 
> format 
> used to encode tiddlers into the HTML file.
>
> The new format is based on JSON, making it much easier to develop 
> tools that produce or consume TW5 standalone HTML files. While there is 
> some limited backwards compatibility, the developers of many existing 
> tools 
> will need to make modifications to keep things working with v5.2.0.
>
> Hence the version number change: it's intended to make every developer 
> ask "Gosh, what could have changed to warrant such a big jump", and helps 
> us to make sure that the news of the change is promulgated as widely and 
> prominently as possible.
>
> The change also brings one big improvement for all users: field names 
> now have no restrictions on which characters can be used, and are 
> case-sensitive so that "MyField" is a valid fieldname, and refers to a 
> different field than "myfield" (just like tiddler titles). Finally, we 
> can 
> have fields called "⛄️".
>
> These changes will be merged shortly, but in the meantime can be 
> inspected here:
>
> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>
> So, with that, back to the artwork competition. The task is to design 
> the banner image that is shown on the splash screen and within the 
> opening 
> HelloThere tiddler. It is traditional for the artwork to reflect some of 
> the changes in the new version.
>
> The rules for the competition are:
>
> * The version number (with the correct punctuation) must be clear and 
> readable even when the banner is shown at a reduced size
> * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
> * The bottom 46 pixels will be obscured by the banner text “What’s new 
> in 5.2.0” when it is displayed within HelloThere
> * Feel free to enter an updated version of artwork that was a 
> runner-up in a previous competition
> * Reply to this message with your entry, or any questions
>
> Here are the posts about previous artwork competitions:
>
> v5.1.23 - 
> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
> v5.1.22 - 
> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
> v5.1.21 - 
> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>
> If you’ve got a great idea for the banner image, but don’t have the 
> skills to produce finished artwork, do feel free to share your ideas in 
> case somebody else would like to work on the artwork.
>
> The competition will be open for a week, at which point if there is 
> more than one submission I’ll set up a Google Form for voting.
>
> Best wishes and many thanks,
>
> Jeremy
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
 -- 
>

[tw5] Re: template: where is the widget???

2021-06-28 Thread Soren Bjornstad


>
> I've read in the doc that widgets are the fundamental part of tiddlywiki 
> and that all wiki syntax sugar is finally resolved as a number of widgets.
>
> Use of template is only described with transclusion as {{||template}} 
> (with tiddler or field or index before ||).
>
> the transclude widget has no template attribute.
>
> How then is done the transclusion? Shouldn't the transclude widget have a 
> template attribute?
>

Actually, the *template *is what's being transcluded during a transclusion, 
not the tiddler. When you transclude a tiddler through a template, the 
current tiddler is set to that tiddler and then the template is transcluded.

{{Tiddler||Template}} evaluates to:

<$tiddler tiddler=Tiddler>
  <$transclude tiddler=Template/>


{{||Template}} doesn't change the current tiddler and so evaluates to 
simply:

<$transclude tiddler=Template/>

{{Tiddler1}} is shorthand for {{Tiddler1||Tiddler1}}, and evaluates to:

<$tiddler tiddler=Tiddler1>
  <$transclude tiddler=Tiddler1/>


More on templates and current tiddlers 
 
from 
my TiddlyWiki textbook.
 

> Also, I've come across $:/tags/ViewTemplate which is only described as: 
> "The system tag  $:/tags/ViewTemplate 
> marks the view template." which is not very telling.
>
I've done tenplates tgat work fine. They are not 
> tagged $:/tags/ViewTemplate. If I tag them as scuch, they act aout as if 
> their content was twice included. What does $:/tags/ViewTemplate really do? 
> How should it be used?
>

Haha, some of those tag explanations could use some work. TiddlyWiki just 
transcludes all the tiddlers with that tag in sequence when it is rendering 
each tiddler:

<$list
 filter="[all[shadows+tiddlers]tag[$:/tags/ViewTemplate]!has[draft.of]]" 
variable="listItem">
  <$transclude tiddler=<>/>


So the view template is essentially a list of templates that get 
*automatically* transcluded for every tiddler without mentioning them in 
your wikitext. This includes things like the title, the tags bar, and so on.

More on the view template 
.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/bf3dcb60-76bd-4685-a4fd-643418e3d8c5n%40googlegroups.com.

[tw5] Re: using negative values

Mohamed,

Negative values may not always be valid but you example has a space between 
the sigh + or - and the number. Make it part of the number with no gap. -4 
NOT - 4

Regards
Tones

On Monday, 28 June 2021 at 23:12:26 UTC+10 mohamed...@hotmail.com wrote:

>
> Hi ,
>
> i have a field that has a number value  referenced in a mathematical 
> operation
>
> now I need to use a negative number  , like say - 4  
>
> if i write the number  like that ,the mathematical operation does not work 
> and does not pick up on the number 
>
> is there a specific format for using negative values ?
>
>
>

-- 
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/5505f1cc-c367-4024-bfce-160199a8c6ban%40googlegroups.com.

[tw5] Re: template: where is the widget???

Jean-Pierre,

The word template is over used in tiddlywiki, mostly because of the many 
ways to do templating. There are more possible than the common ones.

   - {{tiddlername}} is like incorporating content from a template 
   containing text or code
   - {{||tiddlername}} says display tiddler name here, with the current 
   tiddler as the underlying content ie; use the current text and fields title 
   etc...
   - These are in fact just a short hand for transclusion see the 
   <$transclued widget for the long hand form, the transclude say apply this 
   tiddler here, ie use it as a template.
   - Tagging a tiddler with $:/tags/viewTemplate says please use this in 
   the core template called  "viewTemplate" as you view each tiddler, the 
   viewTemplate is a special template
   - Tagging a tiddler with $:/tags/editTemplate says please use this in 
   the  template called  "editTemplate" as you edit each tiddler , the 
   editTemplate is a special template
   - In fact in many ways macros are almost identical. When you use a macro 
   its contents are pulled into the location where you use it.
   - Then after all your content development the finial result is 
   transcluded, expanded, rendered, processed and displayed according to what 
   you asked for.

In some ways it is best to return to the English definition of template;

*A template is a form, mold, or pattern used as a guide to making 
something. Here are some examples: A ruler is a template when used to draw 
a straight line. A document in which the standard opening and closing parts 
are already filled in is a template that you can copy and then fill in the 
variable parts.*

In some ways, in code and tiddlywiki a template is simply a piece of 
reusable content. Almost everything is reusable in tiddler wiki, so almost 
everything can be used as a template.

Widgets on the other hand are very similar to html tags eg; List 
item or  but the $ indicates you are referring to a 
<$widgetname/> and like html it can have attributes which are effectively 
the parameters to the widget. Widgets are the tiddlywiki way to introduce 
code such as html may use javascript. In fact most widgets are javascript 
but with one special feature, they honor the structure of tiddlywiki, they 
do what they do but in a way the whole wiki knows how to handle changes to 
itself, it is this magic ingredient that makes a wiki so interactive, 
always up to date and maintains the user interface. Widgets are a way to 
transclude functional code in your tiddlers.

I hope this clarifies things a little.

Topes
On Monday, 28 June 2021 at 21:39:22 UTC+10 jn.pierr...@gmail.com wrote:

> Hi!
>
> I've read in the doc that widgets are the fundamental part of tiddlywiki 
> and that all wiki syntax sugar is finally resolved as a number of widgets.
>
> Use of template is only described with transclusion as {{||template}} 
> (with tiddler or field or index before ||).
>
> the transclude widget has no template attribute.
>
> How then is done the transclusion? Shouldn't the transclude widget have a 
> template attribute?
>
> Also, I've come across $:/tags/ViewTemplate which is only described as: 
> "The system tag  $:/tags/ViewTemplate 
> marks the view template." which is not very telling.
>
> I've done tenplates tgat work fine. They are not 
> tagged $:/tags/ViewTemplate. If I tag them as scuch, they act aout as if 
> their content was twice included. What does $:/tags/ViewTemplate really do? 
> How should it be used?
>
> Regards,
>
> -- 
> Jean-Pierre
>
>
>
>
>
>

-- 
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/4b26d05d-16df-429f-a4f1-7098184a87ben%40googlegroups.com.

[tw5] using negative values

2021-06-28 Thread paulgilbert2000


Hi ,

i have a field that has a number value  referenced in a mathematical 
operation

now I need to use a negative number  , like say - 4  

if i write the number  like that ,the mathematical operation does not work 
and does not pick up on the number 

is there a specific format for using negative values ?


-- 
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/ca7f6907-cbed-44d8-887c-5c8b166c9d8en%40googlegroups.com.

[tw5] Re: details tag and wiki interpretation

Thank you Eric. And ... does work too. Nice trick!

Le lundi 28 juin 2021 à 14:20:53 UTC+2, David Gifford a écrit :

> A span works just as well. Blessings.
>
> On Monday, June 28, 2021 at 7:02:21 AM UTC-5 Eric Shulman wrote:
>
>> On Monday, June 28, 2021 at 4:49:46 AM UTC-7 jn.pierr...@gmail.com wrote:
>>
>>> I've got a perfectly all right tiddler content with something like an 
>>> ordered list in wiki syntax.
>>> Then I've decided to have that part within a html details markup. The 
>>> problem is, the wiki syntax is no more producing a list.
>>>
>>
>> The  element seems to be "eating" the newline that is required 
>> to precede the wikitext ordered list syntax.
>> To work around this, wrap your ordered list within a ... 
>> element, like this:
>>
>> 
>> fubaring
>> 
>>
>> # foo
>> # bar
>> 
>>  
>>
>> Note that the newline preceding the first # item is necessary to ensure 
>> "block mode" parsing of the ordered list.
>>
>> 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/74dfc343-e1fe-4436-8096-8c9edf03cf44n%40googlegroups.com.

[tw5] Re: details tag and wiki interpretation

2021-06-28 Thread David Gifford

A span works just as well. Blessings.

On Monday, June 28, 2021 at 7:02:21 AM UTC-5 Eric Shulman wrote:

> On Monday, June 28, 2021 at 4:49:46 AM UTC-7 jn.pierr...@gmail.com wrote:
>
>> I've got a perfectly all right tiddler content with something like an 
>> ordered list in wiki syntax.
>> Then I've decided to have that part within a html details markup. The 
>> problem is, the wiki syntax is no more producing a list.
>>
>
> The  element seems to be "eating" the newline that is required to 
> precede the wikitext ordered list syntax.
> To work around this, wrap your ordered list within a ... 
> element, like this:
>
> 
> fubaring
> 
>
> # foo
> # bar
> 
>  
>
> Note that the newline preceding the first # item is necessary to ensure 
> "block mode" parsing of the ordered list.
>
> 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/590dc823-e2a1-483b-a13d-48c997cffcfen%40googlegroups.com.

[tw5] Re: details tag and wiki interpretation

2021-06-28 Thread Eric Shulman

On Monday, June 28, 2021 at 4:49:46 AM UTC-7 jn.pierr...@gmail.com wrote:

> I've got a perfectly all right tiddler content with something like an 
> ordered list in wiki syntax.
> Then I've decided to have that part within a html details markup. The 
> problem is, the wiki syntax is no more producing a list.
>

The  element seems to be "eating" the newline that is required to 
precede the wikitext ordered list syntax.
To work around this, wrap your ordered list within a ... 
element, like this:

fubaring

# foo
# bar

Note that the newline preceding the first # item is necessary to ensure 
"block mode" parsing of the ordered list.

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/31120e78-6269-4351-9163-5a74dcab3230n%40googlegroups.com.

[tw5] details tag and wiki interpretation

Hi!

I've got a perfectly all right tiddler content with something like an 
ordered list in wiki syntax.

Then I've decided to have that part within a html details markup. The 
problem is, the wiki syntax is no more producing a list.

for instane my wiki code would be


fubaring

# foo
# bar



see image

[image: details-bug.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/9d94e874-2ba3-4af3-bb56-1abbbc336cc6n%40googlegroups.com.

[tw5] template: where is the widget???

Hi!

I've read in the doc that widgets are the fundamental part of tiddlywiki 
and that all wiki syntax sugar is finally resolved as a number of widgets.

Use of template is only described with transclusion as {{||template}} (with 
tiddler or field or index before ||).

the transclude widget has no template attribute.

How then is done the transclusion? Shouldn't the transclude widget have a 
template attribute?

Also, I've come across $:/tags/ViewTemplate which is only described as: 
"The system tag  $:/tags/ViewTemplate 
marks the view template." which is not very telling.

I've done tenplates tgat work fine. They are not 
tagged $:/tags/ViewTemplate. If I tag them as scuch, they act aout as if 
their content was twice included. What does $:/tags/ViewTemplate really do? 
How should it be used?

Regards,

-- 
Jean-Pierre





-- 
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/bfe6e25c-149f-4fdb-aa9a-fdd383877f05n%40googlegroups.com.

[tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

2021-06-28 Thread TiddlyTweeter

PMario wrote:

> That's right, because languages haven't been designed to be expressed by 
> algorithms. They have been designed by the human brain. And it seems humans 
> do like "exceptions" from the norm, which tend to cause problems for 
> programs.
>

Ha! Great reply!

The way I put it is this: 
  The computer works for ME! 
  I don't work for IT!  
TBH, a lot of internet sites seem to believe in the latter (i.e use 
algorithms to impose solutions and logic), to their detriment, rather than 
the former.

Just saying, 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/4009418f-d366-4b45-95c7-0cc9c306658cn%40googlegroups.com.

[tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

There is one thing, which is also interesting. Browsers have a lot of 
different built in functions 

 
already. The problem is, we don't have wikitext representations for them. 
This is a whole new field for possible improvements ... if someone wants to 
collect some fame ;)

On Monday, June 28, 2021 at 12:14:05 PM UTC+2 PMario wrote:

> On Monday, June 28, 2021 at 11:18:29 AM UTC+2 TiddlyTweeter wrote:
>
> While it is possible to emulate *natural language usage* (i.e. code for 
>> variations of plurals; or passive v. active voice) I'm not sure it is ever 
>> satisfying.
>>
>
> That's right, because languages haven't been designed to be expressed by 
> algorithms. They have been designed by the human brain. And it seems humans 
> do like "exceptions" from the norm, which tend to cause problems for 
> programs. 
>
> -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/05a984b6-2b88-40ad-bdf3-ae1c955aec9fn%40googlegroups.com.

[tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

On Monday, June 28, 2021 at 11:18:29 AM UTC+2 TiddlyTweeter wrote:

While it is possible to emulate *natural language usage* (i.e. code for 
> variations of plurals; or passive v. active voice) I'm not sure it is ever 
> satisfying.
>

That's right, because languages haven't been designed to be expressed by 
algorithms. They have been designed by the human brain. And it seems humans 
do like "exceptions" from the norm, which tend to cause problems for 
programs. 

-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/54bb5c62-ad4f-41f2-8ccf-77e6afb1d150n%40googlegroups.com.

[tw5] Re: [UPDATE] uni-link pugin V2.1.0 released

2021-06-28 Thread TiddlyTweeter

PMario wrote:

> Si wrote:
> ...
>
>> I only just noticed your Uni-link Search feature! Very handy -  I have 
>> been frequently writing things like [[really good idea|Really Good Ideas]], 
>> so this will save me a lot of time.
>>
>   
>
>> I'm wondering if there is a way to use Uni-link search, but tweak it so 
>> it will ignore the final "s"? So [[books|??]] would automatically link to 
>> [[Book]].
>>
>
> The main problem is, that singular / plural rules depend on the language. 
> book - books in German is Buch - Bücher 
> So a hardcoded rule won't help the plugin. 
>
> The second problem is, that it has to work in both directions. So imo a 
> link like [[books|??]] needs to search for "book" and "books"  ... 
> [[book|??]] has to do the same thing. ... This will make the search 
> function 50% slower :/  
>
> It would be possible to implement "plural" / "singular" filter rules. But 
> they will be language specific. Some 3rd party libraries will be needed. So 
> there would be an additional plugin per language.
>

This is a very interesting technical discussion. Why interesting? Because 
it illustrates the huge issue of language precision v. language latitude.

Personally I see is as a GENERIC problem, not anything specific to the 
excellent UNILINK.

While it is possible to emulate *natural language usage* (i.e. code for 
variations of plurals; or passive v. active voice) I'm not sure it is ever 
satisfying.

A related, semantic, case in point is the breeding of Topics on TW Links 
 where we have "Theme", 
"Themes", & "Theming" . That makes no sense and the proliferation clogs the 
visuals.

The re-link plugin is very popular and I try to keep uni-link compatible 
> with it. IMO the singular / plural links will definitely be out of the 
> scope, what re-link should handle. ...
>

Right. 

The question is interesting and valid, and it seems to be an easy change. 
> .. But due to its language specific nature, it isn't. Implementing it will 
> probably double the actual complexity of the plugin.
>

Right.

It's one of those "between the devil and the deep blue sea 
"

issues?

Just FYI, I personally deal with this kind of issue by setting 
"CONVENTIONS" (case, plurality) for each particular use case and never 
change them.

This is merely a side-comment. 
Best wishes, 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/ac2eadf8-47be-45b1-8568-a1c76911a36en%40googlegroups.com.

Re: [tw5] Re: TW as static site generator in AWS lambda

2021-06-28 Thread Victor Dorneanu

This is really amazing. It shows me how easy Tiddlywiki can be used for 
processing data (especially when you have standard formats like JSON). I've 
also thought the Lambda flavour/instance of Tiddlywiki would be way more 
difficult to deploy. 

I guess I'll use the same approach to implement some bookmarking mechanism, 
where I use data exported from getpocket.com, send it to AWS API Gateway 
which then calls Tiddlywiki Lambda to store the bookmark (or add it to some 
existing page/tiddler). 

Again, thanks for this link! 

On Saturday, June 26, 2021 at 4:28:18 PM UTC+2 Mohamed Amin wrote:

> Thanks a million Mohammed for sharing such a great article
>
> For me, the following paragraph shows how powerful TW5 is :
>
> Purple News was born out of a client need to track the way several news 
> sources were covering the topic of “Voting” during the 2020 US presidential 
> election. Using AWS Athena to scale up SQL query automation, we extended 
> this concept to track lots of different topics — and used 
> TiddlyWiki-on-Lambda to generate every page on the site!
>
> Regards
>

-- 
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/0f039a5d-7dc4-4b12-bd6f-474c99bdc42fn%40googlegroups.com.

[tw5] Re: [UPDATE] uni-link pugin V2.1.0 released