On 02 Feb 2006 10:39:52 +1300, <b class="gmail_sendername">John Rankin</b> <<a href="mailto:john.rankin@affinity.co.nz">john.rankin@affinity.co.nz</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday, 1 February 2006 3:16 PM, John Rankin <<a href="mailto:john.rankin@affinity.co.nz">john.rankin@affinity.co.nz</a>> wrote:<br>>Tegan Dowling wrote:<br>>I'm just trying to use the Wikilist part of the WikiForms recipe to present
<br>>records in tabular form, with those nifty headings that you can click and<br>>re-click to sort-ascending and re-sort-descending.<br>><br>>Can anyone suggest a hack to the recipe that will suppress display of the
<br>>first column?<br><br>For consistency the page name should work the same way as other columns,<br>so it should allow you to omit the page column by writing<br><br> (:wikilist !page:)<br><br>No worries -- download the latest version of
wikiform.php from<br><a href="http://www.pmwiki.org/wiki/Cookbook/WikiForms">http://www.pmwiki.org/wiki/Cookbook/WikiForms</a><br><br><br>But I understand there is a wider requirement, eg Tegan's note that...<br><br>The individual pages for the contacts would not be the numbered pages that
<br>feed the (:wikilist:), because I want the page names to be the names of the<br>individuals, and I want to be able to format the contact pages and add<br>pictures, etc.<br><br>There are at least 2 options for doing this:
<br><br>1. Retain the page numbering scheme, but use a (:title Textual Name:)<br> directive on each page.<br><br> The new [[name |+]] markup could then be used to show the title in<br> the (:wikilist:). This would be relatively easy to implement, it
<br> works "the pmwiki way", but requires an author to specify a title.<br> It is probably more robust than using the person's name as a page<br> name -- what if the name changes?<br><br>2. Modify wikiforms to work off regular page names as well as the
<br> all numeric pattern.<br><br> I haven't seen a good way to implement this as yet. In particular,<br> I haven't come up with a robust way to distinguish between pages<br> that are form-based and pages that aren't. Both the form handler
<br> and list handler will run into trouble if they try to process<br> pages that don't follow the template.<br><br>So I tend to favour option 1. It would need to support sorts by<br>title instead of name, but that is straightforward.
<br>
</blockquote></div>
<br>
Regarding option 2: When you say<span class="q"><br>
"Both the form handler and list handler will run into trouble if they try to process pages that don't follow the template." <br>
<br></span>
What kind of trouble? If they fail in the PmWiki way, by just
returning nothing, then that might not be such a big deal... While I
was poking around in it, I wondered if the new, more feature-full
pagelist might work for identifying and selecting pages with
names. An admin could create a custom "list=" that excludes pages
that aren't wanted.<br>
<br>
Regarding option 1: would the user provide the page title, as part of filling in the form?<br>
<br>
And in either case, will you be able to support allowing formatting of
the form page, (or pulling field contents into a formattable page) for
viewing?<br>
<br>
Thanks a lot for your attention and efforts on this!<br>
<span class="sg">
<br>
Tegan</span>