On Wed, Feb 18, 2009 at 3:02 PM, Lino <[email protected]> wrote:
>
> The great thing with hierarchy pages is also
> 1. hierarchy tree copy, for use as template tree, (new projects,
> multilingual pages.. you name it),
> 2. actual nesting in i.e. QM systems (ISO 9001 is perfect example.
> Here is page data another excellent (approval) tool)
> 3. rentree for archiving whole projects..
>
> I don't care about how deep it is, as long as it includes everything I
> need. Besides, we can always put toc in header zone of the page.
> **TOC question here**
> How to reduce indent in TOC display? It is now some 20px and I would
> like to have it 10-ish. Could not find where to set it...
It's actually 6 character spaces, not px. You can set it to a smaller
number (down to 3) by adding leader=' ' in the toc function. Or
anything you want. Try leader=' > ' for a cool effect... There's
also an offset to bump everything down a notch. Try doing
?p=some.page&help=toc. You'll fnd the info there, assuming you have
your help system turned on...
> Dan, I have bad news about action.child page: preview is creating new
> page and preventing you in further editing in the same box. I tried to
> figure out why and have several hilarious explanations, but not one
> helpful.
Ah, yes, guess it would do that, wouldn't it... My mistake. The warn
line needs to come before the target and create commands. Like this:
! >>Create Child Page<<
[form]
>>Name of child page you want to create in {p}:<< [text child size=25]
[if* set {?boltkey}]
[(preview content)]
[if*]
[box content cols=60 rows=16 gui=true][(preview content output=escape)][box]
[submit name=boltsubmit[] value=PREVIEW][submit name=boltsubmit[] value=CREATE]
[session if "equal '{=boltsubmit}' 'PREVIEW' ? warn=Preview Mode."]
[session warn]
[session target {p}.{=child}]
[session create {=content}]
[session author {member}]
[session changesummary "Page created by {=author}."]
[session savedata author,changesummary]
[session nextpage {=target}]
[form]
> Anyway, I'm using my first solution... In this case only thing to
> improve is check in the action.create. Since I'm redneck and we still
> have no redneck.help pages;
> Q2: how to clear {p} if it is action.create? Something like [if "equal
> '{p}' 'action.create' {p}=' ' "] - to clear page name box and make it
> looks like before in regular create?
(Going back to your original email...)
[text target size=80 {p}]
needs to become:
[text child size=80] // the {p} supplies the content of the box...
[session target {p}.{=child}] // this lines sets actually sets the
target, by combining current page and the contents of child.
> PLEASE: don't make create.aunt function. I already have one.....
All right. As long as she can help out with your page creation needs.
Aunts can be pretty helpful. I got a great one myself... :)
Cheers,
Dan
P.S. Note, in the next release you can just put =child in the create
box and it will automatically become a child page. That should be a
nifty little addition to BoltWire's tricks...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
