On Tue, Sep 22, 2009 at 1:10 PM, Kevin <[email protected]> wrote:
> This has been a fun but frustrating project... still learning how things go
> together...
You are making good progress. Before long you'll be whipping stuff out
with no trouble.
> The page creation and now listing (using search) works pretty well.
> Actually tried it early this morning with a real issue to see how it would
> look.
>
> Updating is not going to work the way I had planned it though...
>
> Originally, I had planned on having a form that would collect the update
> info, and then modify the existing page by adding the content to the end of
> the page.
Why not use the commentbox plugin? Very simple. And faster than having
all the updates on a separate page. Also, makes it easy to rename or
backup files--all the issues on one page.
Just install the plugin and put [(commentbox)] in whiteboard.footer.
> However in play with this manually with a real issue last night, I found
> that adding updates to the bottom of the page is not very intuitive.
Basically it takes something like
[box content][box]
[session source {p}]
[session edit "{=source}\n{=content}"]
...
This is one example of where the \n is really useful.
> [(search group=whiteboard.* pattern="/whiteboard.\d{10}/" order=reverse
> sort=p2 count=20 template=wbtemp)]
>
> Thinking it would only match the first level, but that didn't seem to work.
The * means all the sub pages down. Without it, all the child pages
only, no grandkids.
So you could do group=whiteboard and you probably got it.
There's also this
[(search group=whiteboard* if='equal {+p0} 2')]
As for your pattern my guess is you need to correct the pattern.
Perhaps something like:
"/^whiteboard\.\d{10}$/
The . needs to escaped and you need a $ at the end to block the grandchildren.
> sort=p2 count=20 template=wbtemp)]
> If I can get that to work, I could then simply treat updates as sub pages to
> the original issue, create a search for it that then displays them on the
> issue page.
You got the gist of it. But the comment box is faster and easier and
can be customized as desired.
> It looks like I will end up using a skin for these pages as I can then add
> common parts that are not actually in the posted pages themselves (like the
> table of updates, buttons for updating etc..)
Normally these go in whiteboard.header or whiteboard.footer. Or even
whiteboard.side, etc. You shouldn't need a new skin. Just use
BoltWire's hierarchies for you zones.
> Will be the first time I have tried that.
If you do create a skin, call it
code.whiteboard.skin or code.whiteboard.skin.myname (depending on
whether or not you are using the core code.skin. This is hierarchies
at work again. But you should be able to do it with zones.
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
-~----------~----~----~----~------~----~------~--~---
