"Adrian Holovaty" <[EMAIL PROTECTED]> writes:
> If you just want to use the HTTP request/response part of Django,
> there's no requirement that you need to use a database.
>
> All Django cares about is that your view functions return an
> HttpResponse. What they do internally -- whether it's connecting to a
> database, or connecting to your ReStructured Text source -- is
> entirely up to you.
>
> def my_view(request):
> t = get_my_restructured_text()
> return render_to_response('mytemplate', {'text': t})
>
> There is no reason you'd have to store your text in a database, except
> if you wanted your text to be edited by Django's admin interface. But
> if you're using SVN to manage your data, you wouldn't want that,
> anyway.
So the idea is to map certain URLs into that view, have the view parse
the URL to find the files in the SVN working copy that it should use
to generate the page, use those files to generate a data structure on
which the template can operate, and pass the data structure off to the
rendering code? Wow, suddenly that looks easy.
Thanks :)
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
