'Ello y'all. I was wondering if there was a way to use a variable as a tag for a new tiddler.
I tried this:
<$edit-text tag="input" tiddler="$:/temp/getname" default="" />
<$button> Button Text
<$action-maketid $title={{$:/temp/getname}} tags="[[tag1]] [[tag2]] {{!!custom_field_defined_elsewhere}}" field1={{$:/temp/getname}} field2="input for field2" $template="" $navigate="show"/>
<$action-setfield $tiddler="$:/temp/getname" $value=""/>
</$button>But that just makes a tag with literally {{!!custom_field_defined_elsewhere}}. Is this possible in another way?
I also tried <$action-sendmessage $message="tm-add-tag" param={{!!custom_field}} $title={{$:/temp/getname}} /> from within the button as well, but maybe I've got the syntax wrong?
Any enlightenment is appreciated.
I reworked it a little. Examine this:
<$edit-text tag="input" tiddler="$:/temp/getname" default="" />
<$button> Button Text
<$wikify name= moreTags text="[[tag1]] [[tag2]] <$text text='[[' />{{!!custom_field_defined_elsewhere}} <$text text=']]' />">
<$action-createtiddler $basetitle={{$:/temp/getname}} tags=<<moreTags>> field1={{$:/temp/getname}} field2="input for field2" />
</$wikify>
<$action-navigate $to={{$:/temp/getname}} />
<$action-setfield $tiddler="$:/temp/getname" text=""/>
</$button>I hope it helps!
Here is a slightly more elegant version that uses your second thought with tm-add-tag. The 2 differences to note here are:
- The
paramin$action-sendmessageis with dollar sign so$param - You have to wrap
tm-add-tagwith a<$fieldmangler>widget which tells it on exactly what tiddler to operate on. It is a side case only fortm-add/remove-tagandtm-add/remove-field.
In my opinion this code is more readable and easier to maintain than the first one:
<$edit-text tag="input" tiddler="$:/temp/getname" default="" />
<$button> Button Text
<$action-createtiddler $basetitle={{$:/temp/getname}} tags="[[tag1]] [[tag2]]" field1={{$:/temp/getname}} field2="input for field2" />
<$fieldmangler tiddler={{$:/temp/getname}}>
<$action-sendmessage $message="tm-add-tag" $param="tag3" />
<$action-sendmessage $message="tm-add-tag" $param={{!!custom_field_defined_elsewhere}} />
</$fieldmangler>
<$action-navigate $to={{$:/temp/getname}} />
<$action-setfield $tiddler="$:/temp/getname" text=""/>
</$button>Have a nice day!
I was also looking at the fieldmangler option as well, but I thought if the
action-sendmessage could be done outside of it, it work just the same. Interesting to know that there's a side/edge case for the tm-add/remove-tag/field; I hadn't read anything about that in the TW docs.I also prefer your second version without the wikify as it would be much easier to understand (and maintain as you said). I'll give it a go in my twiki and hope for the best!
Of course it is!
Replace the line with the custom field with this one.
<$action-sendmessage $message="tm-add-tag" $param={{{ [{!!custom_field_defined_elsewhere}addsuffix[MySuffix]] }}} />I am very happy that I was able to help you!
I use a filtered transclusion to pass it on the parameter, which allows me to use a filter, then from the filter notation I use transclusion for the custom field and then addsuffix filter operator to add the suffix.
( in filter notation transclusion is with single brace. each filter run has a square brackets, so that's why it looks like that. Filtered transclusion has triple braces )
I had leveraged setvars by Tobias Beer to concatenate two vars and then passed that into the $param instead.
<$setvars tagSuffix="tag nexTag" _tag={{!!custom_field_defined_elsewhere}} _nextTag="suffix"> <$fieldmangler tiddler={{$:/temp/getname}}>
<$action-sendmessage $message="tm-add-tag" $param=<<tagSuffix>> />
</$fieldmangler>tm-add-tag that are not under a $fieldmangler I think those may take action on the "currentTiddler"
<$fieldmangler tiddler={{$:/temp/getname}}>
$set widget can also be used, so here is an alternative way to the same thing
<$edit-text tag="input" tiddler="$:/temp/getname" default="" />
<$button> Button Text
<$set name="allmytags" filter="[{!!custom_field_defined_elsewhere}addsuffix[MySuffix]] [[tag1]] [[tag2]]">
<$action-createtiddler $basetitle={{$:/temp/getname}} tags=<<allmytags>> field1={{$:/temp/getname}} field2="input for field2" />
</$set>
<$action-navigate $to={{$:/temp/getname}} />
<$action-setfield $tiddler="$:/temp/getname" text=""/>
</$button>$vars is different from $set simply by $vars being a very simplistic shorthand for $set, in fact I read somewhere that for performance reasons $vars Is prefered to $set, because $set is more powerful... but in this case we need the power it has so that's why it had to be used. I too typically avoid $set and use $vars instead but in this case $set is needed.
$list loop)
Those I collect in a type1, type2, etc... Overview tiddler, which groups them in a tab with filters based on the tags set by the button (hence why it was so important).
And I then that one get mixed with the other types in a grand Overview tiddler which shows them all.
1 reply
2 replies
oh yes, I see now. I do not have time to think on it but I can imagine it can kinda complicated to create a structure to work with this requirement. Because in my vision I think you'll have to create tiddlers that hold the values in fields and then use the radio button value as intermediate and get the exact value from specific tiddlers for what you need.
But maybe the way you do it with $select and list could be better because "multiple" options are selected.
so I am sure you are doing it well since it is working for you! 😊
tl;dr: xlsx parser is fixed in the prerelease and this fix will be available in the next official release of TiddlyWiki or so I think
Hello! I am not sure why the import of JSON would result in a binary file if they are the JSON format produced by TiddlyWiki. For CSV.... Now I am not sure if that has a parser for it? TiddlyWiki best works with the JSON because it can export and import multiple tiddlers. CSV is only export as far as I know. (I quickly tested what I was saying and I seem to be right. CSV is export only format. It has no parser for importing.)
So I'd recommend the JSON format as the main if you have to deal with set of tiddlers between different TiddlyWikis.
CSV only if you want to easily export them to use them in a spreadsheet application for example for rendering or processing them for some other reason.
Now... on a more serious note, I didn't get "in depth" with the .xlsx parser. So following your comment, I can confirm that the xlsx-utils demo does not work for me in both Chromium and Firefox.
The demo is found here: https://tiddlywiki.com/editions/xlsx-utils/
Upon importing the Presidents and Justices.xlsx, TiddlyWiki returns a RSOD: Uncaught TypeError: Cannot read property 'getTiddlerText' of undefined
However in the prerelease, this seems to be already fixed. So consider using the pre-release version of TiddlyWiki and the plugin.
You can find the prerelease of the Demo page here: https://tiddlywiki.com/prerelease/editions/xlsx-utils/
It seems to import there correctly and the Demo page works just fine for me. It did give some warnings but it worked for me.
You can find the pre-release of TiddlyWiki at: https://tiddlywiki.com/prerelease/
So consider experimenting with the prerelease.
I hope this helped to clarify some things. Have a great day.
Of course you can! You can also import existing old Wiki HTML on a new empty one (sometimes I do that when testing things).
However, here is the preferred friendlier way, the prerelease updater.
I am not sure how to help you more. However, I can share what I did to test if it works for me.
- I use Windows 10 x64 bits. So I got TiddlyDesktop-win64-v0.0.14
- I downloaded the xlsx-utils prerelease demo as a HTML file
- I downloaded the
Presidents and Justices.xlsxto a file. - I loaded xlsx-utils prerelease demo HTML file into TiddlyDesktop
- I imported
Presidents and Justices.xlsxinto the xlsx-utils demo running under TiddlyDesktop - I had no issues. So maybe you could test the same setup and see if you get the same problem or not.
Additionally I also tested to upgrade the 5.1.23 xlsx-utils demo as HTML file with the prerelease upgrader and then tested that to import the Presidents and Justices.xlsx file, it still worked. (I upgraded using Firefox but I doubt this matters)
Maybe I didn't understand what is not working. I assumed you speak about xlsx-utils prerelease.