It sounds like you're actually proposing two things here.

1) Using Django to serve static files.  There already exists a
mechanism for Django to accomplish this during development, detailed
here: http://www.djangoproject.com/documentation/static_files/ ,
although it's not a good idea to use this in production.

2) Using Django to compile, compress, and obfuscate javascript into
one file.  This sounds like something that's a bit more reasonable,
although some might argue that you could write a utility to do this up-
front, and let the server serve it statically.  Someone has done
something very similar to your proposal, but with images, and you can
check that out here: http://www.djangosnippets.org/tags/imagebundle/
.  The way that amitu went about promoting his/her imagebundle was a
really good approach: write some code, paste it to djangosnippets.org,
and see if others find it useful.  If you're looking to implement your
Javascript obfuscation and merging filter, you might want to go a
similar route.

Hopefully that helps.

-Eric Florenzano

On Dec 11, 6:30 pm, "Mike Scott" <[EMAIL PROTECTED]> wrote:
> Hey All,
>
> I've been looking at how to better serve my static files for django sites,
> and I'm particularly interested in things like Javascript handling.
>
> For example if we were to look at RoR, they have their include tags which
> can automatically compile javascript into one big file, compressing and
> obfusicating it.
>
> Is this an approach the bulk of the Django community are interested in
> taking or is it something that we should leave to the things that do it
> best, ie: Apache and the like.
>
> Regards,
>
> Mike Scott
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to