[EMAIL PROTECTED] wrote:
> For example, the "feature" of not serve static files. The worst? I
> don't can relly in the available workarounds to this "feature" (yeah I
> put "feature" for be sarcasting... I understand the reason, the why,
> but be patiente: I have a deadline too and this experiment is taking
> more than expected!!)
>
> [...]
>
>
> I think this is the way if is expected that normal web designers build
> the front-end of the system...
>
> I talk with my designers and think is not that bad use a "template
> language" if that mean total freedom to desing (in contrast to *nuke
> CMS, I mean). But is a total requeriment to see what is happening with
> the css/images/etc.. in desing mode...
This is what I do for dev work:
- put all my static in a folder, eg:
/home/dev/website/static/
- tell the toplevel urls.py where to get the files:
STATIC_LOC="/path/to/static/"
urlpatterns = patterns('',
(r'^static/(?P<path>.*)$', 'django.views.static.serve',
{'document_root': STATIC_LOC}),
)
- markup in templates like this:
<link rel="stylesheet" type="text/css" href="/static/css/screen.css">
One tip: don't start your path with '/media': it might conflict with the
admin app if you have it installed.
cheers
Bill
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
