@Jed You've got some seriously interesting stuff there!!! Access to maximum control while simultaneously not overwhelming the user does in deed seem a tricky problem. But I reason that if those major web search engines can make sense out of zillions of webpages, then surely we'll figure something out for a few hundred tweaks.
First of all, I think locating a setting is one thing and presenting it is another. Not that you've contradicted this, I'm just sayin', because I think we can deal with the issues separately. For *locating *something as abstract as, for instance, some particular CSS setting, I think the solution is to attach "all imaginable" search terms to it. Your demo <http://ooktech.com/jed/ExampleWikis/ControlPanelAddon/> seems to indicate you reason like this too. When we eventually federate, it would be really useful to let "the world" attach e.g tags to settings for quick search localization. However (and this problem keeps coming up for me) tags in their current implementation or presentation are not very good for search as you're limited to very few tags per tiddler or it simply looks bad visually. They're probably better for categorization than as search terms. As you may know, I and others have brought up the issue many times ("tag types" and similar terms, as well as hiding tags). Tobias made a solution <http://tobibeer.github.io/tb5/#Search%20By%20Keywords%20Tab>with "keywords" - maybe it is useful for the Settings context we're discussing here? For Settings it is probably not necessary that the user actually sees all meta-search-data so might be useful. Like you indicate with your demo <http://ooktech.com/jed/ExampleWikis/ControlPanelAddon/>, I think tagging (or comparable) would be a key aspect in this. Your modified version <http://ooktech.com/jed/ExampleWikis/OtherMindMap/> that allows searching tags within different contexts should be very useful, particularly as it could allow tagging (or similar) more freely. If users are to be able allowed to tag, then we can expect tags like "important!" or "good" and to have such results appear in context should be very useful. Do you know of the old Tagsplorer macro? It feels related or at least relevant to check out. Unfortunately the hosting site for it is down, but I found this discussion <https://groups.google.com/d/msg/tiddlywiki/KYbX766Ftu8/K4DHi9mcTb0J>. I really like the mobile menus <http://www.google.com/url?q=http%3A%2F%2Fooktech.com%2Fjed%2FExampleWikis%2FText%2520Menus%2F&sa=D&sntz=1&usg=AFQjCNFiqQ9tz3kVu_bvKHnwPQ2f4kXXqw> thinking! Brilliant to let the irrelevant menu items disappear. Did *@Jeremy* see this - as option to his system tiddler explorer <http://tiddlywiki.com/prerelease/index.html#%24%3A%2Fcore%2Fui%2FMoreSideBar%2FExplore>, which he is not happy with? Here is a quick demo > <http://ooktech.com/jed/ExampleWikis/ControlPanelAddon/> of what I am > talking about. I was going to use your sliders to set the values but I > can't figure out how to make them work. > Is this answered with Erics reply, or is it some other aspect? I'd be happy to explain so please tell me what is unclear. > If I can make the I would like to have one of the sub-menus (called 'Page > Layout' or something similar) be the adjustments you have for > tiddler/sidebar positioning and move the font options into an appropriate > sub-menu of their own. > The font options are a bit problematic because when you change them, the whole page can change which makes the fontsliders move. This is why I put them in a fixed box. If we get the min/max/step working, then this might be less problematic. > I think that instead of having the text input like I have now, each option > should be a slider with a select widget that lets you pick the desired unit > and have the options on the slider adjust to be appropriate for the > selected unit (so 1-100 when using %, vh or vw, some range for em, and > another range for px and so on). > I agree that different units are appropropriate depending on which setting, but to have a select widget seems more cluttery than useful to me. Unless you mean another idea I've been thinking of: To have *one *single slider, for which you select setting, perhaps from a select widget. A "central slider" to which you bring whatever it is you want set. Then, maybe, a unit selector might make sense unless it is not already coded as meta data to the thing you want to set. > I think that using what you have made will let us make something to allow > users to make fine adjustments without requiring any knowledge of the inner > workings of tiddlywiki or css. Exactly! The unnecessary knowledge and information should be cut out. The user should be able to focus on working *with *TW, not *on *TW. *Content*, not TW per se. (Unless he wants to, like most guys *here *do.) I like range sliders because they don't force you to know arbitrary "numbers of pixels", or even "pixels" for that matter. But, returning to the ideas on how to locate things, do you have any thoughts on how to generally locate anyting in the Stylesheets? I mean an arbitrary piece like; .tc-page-controls svg.tc-image-new-button { fill: <<colour toolbar-new-button>>; } The first part of the problem is probably that the user must know what he is looking for. A user feeling he wants a, say, different color for the New Tiddler button must know this is possible (until just now, I thought the color change was an image change!). How would he know? And even if he does, he would have to find ".tc-page-controls svg.tc-image-new-button". I'm thinking this latter part may be solved with a listing of all CSS selectors and search terms next to them. A kind of data tiddler. (Further fantasies: Clicking a selector could open a transclusion from the Stylesheet but with only that selector (not doable yet, I guess) and with the property:value presented in a more user friendly way - such as sliders if applicable.) Ok, I'm going off on tangents as usual but I'm getting excited from your demos. Please continue to share your thoughts and tell me if you think I can help out. <:-) -- 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 http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/feee8cfa-8f44-4837-a8cb-615d029dffa7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
