searchArgs when table rendering

[Mike Myers]

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.

As Sam correctly points out, a URL like this fails because it jumps over the
renderTableWith directive:

  mysite/category1/default?topic=blah

So the easy way won't work. If I really want to do this, I'll have to
re-tool with an objectNotFound handler.

Thanks Sam,

mpm