{{||ThingAndStuff}} - I don't have a specific example - more curious
- make a template with a table that displays a set of feilds
- transclude said template
- forget what fields i need to fill out
- reference template :P
I am not sure what you mean exactly.... but that's because I cannot understand it. Anyway... I will try to give you something in hope that it may be what you want.
Create a new tiddler and put this as contents...
''Info'': <$edit-text tiddler="$:/temp/test" field=testfield /> <br />
''Msg'': <$edit-text tiddler="$:/temp/test" field=testfield2 /> <br />
<$button>
<$action-setfield info={{$:/temp/test!!testfield1}} />
<$action-setfield msg={{$:/temp/test!!testfield2}} />
<$action-deletefield $tiddler="$:/temp/test" testfield testfield2/>
Set fields info and msg of current tiddler.
</$button>and I guess the next time you forget what fields were there, you can just transclude this tiddler with something like {{||ThingsAndStuff}} then you'd be able to set whatever fields you had to set without having to remember anything else but one main field editing template?
Sorry if that's not remotely related to your answer. I don't understand and probably won't be able to help you.
Yes, I see. This is one problem that I am mentally struggling with too, so I understand the "external updating" will fail, because I do feel like that myself. My personal take on similar problem is to 1) make my TiddlyWiki my central repository of it - like the only copy of that information so that I know it is exactly there when I need to do modifications and open it when I do modifications to the things and it to be as brief and easy to update as possible. and 2) Make the TiddlyWiki more useful to me too so that I can actually "need" it or use it during such thing. Example: as a checklist of things that I must do so that I can just not think what I must do but just look at what I should check and update everywhere else; or additionally like half-baked commands maybe.
So indeed, experimenting is needed and if you find out something that actually works for you, I'd be happy to hear and hopefully see if I can add it to my own workflow or something.
Disclaimer: all this is just abstract suggestions and some of my ideas since I have similar problem with my not as frequent as I want TiddlyWiki usage that I am still trying to even out and still far from even my own suggestion.
{{||ThingStuff}} doesn't add fields from the transcluded tiddler? is there another method to transclude, maybe?
{{My Other Tiddler||ThingsStuff}} (this is a shorthand for the transclude widget in WikiText) or try to use the full way which is with the $transclude widget https://tiddlywiki.com/#TranscludeWidget
qbit: I think you are using it wrong. This form of a transclusion is a "template" {{||ThingStuff}} eg:
Let's say you have a tiddler named: test. eg: If you want to show the "description" field within the test-tiddler you can do this: {{test!!description}}. Since you are already "in" the test-tiddler you can use the "shorthand" instead: {{!!description}}. ... So {{!!description}} internally uses the <<currentTiddler>> variable for the missing tiddler name. ... In the context of the test-tiddler text the <<currentTiddler>> variable is set to "test"
If you transclude: {{myText}}, it will show the content of the "myText" tiddler within the test-tiddler. If you use {{!!description}} in the "myText" tiddler it will show the description-field form myText and not the description from test-tiddler. The <<currentTiddler>> variable with "{{myText}}" is set to "myText"
If you use {{||myText}} in the test-tiddler, it will keep the <<currentTiddler>> variable at "test" ... So if you use {{!!description}} in the "myText" tiddler it will show the "description field" of the "test" tiddler. ... So {{||myText}} is called a template-tiddler.
pmario: that’s how I am using them, but I was hoping I could also transclude the literal field names into the new tiddler.
Basically I want to auto populate a new tiddler’s field set (the literal list of fields, not the values from the template) from a transcluded tiddler
Yea, I thought about that as I did read your posts. ... Fields don't "stack" :). ... What you can do is using the <$tiddler /> widget. eg:
title: test
description: test - test
Transclude the "local" description field: {{!!description}}
<$tiddler tiddler="myText">
Transclude the "myText" description field: {{!!description}}
</$tiddler>
I'm trying to create a template to show all the tasks for today, I use the journal title as
YYYY-0MM-0DDand i would like to filter something like this
[sameday:schedule[<currentTiddler>search-replace:g[-],[]]]if I hardcode the title it works
[sameday:schedule[20210816]]
schedule[] part?
<$text text=<<result>> />
</$wikify>
You cannot nest things like that. Especially you should remember you cannot have "another pair of square brackets inside a another one" except the initial first pair. Sorry, that sounds more confusing than it is, but you can't nest them like that. You must "export" such logic into variables and then use those. Here is a working example of what you want to do
<$vars thedate={{{ [<currentTiddler>search-replace:g[-],[]] }}}>
{{{ [sameday:schedule<thedate>] }}}
</$vars>I tested this by creating a tiddler named 2021-08-16 and put the "code" in the tiddler body. While I had created another tiddler with any name but with a field schedule with value of 20210816 and it worked. Good luck!
<$vars thedate={{{ [<currentTiddler>search-replace:g[-],[]] }}} >
{{{ [sameday:schedule<thedate>] }}}
</$vars>https://tiddlywiki.com/#TiddlerFiles
Well, you can import/export multiple tiddlers using ".json" format. But you still have to import them manually. The other format like that contain a single tiddler like .tid may also work but you'll still have to manually import them all in a bulk (via drag and drop at the top part of the Tiddlywiki in browser because the import button which brings a window doesn't allow multiple selection) and it should work.
Alternatively, if you want everything automated. After making a json file that looks like the json TiddlyWiki can export, you may try to construct a TiddlyWiki using node.js commands.
Just wanted to let you know, a new discussion group started at https://talk.tiddlywiki.org It uses Discourse as the backend and will be a community driven effort. Feedback and help is very welcome. You can use GitHub, Twitter and Google accounts for a fast sign up, or you can use the form on the page ;)
have fun!
mario
2 replies
I've been trying to figure this issue around fields for awhile, but left it until I had more time to spend on it. And now I have the time to spend (also reading through the TW docs and looking through Grok), I have to ask about it cause I haven't figured it out still.
The situation is as such:
I've got a series of tiddlers, each with a incremental value, (i.e. TestMe1 with field name=testname1, TestMe2 with field name=testname2, and so forth). In these tiddlers, I've placed the reference to the name (i.e. {{!!name}}). All have the same tag (tag=listForTabs). I've also added an additional transcluded tiddler via a list filter as well (
<$list filter="[{!!name}addsuffix[-additional]]" > <$transclude mode="block"/></$list>).In another tiddler called MyTabList, I list these in with a tab function
<<tabs "[tag[listForTabs]!sort[title]]" """$:/state/tab" "tc-vertical">>. Here's where the problem occurs- the fields that I've referenced and the transclusion via list are not visible, so the tabs have names, but show up with blanks in them. Is there a way that I can get the fields that I've referenced and transclusions to 'stick' wherever it will be shown within the tabs?
Without reproducing your setup fully. I want to tell you about the fact that within a tabs macro, the variable <<currentTiddler>> points to the Tiddler that contains the tab macro itself, not the ones aggregated by the tags. This is why with {!!name} it tries to find it on the tiddler with the tab macros on. Not the Tiddler that is the tab.
Saying this just in case due to ambiguity, but If you are storing the same tiddler title in a field name that's may not be needed?, because transcluding {{!!title}} or <<currentTiddler>> (or within a filter step {!!title} and <currentTiddler> even all[current]) will produce the tiddler name. Which you may be able to use. In that case, it may be sufficient to replace those with another variable provided by the tabs macro called <<currentTab>> (or <currentTab> for filter notation)
More information about <<currentTiddler>> problem and <<currentTab>> and its existance can be read here (at the bottom of this tiddler): https://tiddlywiki.com/#tabs%20Macro
Either way, those were side notes from me.
Your solution that you are looking for, should be this. Wrap your list widget with the workaround from the link.
<$tiddler tiddler=<<currentTab>>>
<$list filter="[{!!name}addsuffix[-additional]]" > <$transclude mode="block"/></$list>
</$tiddler>