On Wednesday, January 14, 2015 at 9:50:37 AM UTC-6, Tobias Beer wrote: > > I like the concept. > But definitely two good, albeit separate ideas. > > *toolbar* > > I would only show the most common markup by default, at most 7 buttons. > Nothing like sub- or superscript. > Some reveal button could show an extended toolbar when clicked. >
I notice that the Google groups toolbar has 19 icons/elements on it and though it does seem a bit much it isn't as excessive as a Microsoft Office product. There may be a key idea there though. If you only showed 7 or so at a time, it would definitely be cleaner. I rarely use the subscript or superscript but the bookmarklets existed so I converted them and assigned them to the toolbar to test my work. > Which buttons are standard and which are extended, > can be overrun in the control-panel. > > *help* > > Next to *preview* there's a *tiddler* tab... > I presume that was an accident? > The tiddler tab is part of the kludge work-around to make the thing functional. It would definitely not be part of a TiddlyWiki internal editor if I could make it work. In this prototype, it is your main interface with the main wiki. > Personally, I don't like (to use) preview, at all, > So it's a no-go for me to have it always shown. > I agree that the preview should be optional since there are many times the real estate is worth more than the cost of the constantly updating preview. I assume that you would rarely use the Help either. I haven't mastered the combination of the reveal button and the expansion of the iframe to fill the available area. That wasn't relevant to the ideas so I put this up without solving that first. > I would simply have two link-buttons just as there is one right now, not > tab buttons, > conditionally revealing *either* help or preview in the same pane, > the active button / link being highlighted where clicked. > That works as well. Tabs were easier to do quickly on a concept basis. > As for the markup reference, I would definitely prefer to > search / filter for the markup I need rather than tabs. > > Tabs in a narrow space look ugly and don't make searching easy, > especially not when there are 10+ of them. > Rather, use a select box. > I would definitely limit the number of tabs to a handful since something with dozens tend to simply become a cloud. The only problem with a Search filter is that you have to come up with the right word to have a chance of finding what you want. Search for "Underscore" and you won't find "underline." But show a selectbox that has "underline" as a choice, and the user will have no problem finding what they want. -- 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. For more options, visit https://groups.google.com/d/optout.
