[tw5] Re: <> vs []

2019-07-08 Thread TonyM
Mat,

Is the origin of Foo bar from the "Grand Foo Bar" from a masonic lodge? a 
very U.S. centric source?. I also find it all but useless myself, I have to 
read something 5 times if it has too many foos and bars because there is 
not any other information contained within them. The fact that someone does 
not need to think to use foo bar belies that fact, I can see that a little 
more thinking would have being helpful. It may appear to make sense to the 
writer, but I suspect it is often more confusing for the reader.

Over the years I have used consistent examples like Fred, Alice and Bob, 
Fruits and number suffixes number-1 or "if-true" var-1, input etc I 
understand Foo and Bar but find it the least helpful of the bunch.

Watts funny lines struck a chord.
*Has my plea been footile? It has just the opposite effect on me, I can't 
stop thinking 'what's a foo?' I must be foolexic, or was on a bar stool the 
day they covered it at school. Couldn't 'apples' be used instead?*


just saying..

Regards
Tony

On Tuesday, July 9, 2019 at 1:20:34 AM UTC+10, Mat wrote:
>
> @Watt 
>>
>>
> Foo, foobar etc was invented specifically so you don't have to think. Plus 
> it is now a convention so if you introduce something else, then people will 
> have to get used to that instead. For a single string I guess HelloThere 
> would work but it is not generic. And for multiple strings... it is 
> annoyingliy difficult to come up with anything that is not asdfasdöghhagsöj 
> which is also not good. Besides, bars can be nice.
>
> In the docs I do thing we avoid Foo though.
>
> <:-)
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ca73e168-f93d-472e-81ef-08a4060e40d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: <> vs []

2019-07-08 Thread Mat
I'm actually allergic to apples. 
...but I must admit, that IS a nice alternative. I might start to use it :-)

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d796bb4f-9074-4df0-8406-ab921d5b268c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: <> vs []

2019-07-08 Thread Watt
Has my plea been footile? It has just the opposite effect on me, I can't stop 
thinking 'what's a foo?' I must be foolexic, or was on a bar stool the day they 
covered it at school. Couldn't 'apples' be used instead?

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a19fb439-7601-4a7e-853e-9720881bacee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: <> vs []

2019-07-08 Thread Mat
Addendum: And any newcomers who have a modicum of programming knowledge 
will use Foo anyway so... it's probably better to just learn it. IMO it is 
part of common computer literacy.

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e3156beb-ef18-4e7a-8b72-8d8ca7c0b9a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: <> vs []

2019-07-08 Thread Mat
@Watt 
>
>
Foo, foobar etc was invented specifically so you don't have to think. Plus 
it is now a convention so if you introduce something else, then people will 
have to get used to that instead. For a single string I guess HelloThere 
would work but it is not generic. And for multiple strings... it is 
annoyingliy difficult to come up with anything that is not asdfasdöghhagsöj 
which is also not good. Besides, bars can be nice.

In the docs I do thing we avoid Foo though.

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ae8676aa-bcd6-4d71-9672-7e4e9ea99912%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: <> vs []

2019-07-08 Thread Watt
I hope you twizards know how much your contributions are valued and appreciated 
but on behalf of non-programmers everywhere, the easily confused and all those 
unfamiliar with the use and tradition behind the word 'foo' can I humbly 
request that it is never used in examples relating to tiddlywiki? It really 
doesn't make things easier to understand. 

And as for 'bar'...  please, don't do it.

https://en.m.wikipedia.org/wiki/Foobar

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/272cf335-2d53-4b59-8153-2f6469721cd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: <> vs []

2019-07-08 Thread Mat
Great answers guys!

I missed to include the "enlist" operator (now added in the OP) but I 
assume this doesn't change @pmarios point that it is still generally faster.

>Open close the preview several times  

Trick!

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f2850882-54b1-4944-9528-c2e36d2ad295%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: <> vs []

2019-07-08 Thread PMario
Hi Mat, 

If we only look at the the <$list line, they are fundamentally different. 

The *first *one assigns a macro-call to the filter variable
The *second *one assigns a string value to the filter variable. 

The *first list* needs to run 2 filters. 1 in the set widget 1 in the list 
widget

The *second list *needs to run only 1 filter .. which shuld be faster as 
calling a macro and run 2 filters


If you open the https://tiddlywiki.com/prerelease/ and paste this code: 

\whitespace trim 

<$set name=myfilter filter="[tag[foo]]">

<$list filter=<> /> 

<$list filter="""[]"""/>


Activate the preview: *Parse Tree*
You can see the result is very simlar. See the macro-call

Activate the preview: *Widget Tree*
The result is different. 



Open close the preview several times  
F12 ... open dev consule
select the "Console" tab
click the "bin" button to clear the output

type: $tw.perf.log()

which will open the filter log.  The filter a should be around line 
40    filter [] is around line 80

This suggests, the second one is faster. ... I'm not sure if the new filter 
optimizer is responsible for this. 

have fun!
mario

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7c6fff1b-d5f8-45f2-a760-c30452555f3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: <> vs []

2019-07-08 Thread Jed Carty
filter=<> uses whatever is stored in the variable foo as the filter 
itself, filter=[] uses whatever is stored in the variable foo as an 
input title.

Some examples are probably more helpful:

<$set name=foo value="""[tag[HelloThere]]""">

Set `foo="[tag[HelloThere]]"`

! Using `"[]"`

<$list filter="[]">



! Using `<>`

<$list filter=<>>






This lets you build filters using [] and then use that filter using 
<>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/aa81e5f8-7d06-4877-859c-f030e2164460%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.