c5qb-3fe3@spamex.com wrote:
 >> This is a weird error, I agree. I'll see if I can improve it. However,
 >> what you are trying to do is not allowed. quixote_tal.py only allows
 >> legal quixote URLs in path expressions. If you try to access your
 >> images object in your webbrowser you'll see that it doesn't work.

 >I'm not sure quite what you mean by the above.\

I meant that you are using a bad URL. Did you try the URL is your
webbrowser? If you did you will notice that Quixote doesn't allow URLs
that point to lists. In general URLs will point to functions or methods
that take one argument, a request. You can also use a string as a URL
endpoint.

 >  In the examples above, i
 >ensured that 'images' was added to the _q_exports list in line with
the little
 >demo program for quixote_tal.py here:
 >http://quixote.ca/qx/QuixoteAndSimpleTalAdvanced
 >It's similiar to the access of 'name' - except using a different tag,
or do
 >different rules apply to tal:repeat ?

You can't simply say that an object is available on the web by adding it
to _q_exports if it isn't designed to be used on the web. I suggest that
you take a look at some of the Quixote documentation. The
doc/programming.txt file is a good place to start.

Good luck.

-Amos

P.S. Your questions bring up the point that using Quixote URLs as path
expressions with TAL may not be a good idea. I thought it was a cool way
to integrate TAL and Quixote, but it may be too confusing and possibly
not well suited to the problem of displaying an object in HTML. Perhaps
I should change quixote_tal.py to use normal path expressions and add a
new expression type for Quixote paths.

P.P.S. I am not subscribed to the Quixote list, so please CC me with
questions about quixote_tal.py Thanks!