searchArgs when table rendering

[Samuel Reynolds]

>On 4/22/02 6:58 PM, "Samuel Reynolds" <sam at spinwardstars.com> wrote:
>
>> The logic for deciding whether to render a table as a page or
>> to treat it as a subdirectory doesn't always work  the way you
>> expect it to. The dynamic webserver doesn't render the table
>> as a page if The Walk doesn't see #renderTableWith *before*
>> it gets to the table. And you are probably jumping right over
>> the directive.
>
>(A stupid error made me think that the tableRenderer was not being called.)
>
>Your comments about the directive location made me go back and try adding
>the searchArg to the URL one node up.
>
>structure:
>
>Mysite.#renderTableWith    = name of script in #tools
>Mysite.category1.default   = @somewhereElse1
>Mysite.category2.default   = @somewhereElse2
>
>URL:
>
>  mysite/category1?topic=blah
>
>That will render without error, but the searchArgs subtable in the page
>table remains empty. Perhaps mainResponder could be changed to propagate the
>search argument in these situations, but I doubt UserLand is interested in
>touching that.

You can parse the searchargs yourself, you know.
They *are* in the page table. (Crib the code from
the ONFH tutorial; it's a few lines in [one or more
of] the scripts.) Could be the simplest change to
make to make it work as you'd like.

I'd still go with the ONFH approach, myself, because
it can allow you to add categories & topics without
making any change to the site; the ONFH can handle
them automagically. (I.e., you wouldn't even need
the Mysite.categoryN entries.)

Glad I could help.

- Sam
_____________________________________________
Samuel Reynolds         sam at spinwardstars.com
Custom Software Development
Put the two-way web to work for you.
http://www.spinwardstars.com/