Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    rayv
    @rayv:matrix.org
    [m]
    VERY great!!
    qbit
    @qbit:tapenet.org
    [m]
    Dedime: nice :D (re the tiddly saver)
    I just made a go tool as well! https://github.com/qbit/widdler
    standalone webdav server that dynamically creates new wiki files when you browse to them
    (and saves in TW are written back to disk directly - via webdav)
    Dedime
    @dedime:privacytools.io
    [m]
    qbit well done mate! Interesting project
    qbit
    @qbit:tapenet.org
    [m]
    Ty
    qbit
    @qbit:tapenet.org
    [m]
    https://deftly.net/widdler.mov got multi-user working in widdler \o/
    antepost
    @antepost:matrix.org
    [m]
    Hi all
    qbit
    @qbit:tapenet.org
    [m]
    Hola!
    antepost
    @antepost:matrix.org
    [m]
    TiddlyWiki is cool .. i like the idea... thanks
    qbit
    @qbit:tapenet.org
    [m]
    have any of you setup TW + gitea?
    Pavan Gurudutt
    @codeaches
    How do I set reminders in tiddlywiki5?
    qbit
    @qbit:tapenet.org
    [m]
    there are a number of plugins you can use
    or you can use the tiddlywiki itself .. but i am not smart enough to do that yet :D
    Pavan Gurudutt
    @codeaches
    I tried a plugin http://remindermacros.tiddlyspot.com/ but looks like its is not for TW5 version?
    qbit
    @qbit:tapenet.org
    [m]
    Projectify can do it
    Pavan Gurudutt
    @codeaches
    Thank you @qbit. Worked like a charm!
    qbit
    @qbit:tapenet.org
    [m]
    woo!
    HybridEyeGrillage
    @HybridEyeGrillage

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

    @yanderella:sibnsk.net
    [m]

    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!

    @yanderella:sibnsk.net
    [m]

    Here is a slightly more elegant version that uses your second thought with tm-add-tag. The 2 differences to note here are:

    • The param in $action-sendmessage is with dollar sign so $param
    • You have to wrap tm-add-tag with a <$fieldmangler> widget which tells it on exactly what tiddler to operate on. It is a side case only for tm-add/remove-tag and tm-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!

    HybridEyeGrillage
    @HybridEyeGrillage
    Thank you very much yanderella!
    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!
    HybridEyeGrillage
    @HybridEyeGrillage
    A follow up question: is it possible to add a suffix to the tag in the action-sendmessage?
    @yanderella:sibnsk.net
    [m]

    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 )

    HybridEyeGrillage
    @HybridEyeGrillage
    Aha, that's much easier than what I came up with!
    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>
    @yanderella:sibnsk.net
    [m]
    I am not familiar with the setvars, but Tobias Beer does have really impressive plugins. So I am glad you came up with a way. Though my personal way is that I try to keep myself as vanilla as possible so that way I can provide solutions without resorting to plugins and as a last resort to use such! However, I am glad you did find a solution already! I hope my answer is of some use to you.
    HybridEyeGrillage
    @HybridEyeGrillage
    I'd agree you you to keep things vanilla. :)
    A strange occurrence: when I click on the button to make the new tiddler, it applies the tags to the current tiddler as well as the new one? (I've also added a $template to base the new tiddler off)
    @yanderella:sibnsk.net
    [m]
    make sure you don't have a tm-add-tag that are not under a $fieldmangler I think those may take action on the "currentTiddler"
    <$fieldmangler tiddler={{$:/temp/getname}}>
    also inspired from your "setvars" idea... I realized that the $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>
    this doesn't use tm-add-tag or fieldmangler
    but a variable
    HybridEyeGrillage
    @HybridEyeGrillage
    Ah, that would save some lines; I had tried that with $vars before to no avail. Kind of infuriating that I end up so close to a solution but then wander off. >_<
    1 reply
    @yanderella:sibnsk.net
    [m]
    $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.
    (but what I said only could matter if you use this with lots of tiddlers or something complex so normally it isn't a concern to be worried about. I meant like a large $list loop)
    HybridEyeGrillage
    @HybridEyeGrillage
    Hmm... not sure if what I'm doing is considered complex. Basically, I have a starter tiddler with the button above that creates a new tiddler based on a choice's template (options box because I couldn't figure out how to have multiple vars with a radio button ('^_^) ).
    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.
    @yanderella:sibnsk.net
    [m]
    Also what you are doing sounds great, so keep it up. What I meant by complex is "computationally intensive" to render, like rendering way too many tiddlers and using $set without utilizing the full potential while a $vars would suffice too
    1 reply
    Also for radio buttons, as far as I can remember, you use the same field in any temporary tiddler to create a specific value? which is similar to option list? but I don't know
    2 replies
    @yanderella:sibnsk.net
    [m]

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

    HybridEyeGrillage
    @HybridEyeGrillage
    Haha, thanks! I can say that I couldn't have done it without your help (and others from way earlier)~ :smiley:
    Dr Pat Brundell
    @PatrickRB_twitter
    hi, first time here, hoping someone might advise why (I have loads of wikis) in some versions the import of CSV, JSON files works, but in other I get a binary file. Trying to use xlsx importer and it won't work past verison20.
    @yanderella:sibnsk.net
    [m]

    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.

    Dr Pat Brundell
    @PatrickRB_twitter
    That's great, thanks. I suspect there's something broken with the importer. Although the pre-release is available as an empty wiki, there is no updater yet. Can I manually update a wiki without using node.js? (I use tiddlydesktop). Have a great day too!
    @yanderella:sibnsk.net
    [m]

    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.

    https://tiddlywiki.com/prerelease/upgrade.html

    Dr Pat Brundell
    @PatrickRB_twitter
    Thanks for the help, but it seems that there's a problem with Tiddlydesktop and this file. I can open the wiki in Opera and the import works fine, but not in TD - even in earlier versions and going back to default settings
    @yanderella:sibnsk.net
    [m]

    I am not sure how to help you more. However, I can share what I did to test if it works for me.

    1. I use Windows 10 x64 bits. So I got TiddlyDesktop-win64-v0.0.14
    2. I downloaded the xlsx-utils prerelease demo as a HTML file
    3. I downloaded the Presidents and Justices.xlsx to a file.
    4. I loaded xlsx-utils prerelease demo HTML file into TiddlyDesktop
    5. I imported Presidents and Justices.xlsx into the xlsx-utils demo running under TiddlyDesktop
    6. 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.