Thanks for the idea on the topbar search, I will definitely give it a try. Also, I've already begun work on the easy font-sizing, you can see it at the demo site <http://j.d.simplemobile.tiddlyspot.com/> ("inspect" on Chrome is quite marvelous in that it allows me to easily find the specific parts of the html that I would like to play with).
On the sidebar. I agree with you, like all of TW5, it is used differently by everyone. In its default state, it's comprised of the *Title*, *Subtitle*, *Page Controls*, *Searchbar*, and *Tabs*. Now, as *I* can't live without the *Page Controls*, *Searchbar*, and *Tabs *part of it, those are the only things I've included in the mobile layout, highlighted them, even. I can't, however, imagine that solves it for everyone, so I included the search options, and am planning to include bottombar options as well. Now, after receiving the idea for a swipe-activated sidebar, and already having search and controls fixed elsewhere, I only thought of the swipe-activated sidebar as containing the *Tabs* in its default state. That's because I wish only to manipulate the position/visibility of default elements, and not to add or subtract functions from them (besides completely hiding the *Title *and *Subtitle*). The option to further simplify/mobilize can be had. However, unless I make each change optionable, I don't think it will sit well with everybody. I might play with further ideas after the long holidays. Thanks for the food for thought! On Tuesday, October 31, 2017 at 8:56:36 PM UTC+9, @TiddlyTweeter wrote: > > Ciao JD > > That work is seriously good because its mobile-centric. Current default > TW CSS is currently "mid-space", half-way between "universal" and "desktop" > -- tablet okay, mobile-phone not always so optimal. > > I have a few comments (including opinions on design) that I hope may be > useful. > > JD - Adjustable font sizes for view title, view body, edit title, and >> edit body (without affecting icon sizes) >> > > Yes. I think its a serious issue. Having desktop font sizing in mobile is > a turn-off. > > Some weeks ago I asked in Google Groups about a button that could TOGGLE > between different CSS. This is a good example of where an up-front button > is preferable to having to wade into special settings files. Given that > "mobiles" come in variant screen sizes & resolutions *easy, upfront, > basic font setting is important*. > > JD - Topbar search hiding on scroll down, showing again on slight scroll >> up (like with modern mobile browsers) > > > If you can't find a way to do exactly like you want an alternative is to > reduce the search bar to just a line of 4 or 5 pixels (using CSS) the drops > down on hover. > > JD - Swipe from edge for sidebar lists > > > Not quite sure you will understand me when I say: though the principle of > this is really good there is an underlying quite complex issue. The issue > being that mobiles are NOT desktops. Its not just about design, its also > about "semantics". Mobiles are fundamentally limited in what can be shown > on-screen at the same time and that CHANGES visual semantics. > > So, IMO, this aspect is not so much about gizmos as understanding what is > the MINIMAL info an overlaid menu should show? Obviously you don't wanna > get into controlling folk's menu (sidebar) content, but the scope of WHAT > is in the "sidebar" (on mobile its "full-screen") kinda matters. > > All that said. A really great step for TW IMO. > > Very best wishes > Josiah > On Tuesday, October 31, 2017 at 8:56:36 PM UTC+9, @TiddlyTweeter wrote: > > Ciao JD > > That work is seriously good because its mobile-centric. Current default > TW CSS is currently "mid-space", half-way between "universal" and "desktop" > -- tablet okay, mobile-phone not always so optimal. > > I have a few comments (including opinions on design) that I hope may be > useful. > > JD - Adjustable font sizes for view title, view body, edit title, and >> edit body (without affecting icon sizes) >> > > Yes. I think its a serious issue. Having desktop font sizing in mobile is > a turn-off. > > Some weeks ago I asked in Google Groups about a button that could TOGGLE > between different CSS. This is a good example of where an up-front button > is preferable to having to wade into special settings files. Given that > "mobiles" come in variant screen sizes & resolutions *easy, upfront, > basic font setting is important*. > > JD - Topbar search hiding on scroll down, showing again on slight scroll >> up (like with modern mobile browsers) > > > If you can't find a way to do exactly like you want an alternative is to > reduce the search bar to just a line of 4 or 5 pixels (using CSS) the drops > down on hover. > > JD - Swipe from edge for sidebar lists > > > Not quite sure you will understand me when I say: though the principle of > this is really good there is an underlying quite complex issue. The issue > being that mobiles are NOT desktops. Its not just about design, its also > about "semantics". Mobiles are fundamentally limited in what can be shown > on-screen at the same time and that CHANGES visual semantics. > > So, IMO, this aspect is not so much about gizmos as understanding what is > the MINIMAL info an overlaid menu should show? Obviously you don't wanna > get into controlling folk's menu (sidebar) content, but the scope of WHAT > is in the "sidebar" (on mobile its "full-screen") kinda matters. > > All that said. A really great step for TW IMO. > > Very best wishes > Josiah > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/6b72af3e-e136-43b4-b77a-6584849673af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
