On 5/27/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > Russell Keith-Magee wrote: > > URL path. When rendered, it should take into account settings.MEDIA_URL. > > As a matter of fact it's not a universal practice to have css and js > filed under this root. A couple of my projects had them in separate > places (even js separate from css). It can be handled as simple as > checking if Widget's media() (or a Meta-class) already contain an > absolute links and only if they don't the join it with MEDIA_URL.
Hrm. I see the problem, but I'm not sure I'm wild on that suggestion for fixing it. One outcome I can see from this proposal is the possibility of widget libraries; allowing absolute paths doesn't really serve to promote this goal. When you say JS and CSS are separate - how separate are they? What relationship (if any) does the path to CSS and JS have with MEDIA_URL and MEDIA_ROOT? Can you describe the 'worst case' URL space that Media objects would need to be able to target? Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
