Folks, Remember the story is a fundamental feature of a tiddlywiki, however within a given tiddler you can create new story views that are somewhat similar to the primary story.
Basically any tiddler can be an alternate viewer of `any tiddler(s). Not only that but the new layout features and $:/config/EmptyStoryMessage can be made to contain a view you want. Regards Tones On Thursday, 17 June 2021 at 09:21:17 UTC+10 iamdar...@gmail.com wrote: > Thanks TiddlyTweeter! My idea came from a personal workflow preference, so > it is rather unique in that sense. > > I also understand where you are coming from regarding a CSS Manipulator, > however, I can also see the major issue there having a background with web > development. > > Having a CSS manipulator macro isn't the issue, it is having the > underlying code available to support it. > > All the CSS changes in my script above, as well as the script it is based > off of, is simply changing existing elements and their behaviors. It isn't > creating new elements. CSS can't do that. I'm pretty sure that Stroll, as a > plugin, adds a new element completely, that is how it can have two columns. > > I also think that Muuri Storyview does something similar. > > I don't think it is realistic to expect TiddlyWiki to include that type of > functionality in its base form due to the level of adjustments needed. It > took the basic of forms because it was a solid decision from a broadly > supported view point. I'm assuming that is why no one has created a "be all > end all" customization plug-in because the effort would be massive. > > IE: If I had my way with my original two row design wish, I would have had > at least two scroll bars, one for the top row and one for the bottom, and > then possibly a third if the two rows together had a height higher than the > user's resolution, or, if they had an index or lots of tags on display. > Then it comes down to; do you want the rows to remain there while the rest > of the page scrolls or do you want the rows to scroll up when you go down > the page. If the height of the two rows is more than the resolution then > you have to consider that you'll be moving the page if you scroll in the > wrong area versus one of the rows. > > The ability to do what we want with TiddlyWiki is definitely there, as it > has been customized by so many already. I just don't think some kind of > blank canvas customization option is possible. Perhaps some kind of layout > picker, where you have two adjustable columns like in Stroll, or two > adjustable rows that work like the columns due in Stroll, or two rows with > the top row being two columns, or two rows with the bottom row being two > columns. Then you could have a keyboard+mouse combination (like Stroll's > Shift+Left Click) to force linked Tiddlers to load inside whichever section > of the layout they are in so you could create a menu/interface type > solution. > > I just think the expectations and goals in what you suggest is similar to > a new type of personal application, versus a fancy or beefed up TiddlyWiki. > > Just my thoughts of course, and I hope I didn't make any offensive > assumptions with your knowledge. I was just trying to cover all my bases in > the examples and reasons. > > Thanks again! > > DM > > On Wednesday, June 16, 2021 at 2:29:16 PM UTC-4 TiddlyTweeter wrote: > >> iamdar...@gmail.com wrote: >> >>> The below CSS is a slightly modified submission by Soren over on a >>> different thread: https://groups.google.com/g/tiddlywiki/c/AbBmtgL7s74 >>> >>> When a Tiddler is edited it drops to the bottom of the screen and stays >>> there until it is saved. While locked at the bottom of the screen you can >>> still open and scroll through other Tiddlers. When scrolling the Tiddlers >>> being viewed go behind the one being edited. Also, the edit Tiddler is set >>> to 500px height so if the Tiddler has a lot of content a scrollbar will >>> appear vs it pushing up the screen and covering more of the stream. I >>> wanted to post it here because the above thread was getting very long and I >>> wanted to share the below code in case it was helpful for anyone else. >>> >>> div.tc-tiddler-frame { max-width: 60em; margin-left: auto; margin-right: >>> auto; } >>> div.tc-tiddler-edit-frame { max-width: 90em; margin-left: auto; >>> margin-right: auto; max-height: 500px; overflow:auto; position: fixed; >>> bottom: 0; z-index:2; } >>> div.tc-tiddler-body { max-width: 50em; margin: auto; } >>> .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor { width: 69%; >>> } >>> div.tc-tiddler-preview-preview { width: 29%; } >>> >> >> Very good stuff! It is clever! >> But, would it not be better if we could collectively produce such >> mini-style-sheets dynamically in TW??? >> >> What I find OFF is any idea there is some "optimal" solution to these >> issues. >> PERSONALLY I simply find the needed solution will often be variable by >> Application??? >> As I mentioned elsewhere, I kinda think that some kind of "CSS >> Manipulator" macro is really the way to go??? >> >> Just thoughts >> TT >> > -- 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/f9b53314-0a17-4607-ada1-c5fd266a1c73n%40googlegroups.com.
