[tw5] Re: Unexpected behavior with list filter for ViewTemplate
That is a distinction in the operators which had completely eluded me. That was extremely helpful, thank you! On Friday, November 1, 2019 at 7:22:26 AM UTC-4, Eric Shulman wrote: > > On Friday, November 1, 2019 at 4:06:22 AM UTC-7, Andrés Pérez wrote: >> >> So this is probably me not understanding something fully, so I am asking >> here to be better educated. I was playing around with a viewtemplate and >> thought about how to apply it based on tiddler title. When I did that >> filter, though, it applied the template to every single tiddler. >> >> So I have these two viewtemplate-tagged tiddlers: >> Title-based: >> >>> <$list filter="[all[current]is[tiddler]!is[system]title[foobar]]"> >>> foo >>> >> >> >> Tag-based: >> >>> <$list filter="[all[current]is[tiddler]!is[system]tag[foobar]]"> >>> bar >>> >> >> >> My expectation is that the title-based viewtemplate only gets applied to >> a tiddler with a title of 'foobar' and the tag-based one is only applied to >> tiddlers with a tag of "foobar'. >> What winds up happening is that the tag-based template only gets applied >> based on the tag, but the title-based one gets applied to all tiddlers. >> >> I feel like this is due to something fundamental/important in how this is >> all put together, but I don't know what or why. >> >> I have a working example in this link: >> >> https://storage.googleapis.com/hgdrop/titlebasedtemplate.html#TagBasedViewTemplate:foobar%20blankTiddler%20tagged%20TitleBasedViewTemplate%20TagBasedViewTemplate >> >> >> And a wordier description here: >> >> With the two ViewTemplates described above, and these 3 tiddlers with no >> contents: >> A: Title: foobar, Tag: *none* >> B: Title: blankTiddler, Tag: *none* >> C: Title: tagged, Tag: foobar >> >> My expectation is that the contents of the three tiddlers be: >> A: foo >> B: *nothing* >> C: bar >> >> Actual rendered contents: >> A: foo >> B: foo >> C: foo bar >> > > The following note appears in the documentation for > https://tiddlywiki.com/#title%20Operator > > title is a constructor (except in the form !title), but field:title is a >> modifier. > > > see https://tiddlywiki.com/#Selection%20Constructors, which explains: > > The output of a Filter Step depends on its operator: >> Most operators derive their output from their input. For example, many of >> them output a subset of their input, and thus truly live up to the name of >> "filters", narrowing down the overall output of the containing run. These >> operators are called selection modifiers. >> A few operators ignore their input and generate an independent output >> instead. These are called selection constructors: they construct an >> entirely new selection. >> A good example of a constructor is title. The output of >> [title[A]title[B]] is just B. But the field operator is a modifier, so >> [title[A]field:title[B] outputs nothing at all. > > > Thus, in your experiment: > "title[foobar]" is a "constructor" that always returns "foobar" regardless > of what precedes it in the filter, while "field:title[foobar]" is a > "modifier" that only returns "foobar" if the preceding filter terms already > contain "foobar" > > enjoy, > -e > Eric Shulman > TiddlyTools: "Small Tools for Big Ideas!" (tm) > http://tiddlytools.github.io/ > InsideTiddlyWiki: The Missing Manuals > http://insidetiddlywiki.tiddlyspot.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/c5a1ed53-b95b-4578-9e6d-83caa53f060c%40googlegroups.com.
[tw5] Unexpected behavior with list filter for ViewTemplate
So this is probably me not understanding something fully, so I am asking here to be better educated. I was playing around with a viewtemplate and thought about how to apply it based on tiddler title. When I did that filter, though, it applied the template to every single tiddler. So I have these two viewtemplate-tagged tiddlers: Title-based: > <$list filter="[all[current]is[tiddler]!is[system]title[foobar]]"> > foo > Tag-based: > <$list filter="[all[current]is[tiddler]!is[system]tag[foobar]]"> > bar > My expectation is that the title-based viewtemplate only gets applied to a tiddler with a title of 'foobar' and the tag-based one is only applied to tiddlers with a tag of "foobar'. What winds up happening is that the tag-based template only gets applied based on the tag, but the title-based one gets applied to all tiddlers. I feel like this is due to something fundamental/important in how this is all put together, but I don't know what or why. I have a working example in this link: https://storage.googleapis.com/hgdrop/titlebasedtemplate.html#TagBasedViewTemplate:foobar%20blankTiddler%20tagged%20TitleBasedViewTemplate%20TagBasedViewTemplate And a wordier description here: With the two ViewTemplates described above, and these 3 tiddlers with no contents: A: Title: foobar, Tag: *none* B: Title: blankTiddler, Tag: *none* C: Title: tagged, Tag: foobar My expectation is that the contents of the three tiddlers be: A: foo B: *nothing* C: bar Actual rendered contents: A: foo B: foo C: foo bar -- 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/83715acf-4d17-4056-af7b-7bac186bd4c4%40googlegroups.com.
Re: [tw5] Updating from of node TW 17 to 19 not working?
That was it! thank you! On Saturday, February 9, 2019 at 3:53:30 AM UTC-5, Jeremy Ruston wrote: > > Hi Andrés > > It sounds as though one possibility is that your wiki includes a copy of > the old v5.1.17 core plugin. Have a look through the tiddler folder for a > large tiddler file called something like "$__core.tid", and delete it if > you find it. > > Best wishes > > Jeremy > > -- > Jeremy Ruston > jer...@jermolene.com > https://jermolene.com > > On 9 Feb 2019, at 03:42, Andrés Pérez > > wrote: > > Ok, I know I am just missing a step that isn't obvious. But I have a > node.js TW version 5.1.17. I upgrade the TW node app to 5.1.19. When I > create a new TW with that version and call --listen, it serves up the TW. > But when I call --listen against my existing TW, it says that it doesn't > recognize the command. > > This tiddler tells me how to upgrade a single page TW: > https://tiddlywiki.com/static/Upgrading.html > This tiddler tells me how to upgrade my TW node app: > https://tiddlywiki.com/static/Upgrading%2520TiddlyWiki%2520on%2520Node.js.html > > How do I upgrade my tiddler which is in multiple pages due to it being > managed by the node app? > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to tiddlywiki+...@googlegroups.com . > To post to this group, send email to tiddl...@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/5a3f9773-ded1-48d8-b917-6b7591aa66f8%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/5a3f9773-ded1-48d8-b917-6b7591aa66f8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- 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/478c79e4-3d46-4037-badb-0603c956c92b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw5] Updating from of node TW 17 to 19 not working?
Ok, I know I am just missing a step that isn't obvious. But I have a node.js TW version 5.1.17. I upgrade the TW node app to 5.1.19. When I create a new TW with that version and call --listen, it serves up the TW. But when I call --listen against my existing TW, it says that it doesn't recognize the command. This tiddler tells me how to upgrade a single page TW: https://tiddlywiki.com/static/Upgrading.html This tiddler tells me how to upgrade my TW node app: https://tiddlywiki.com/static/Upgrading%2520TiddlyWiki%2520on%2520Node.js.html How do I upgrade my tiddler which is in multiple pages due to it being managed by the node app? -- 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/5a3f9773-ded1-48d8-b917-6b7591aa66f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw5] Re: Using fields from upper tiddlers in multi nested tranclusion
I am aware, yeah. I know that the way I defined the transclusions in Arthur
imply currentTiddler and that by transcluding Arthur as a template I am
sucking at explaining myself.
I essentially want Arthur to use Ford's value without having to have Arthur
explicitly call out Ford. I need Arthur to remain agnostic of any tiddlers
which might use it as a template.
On Thursday, October 18, 2018 at 7:50:24 AM UTC-4, TonyM wrote:
>
> Thats the type of example I could use. Before delving in deeply are you
> aware of the fact you can access a field in another tiddler, transcluded,
> in a template or any tiddler by giving both tiddlername!!fieldname eg
>
> {{tiddlername!!fieldname}}
>
> In filters
> {tiddlername!!fieldname}
>
> And in some widgets or macros with tiddler=tiddlername
> Field=fieldname
>
> These could be fixed litteral names or ones derived from a macro.
>
> Do you see what I am saying?
>
> Regards
> Tony
>
>
--
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/303db7ad-2540-4cd6-a1a7-46f0a74f7903%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[tw5] Re: Using fields from upper tiddlers in multi nested tranclusion
Sure. I thought I had but I can always use more words! I want to know if it's possible to define a template tiddler which is essentially an overload of another template tiddler to set default values. I wound up doing it as a macro and have attached a sample TW with both attempts. I was just curious to see how far I can take - ... well, abuse - the wikitext transclusion functionality :) On Thursday, October 18, 2018 at 7:17:26 AM UTC-4, Jed Carty wrote: > > I think that you need to describe the desired logic behind the display, > not just an example. > -- 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/19117769-6bcb-4e5d-a846-14e628bf8b40%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw5] Using fields from upper tiddlers in multi nested tranclusion
I think I am doing something unorthodox. I want to use a template tiddler (call it Arthur) inside another template tiddler (call it Ford). Arthur will display the transcluded fields 'dolphins' and 'mice' If I set define field 'dolphins' to "fish" inside of Ford, that template displays it due to Arthur displaying it (and 'mice' remains predictably blank). If I then transclude Ford as a template inside tiddler Zaphod, but only set 'mice' and not 'dolphins', then 'dolphins' is blank but 'mice' displays the value I set. Essentially, I want to arrest the transclusion of the 'dolphins' field at Ford without having to specify that in Arthur. -- 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/f8527b17-4ed0-461d-b1fb-8886fc16c105%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw5] Re: how to generate a unique state tiddler for a reveal in a template
/facepalm
yup. That does work. thanks!
On Sunday, October 7, 2018 at 10:52:31 PM UTC-4, Mark S. wrote:
>
> In order to concatenate, the macro needs either placeholders (e.g. $name$)
> or variables (e.g. $(variable)$). In this case, $(currentTiddler)$ is
> already available. So you should be able to use:
>
> \define stateName(name) $:/state/$(currentTiddler)$/$name$
>
> Good luck!
> -- Mark
>
> On Sunday, October 7, 2018 at 6:44:54 PM UTC-7, Andrés Pérez wrote:
>>
>> So I have a reveal in a template tiddler because I need it to be reusable
>> and unique per tiddler that is using the template.
>> Basically I want a reveal in a tiddler that when clicked shows some text.
>> I then want to use that same reveal in multiple tiddlers by just
>> transcluding the template tiddler but having the reveal only show up on the
>> tiddler where it is clicked and not the others.
>>
>> So, I tried with a macro where it builds the state tiddler like this:
>>
>> \define stateName(name) "$:/state/{{!!title}}/$name$"
>>
>> That works fine when I just call the macro in a text field by itself. So
>> in a tiddler named 'test', adding this <> results in
>> $:/state/test/foo
>>
>> If I try it as the attribute for a reveal (<$reveal type="nomatch"
>> state=<> text="show">) the state tiddler which is created is
>> $:/state/{{
>>
>> Can I do what I want to do?
>>
>>
>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To 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/c3048b67-44dd-447e-a580-e84d512ebac3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[tw5] how to generate a unique state tiddler for a reveal in a template
So I have a reveal in a template tiddler because I need it to be reusable
and unique per tiddler that is using the template.
Basically I want a reveal in a tiddler that when clicked shows some text. I
then want to use that same reveal in multiple tiddlers by just transcluding
the template tiddler but having the reveal only show up on the tiddler
where it is clicked and not the others.
So, I tried with a macro where it builds the state tiddler like this:
\define stateName(name) "$:/state/{{!!title}}/$name$"
That works fine when I just call the macro in a text field by itself. So in
a tiddler named 'test', adding this <> results in
$:/state/test/foo
If I try it as the attribute for a reveal (<$reveal type="nomatch"
state=<> text="show">) the state tiddler which is created is
$:/state/{{
Can I do what I want to do?
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To 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/b4a862f2-dfba-411b-b980-fa71b582c8cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [tw5] Node.js TW not responding to HTTP requests in AWS EC2
ah! I see that now. gonna keep the proxy for ssl, but good to know. Thank you!! On Thursday, October 4, 2018 at 11:13:59 AM UTC-4, Arlen Beiler wrote: > > That was my first suspicion. I believe you can specify which IP address to > use in the command line. > > On Thu, Oct 4, 2018 at 10:21 PM Andrés Pérez > wrote: > >> So a netstat -an shows that the server is only listening for traffic on >> localhost >> tcp0 0 127.0.0.1:8080 0.0.0.0:* >> LISTEN >> >> instead of world >> >> tcp0 0 0.0.0.0:80800.0.0.0:* >> LISTEN >> >> I am using nginx to reverse proxy the traffic. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "TiddlyWiki" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to tiddlywiki+...@googlegroups.com . >> To post to this group, send email to tiddl...@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/808dc996-c09f-492f-80ed-5431dcb81452%40googlegroups.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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/dafda364-43ce-4b46-94a8-3e41cef118cb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw5] Node.js TW not responding to HTTP requests in AWS EC2
So a netstat -an shows that the server is only listening for traffic on localhost tcp0 0 127.0.0.1:8080 0.0.0.0:* LISTEN instead of world tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN I am using nginx to reverse proxy the traffic. -- 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/808dc996-c09f-492f-80ed-5431dcb81452%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw5] Node.js TW not responding to HTTP requests in AWS EC2
I stood up an EC2 instance with port 8080 open. I verified it by dropping an index.html in home and serving it with python simplehttp. I then did an --init server in home using the node version of TW, followed by --server. If I curl http://localhost:8080 I get back the new TW, but I get a connection refused if I try it using either the internal or public IPs. Anybody experience this? -- 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/56cbdb90-e435-4152-a5b0-965834d9406b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
