> I would be skeptical of nesting templates within templates like this,
> as you will inevitably come to some issue BoltWire can't handle.

Boltwire can handle nested templates fine. The only problem is that
the source code gets ugly after a while :p

There is very little with templates that i've not had reason to try by
now. The bugs are mostly gone, and we should always strive to be
completly bug free...

>
> Probably the easiest way would be to create a custom toc function that
> handled this, and remap, perhaps.

But... Boltwire should just work. Puppy eyes!

> As a general rule, I'd encourage you to customize BoltWire
> to make it easier to use, rather than find complex ways to get it do
> those same things.

Yes! We should always customize boltwire so it becomes easy to do
complex things. And then patch it in :p

> But a custom function is not even necessary, as you can change the
> leading character string in toc from 5 spaces to 1 asterisk already.
>
> Go to template.toc and change it to this:
>
> [(toc {+p} leader='*')] [[{+p}|{+}]]

Oooh, pretty.

>
> Don't forget the space between the function and the like.  That's
> necessary for the list markup to be picked up. Actually should just
> have+ for the title...  Next release...
>
> Anyway, then do
>
> [(search params... fmt=toc)]
>
> You have to use fmt, not template because the search function must
> output the raw results unprocessed so BoltWire can then later pass the
> ul markup over the entire section to avoid a bunch of separte ul's for
> each page. Which is what templates do--processes the markup table for
> each page separately.  Plus, fmt is always faster. It is important to
> catch the different between templates and fmts.

Hmm. We should document that better. Write it into the help text for
search, as well as visible in the docs for templates.

>
> Last point, I wonder if we shouldn't make this the default behavior?
> That is * for the default leader rather than '     '. It gives a cool
> output. But spaces are more sure--they work whether fmt or template or
> anything. Maybe it's enough to document somewhere the parameters in
> toc?

Thats a good start. I think using *, as long as it works with the
default skin, would be better, just make sure the examples clearly
show "fmt" and not "template", and put in references to the
differences between them all over the place.

BTW, with the new skin, I found that indentation was working really
badly in the side menu, if you switch between left and right. Bullet-
points would be easyer to fix such behaviour with, spaces would always
be to the left.

>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to