On 5/28/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > On Mon, 2007-05-28 at 19:31 +0800, Russell Keith-Magee wrote: > > 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. > > > > 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? > > One "worst case" is using the Yahoo UI library and having the URLs for > the Javascript components point to Yahoo's external hosting. Which is > recommended practice (huge caching benefits).
Granted. > What is you problem with Ivan's suggestion of not munging absolute URLs? I have a bit of a Pavlovian response to the suggestion of output behaviour that varies depending on the exact magic format of the input. However, that said, I'm not completely opposed, and I can't think of an obvious better solution. I mostly just want to make sure that I fully understand Ivan's use cases, so we can make sure that there isn't a better solution lurking around. Thinking about the problem some more, I'm fairly certain my 'widget library' objection is bogus - judicious application of a setting when specifying media references should get around any library portability problems. 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 -~----------~----~----~----~------~----~------~--~---
