For those of you who stumble accross this thread with the same question I had in the first post: I've found a solution.
Basically you use quixote's _q_lookup method to map dynamic URL's to objets (which you've defined in your quixote framework folder). The methods in these objects don't need to be exported - and as far as dynamic links go, all that happens is that _q_lookup(request, value) calls the object class, passes it the value (which is basically the end of the url string) and calls the respective method that you've defined to handle that particular value.
You can also implement checks to allow one to call different methods depending on the value's data, type, range etc.
Very useful indeed!
You're wondering what the use of all this is?
Well say you needed to link to a page called "EditStats" and based on the user that's logged in, say Bobby, you need to call "EditStats/Bobby". Now, Bobby is dynamic, therefore there is no way of having a static method called Bobby in your EditStats object (.py script). So you basically have a generic method (ie: dispDetails) which is called from the _q_lookup method, and the value Bobby is passed to it.
This would allow one to have a dynamic link:
user = getUser() #returns "Bobby"
<a href="EditStats/%s">Edit stats</a>
""" % (user)
This link is therefore generated on the fly, depending on the user, and when you click on it, quixote first maps "EditStats" to your EditStats object, and then looks for the "Bobby" method. Since this method doesn't exist, it then calls _q_lookup(request, value) which in turn calls the generic method dispDetails(value) that renders your page for editing Bobby's data.
I sure as hell think so.
Hope this helps peeps with their quixote.