

If this storage is cleared up, these fields are empty. The widget are only stored in the current browsers local storage. > setTo="open" class="tc-btn-invisible tc-popup-keep"> \define timeline-expandable(limit:"100",format:"DDth MMM YYYY",subfilter:"",dateField:"modified") Save and observe the results! I hope it works and is what you wanted. So create a new tiddler, with any name you'd like, for example $:/custom/macros/timeline-expandable and then tag the tiddler with $:/tags/Macro and finally and most important, put the following macro as body of that tiddler. Now so that all this said can work, you must make a new Tiddler that contains the macro itself that I made just now. This should create a new tab in the sidebar and if you want to get rid of the original Recent tab, you'd need to go to the Tiddler $:/core/ui/SideBar/Recent and remove the $:/tags/SideBar from it. Now, if you want to make this into a tab, you'd need to create a new tiddler, with any name you'd like such as $:/custom/ui/SideBar/Recent-Expandable and tag it with $:/tags/SideBar and put that macrocall widget as body of the tiddler and add a field caption with the text you'd want to see in sidebar such as "Recent ToC" and if you want it to be in front of the "Open" tab, you can add a new field list-after with value of $:/core/ui/SideBar/Open Here is how you'd call the macro that I just made. However, since this is foldable, I decided to put the limit to be higher than 100 so I thought 250 is okay. The usage for this are few, since it is a macro you can call it from any tiddler, the calling happens exactly how it was for the Recent tab in the sidebar.

So I decided to use my knowledge and these two macros "timeline" and "toc-expandable" to create a kinda basic macro that is purely based of "timeline" but is foldable. Basically, the recent tab uses a builtin macro called "timeline" which is different from ToC. I did my take on this problem, however it kinda got long to explain it. I hope this helped to clarify some things. So consider experimenting with the prerelease. You can find the pre-release of TiddlyWiki at: It did give some warnings but it worked for me. It seems to import there correctly and the Demo page works just fine for me. You can find the prerelease of the Demo page here:

So consider using the pre-release version of TiddlyWiki and the plugin. However in the prerelease, this seems to be already fixed. Upon importing the Presidents and Justices.xlsx, TiddlyWiki returns a RSOD: Uncaught TypeError: Cannot read property 'getTiddlerText' of undefined So following your comment, I can confirm that the xlsx-utils demo does not work for me in both Chromium and Firefox. on a more serious note, I didn't get "in depth" with the. So I'd recommend the JSON format as the main if you have to deal with set of tiddlers between different TiddlyWikis.ĬSV 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. (I quickly tested what I was saying and I seem to be right. 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. 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. 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
