Seems to have been working, but with imperfect css. I've copied over the code I'm using and tweaked the css. Try the new script. Just test first on a clean install, then introduce carefully into your site as other css settings might possibly interfere. I also enabled it on the BoltWire site to show an example...
I did notice small bullets show up in Chrome but not IE. Real pain--can't seem to get rid of them. Oops, now they are on IE too. Though the settings specifically should have them turned off... Any css gurus that care to help with this, I'd appreciate it. It works on my site, not sure why it doesn't here. Don't really want to spend more time on this personally... :) Cheers, Dan On Fri, Jan 8, 2010 at 11:14 AM, Bogdan <[email protected]> wrote: > Actually test.dropdown doesn't work. May be it is not updated to the > current version of BW. > > It would be nice to see the plugin in action. > > Bogdan > > On 8 Ян, 15:52, The Editor <[email protected]> wrote: >> On Thu, Jan 7, 2010 at 7:44 PM, Erlend Sogge Heggen <[email protected]> >> wrote: >> >> >> >> >> >> > This is one feature I've always missed in all wikis. >> >> > What if you could make a simple navigation box, just like a TOC in >> > terms of looks, to display all sorts of page-groups. Say, all the >> > pages with the same parent, in the same category, or in the same >> > 'trail' (see the plugin). >> >> > Through the admin menu, you would have those terms to sort between >> > (i.e. 'parents', 'categories', 'trails'). You'd pick one, and from >> > there you could select for instance the 'cats' category and from now >> > on there would be a in-page navigation for all the pages within 'cats' >> > for all pages in that category. >> >> > (To differentiate it from the TOC, maybe it should be a boxed in (just >> > by default style wise) horizontal menu, with the possibility to scroll >> > through it by JavaScript. Too much? Just throwing it out there :D ) >> >> There is a drop down >> menu:http://www.boltwire.com/index.php?p=solutions.javascript.dropdown >> >> I think you could probably get that to do what you want easily enough. >> You would have to create a variable for parent page, category (I use >> info.tags for my tagging), and trail (just a page with a list of links >> called trail.whatever). Generating the last two might be a bit tricky >> if you wanted to make this site wide... How do you know which >> tag/trail to use on a given page? >> >> <dropdown> >> + [[{parent}|Parent]] >> [(search group={parent} fmt=title)] >> + [[{category}|Category]] >> [(list '{info.tags::{p}}' fmt=title)] >> + [[{trail}|Trail]] >> [(list {trail} fmt=title)] >> </dropdown> >> >> Two observations--the above is not tested, just seems like it ought to >> work. And second, if you put this on every page you are getting a >> performance drain. You would have to weigh the pro's and con's of >> this. But it should be easy enough to setup. >> >> Cheers, >> Dan > > -- > You received this message because you are subscribed to the Google Groups > "BoltWire" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/boltwire?hl=en. > > > >
-- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
