>Then those template tags would depend on DjangoContext -- that couples >DjangoContext to the template tags, which is bad. :-/
Exactly. It would be a much better way to invent a "PaginationHelper" object that will - on creation in the view - take stuff from the request and would be used in the pagination tags. That way the tag only depends on that special object that is directly related to the tag and could easily be exchangend in situations where needed by some other object that just implements the same API. It might sound like overkill, since the pagination mostly needs the selected page number, but encapsulation would help with for example using the django templating system in the context of a twisted application, if the developer is used to Django templating and just happens to need something from twisted (or any other different server thing). Being able to reuse many of the Django parts is a really nice thing, so keeping the decoupling intact should be high on the priorities list. bye, Georg
