@All, Wow, a lot to comment to :) @Saq
Thanks for the mashups that add Stories to the Muuri Demo, I was really curious if it works out well! >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. My goal is that dragging between stories becomes very easy using the muuri storyview. I hope I can achieve that soon >Anyway, don't let me distract you with all the talk of multiple stories :) It doesn't distract me, I had multiple stories in mind the way I created muuri @TiddlyTweeter >*Regarding mobile* ... where I toyed some. I think there is need to assert an approach and stick with it. In terms of mobile interface it might be better, eventually, to hide the "column number" button (I assume through CSS based on screen size detection?). I'm not convinced of value of even 2 columns on mobile--though it may be my bias in having a rather small dimensional smartphone? On mobile I honestly like the classic storyview more, even if it would need some css tweaking like smaller tiddler titles and less space between tiddlers (my opinion). Still on mobile, using the muuri storyview with only 1 column makes dragging a bit complicated / difficult to handle. On bigger smartphones I think two columns work fine >*Regarding the "Finger Toggle" & scrolling *... This applies to both desktop & mobile, particularly on mobile. It can be hard to scroll UP after moving stuff around with the "Finger Toggle" active to switch it OFF. On mobile particularly trying to scroll up you can just end up moving Tiddlers around rather than actually scrolling up. Maybe the toolbar for Muuri should be attached somewhere so its always visible? On mobile that's a bit of an issue, you're right. There's the need to access the dragging-toggle button to be able to scroll up/down... As @Atronoush mentioned before, there are solutions like Nicolas Petton's Notebook theme that add a bottom panel with the page-controls buttons. Something like that I had in mind, I just didn't want to add another solution to the muuri storyview when there are already many solutions made by others, like @JD or @Nicolas Petton >Further ... I'm glad to see, also, that "*In Tiddler Muuri*" are still supported. Its an extremely efficient way to, for instance, create galleries, as your example shows. Yes, that was important to me. A muuri within a muuri within a muuri should also work (and so on :P ) >I think in actual practice I'd use Muuri to *arrange a site* for online publishing I do NOT want users to mess with. Ok, yes I didn't think about that so much. There's the option to disable dragging and to hide the dragging button from the pagecontrols menu, then disabling the dragging-keyboard-shortcut by removing the tag $:/tags/KeyboardShortcut and doing the same for the columns button and the two columns shortcuts... What I'm getting at is its a tool for content/organisation by developers as much as for end users. Yes? Which tool do you mean? Muuri itself or the dragging on/off button? Maybe? Maybe some hidden option to HIDE the tool could aid publishers publish their arrangement without worry the end user will mess with it? I would go with the options described above... >I just stumbled on what looks like a minor CSS issue ... replication on tablet ... Thanks, you've found an issue I'm investigating :) ! Yet I couldn't find a problem in MY code so I'll leave an issue at the muuri github page, maybe its creator can tell me more about this problem (I hope so) @The Rest about Stories I believe multiple stories have their use-cases since we're manipulating different lists, where one could be the normal story list and another one could for example be a prioritized to-do-list where we can re-arrange tiles. I can imagine, like @Saq wrote, that users can be very creative and use the muuri storyview in many different ways - given that it works well enough. And that's it from me atm, I'm going back to have a look at the code, maybe later today I'll have dragging between stories working... We'll see :) all the best, BTC [email protected] schrieb am Sonntag, 18. Oktober 2020 um 12:00:49 UTC+2: > 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 >> >> [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/44129cce-3d88-4331-b065-a21be59e67f2n%40googlegroups.com.
