Thanks for the clarification @BTC. I did a quick mashup adding Stories to your Muuri demo. Works pretty well, you can have Muuri in both stories or just one.
I think having a classic story view in the default story and muuri in the second could be very powerful for making good use of a large screen for some of my workflows. If you are curious, the files are here: Muuri in both stories: https://saqimtiaz.github.io/sq-tw/temp/muuri-stories.html Muuri in the second story only, with the first story only using 35% of available space. https://saqimtiaz.github.io/sq-tw/temp/muuri-stories-alt.html Being able to drag between stories could be very handy. I've considered adding that for the Stories plugin but ultimately didn't have the motivation for it. With Muuri it would have greater appeal. Anyway, don't let me distract you with all the talk of multiple stories :) Cheers, Saq On Sunday, October 18, 2020 at 10:17:55 AM UTC+2, BurningTreeC wrote: > > Hi @Saq, > > >If I understand correctly, does that mean the number of columns would be > have the hardcoded via CSS? Or is there a parameter to the list widget for > it? > > There's no parameter for the list widget for the columns, it's hardcoded > via CSS. I use "width: calc((100% / <<columns>>) - <<margin>> - (<<margin>> > / <<columns>>));" > > >I was wondering if there could be additional optional attributes to the > list widget, such as "columns", which points by default > to $:/state/config/muuri/storyview/columns. > > As said above, the columns aren't handled within the storyview, they are > pure CSS > > >I have also noticed that after changing the number of columns, the layout > of the muuri tiles can be off (overlapping) until one of the tiles is > dragged. Perhaps a refreshEnd reflow is needed? > > Thanks, I've also noticed that, I'll have to investigate further > > all the best, > BTC > > saq.i...@gmail.com schrieb am Sonntag, 18. Oktober 2020 um 10:08:23 UTC+2: > >> Hi @BTC, >> >> >>> 1) I've now fixed your issue with using the core $:/core/ui/ViewTemplate >>> as a template, it does no more lay out using the columns of the >>> columns-button. Their width however needs to be defined using a css... >>> >> >> If I understand correctly, does that mean the number of columns would be >> have the hardcoded via CSS? Or is there a parameter to the list widget for >> it? >> >> I was wondering if there could be additional optional attributes to the >> list widget, such as "columns", which points by default >> to $:/state/config/muuri/storyview/columns. >> >> >>> 2) There's another attribute ("storyList") that defines the tiddler >>> whose list field should be updated. This defaults to "$:/StoryList" >>> >> >> This resolves the refresh issue. >> >> I have also noticed that after changing the number of columns, the layout >> of the muuri tiles can be off (overlapping) until one of the tiles is >> dragged. Perhaps a refreshEnd reflow is needed? >> >> Cheers, >> Saq >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a1d9c23a-587f-43c6-9d2f-28fb6e5dece7o%40googlegroups.com.
