> ... which basically means to create a new feature request at github, to allow the list filter to understand the HistoryList content. ... I'd need to have a look at the source, if it does already.
The problem of course at the moment is that the history list is a JSON tiddler containing an array, and so is not parseable by the current text reference mechanism. One way around this would be to extend the text reference syntax to be able to navigate more complex JSON structures. But a quick and dirty solution would be for the navigator to update a field on the history list called "current-tiddler" that contains the title of the tiddler at the top of the history stack. I'll have a look. For the "open" tab of the sidebar I'd like to have a slightly different behaviour: to highlight the tiddler(s) that are currently visible, taking the scrolling of the story river into account. That would match the behaviour of many docs sites (such as https://www.dropbox.com/developers/core/docs). Best wishes Jeremy On Thu, Feb 13, 2014 at 5:03 PM, PMario <[email protected]> wrote: > On Thursday, February 13, 2014 3:11:20 PM UTC+1, Leo Staley wrote: >> >> On Wednesday, February 12, 2014 3:50:51 AM UTC-7, PMario wrote: >>> >>> On Wednesday, February 12, 2014 2:13:17 AM UTC+1, Leo Staley wrote: >>>> >>>> ...... If you open a new tiddler, the previous one is hidden, but its >>>> title is visible in the TiddlersBar in a greyed out color, as if they were >>>> in tabs. >>>> >>> > >> If you open the "right sidebar: Tools:" menue and activate the "zoomin" >> view, you basically have the single page mode. >> Changing the "tab button" colors will be trickier. At the moment, there >> isn't any CSS class activated, to do different styling. >> >> So, I've been doing hours of digging, and perhaps you could help. >> >> So after installing breadcrumbs and selecting Zoomin, the goal is to get >> breadcrumbs working so that the breadcrumb for the currently open tiddler >> has a different color than the other breadcrumbs. >> > > As I wrote. Any mechanism, that does the selecting of visible tiddlers, > would be needed to add a class eg: tw-xxx-selected to the button of the > active tiddler. This class is needed to create propper CSS rules. > > Ton's _breadcrumbs tiddler is created with a list of buttons. ... If you > have a look at the "ButtonWidget" description, you'll see that there is a > "selectedClass" parameter. But for me it seems it is intended for a > different usecase. .... but anyway ... experimenting needs to start there, > if you want to find out. > > Or you'll need a completely different approach. > > Since you want to style the active tiddlerXXXButton differently, you'll > need to have a look, which existing TW5 mechanism is similar, to what you > want. .... As you wrote, it's the "right sidebar tab" handling. ... So the > starting point is: $:/core/ui/SideBarLists ... it uses the "<<tab>>" macro. > ... So I think, it could be used to create something that could be very, > similar to the "TiddlerTabsMacro" ... but you'd need to create everything > on your own, since Ton's approach is different. > > So it would be needed, to dynamically create the tabs for the <<tab>> > macro or create a new "breadcrumbs" widget / macro ... , that uses the > $:/HistoryList > tiddler > > > The tiddler's which should help us seem to be $:/core/ui/SideBar/Open, >> $:/HistoryList, and $:/StoryList. I can't understand any of the stuff >> beyond seeing that those would be where to start. >> > > For me the StoryList is not the right info, to be used for a functionality > named " breadcrumbs". I'd use the $:/HistoryList to populate the > breadcrumbs. > > So it should be possible to write something like this: > > <$list filter="[list[$:/HistoryList]limit[10]]">...</$list> > > ... which basically means to create a new feature request at github, to > allow the list filter to understand the HistoryList content. ... I'd need > to have a look at the source, if it does already. > > I know, this are no solutions, because atm for me some low level theme > functions are more important. > > At the moment, I'm removing probably "redundant" CSS rules from the > "vanilla" theme. I think the rules used there are way to specific, which > makes modding harder than it should be. Also switching / copying from one > theme to an other may destroy the layout. (As you saw already) > > eg: If you open the $:/core/ui/SideBarLists tiddler in the "story river" > and select the "Open:" or "More: Tags" tabs. Also open them in the right > sidebar. You see, the results are different. .. Which for me points out, > that there is a consistency problem. > > But to prove my ideas, I need to have something that looks exactly like > the existing vanilla theme, and is easier to modify. I also want to have a > responsive % based CSS layout for my desktop. So I can do a browser zoom to > modify the text size without changing the proportions of the overall theme. > A second theme needs to be optimized for mobile devices and an other one > for presentations. All of them need to be perfectly "switch-able" > > In TWc I'm using my own percentage based themes. _All_ of them are > compatible enough to switch between them without breaking the > functionality. But those themes are kind of "old school" with super > complicated StyleSheets. So using "new school" html5 and TW5 stuff will > need some more work, if it should be easy to use too :) > > have fun! > -mario > > -- > 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/groups/opt_out. > -- Jeremy Ruston mailto:[email protected] -- 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/groups/opt_out.
