Try changing line 21 in $:/plugins/phiv/streams-fusion/turndownMacro.js
from
window.TurndownService = require("$:/plugins/sq/typewriter/lib/turndown-browser-umd.js");
to
TurndownService = require("$:/plugins/sq/typewriter/lib/turndown-browser-umd.js");
I was about to release @saqimtiaz fix, but my testing uncovered this is a fix that works only on node.js deployments…
Will try to integrate @cdaven’s superior conversion library today.
I am tied up at present so don’t have the opportunity to fiddle with code, but the other quick fix to attempt is to add this to turndownMacro.js:
exports.platforms = ["browser"];
I’ve pushed version 0.0.14 which removes the turndown library completely (and AFAIK the issue reported with node.js deployments).
For the time being, the optimal way to export to markdown is to fuse to a new tiddler as wikitext and export using @cdaven’s Markdown export plugin. I will try to improve on the theme and use the library without having to export to file. This will require changes to cdaven’s plugin.
We probably need to change this discussions title to remove “(including to Markdown)”
Thanks, with version 0.0.14 everything seems to work.
Hi @saqimtiaz does the typewriter plugin still work on the new version? I got an error screen after intalling it.
@fastfreddy
Hello, I’m loving how Streams-Fusion extends the ‘exportability’ of the base streams plugin.
Is there any way to perchance to export ALL the Streams currently open in your story view? This would be great for creating longer documents from a bunch of smaller streams or sub-streams or even nodes.
Just let me know, thanks!
-Xyvir
Should be relatively easy. Let me look into it over the next couple of weeks.
Have you tried filtering in the Advanced Search Filters tab, then export from there? Although I have not used the aforementioned exporter this is possible with other exporters.
Updated: As per default tiddlers “Retain Story Order” option the filter to use to select all open tiddlers is [list[$:/StoryList]] but you may want to use [list[$:/StoryList]] -$:/AdvancedSearch
I put together a proof of concept today. Seems doable (and am indeed using the same [list[$:/StoryList]] filter suggested by @TW_Tones above in a list widget to loop through the generation of the fused output).
Will refine and do some minor refactoring (the code is a mess, but I probably can’t tackle more meaningful changes at this time). I did find a trivial bug investigating this though, when selecting raw HTML output. Released the bugfix just now. I am surprised this didn’t surface earlier.
I am probably going to add an optional page icon when wanting to fuse the full story list. If that is not likely an approach that works for you, please circle back here.
Also need to confirm you only want open Stream parent tiddlers (and nodes) to be fused, vs all open tiddlers? Easy filter tweak to [list[$:/StoryList]has[stream-list]]…
Correct, just the streams-tiddlers. And a page icon works fine! Thanks for working on this!
Just released v.0.0.18 which provides the functionality you are looking for (as far as I can tell). Please give it a shot.
Please note that the page icon’s feature to fuse tiddlers in the story river is not shown by default, but can be enabled by turning on the relevant setting under Control panel → Streams settings → Configuration → Streams-fusion: Show page icon. The default filter for this feature is to fuse only Stream tiddlers present in the story river, as requested, but the filter can be customized to something else.
@saqimtiaz : I have had to tweak (and sadly package along again) the $:/plugins/sq/streams/Settings/config tiddler to insert [[$:/config/PageControlButtons/Visibility/$:/plugins/phiv/streams-fusion/ui/page-button]] in the list filter so that the page icon visibility setting is also shown on the configuration page (which I think makes sense). Not ideal to override the original $:/plugins/sq/streams/Settings/config tiddler, and I tried various forms of transclusion to have the visibility setting included there, but did not succeed. Inserting instead a more generic filter run would probably make more sense, e.g. a Streams config tag in addition to the prefix-based filter run, as it would be more flexible than my current approach. Happy to converge, as you see fit, in future releases of this $:/plugins/sq/streams/Settings/config tiddler.
Thanks! I’ll check it out
