← Back to team overview

sloecode-dev team mailing list archive

Re: URL mappings of resources

 

Hi,

On 1 January 2012 11:28, Guy K. Kloss <guy.kloss@xxxxxxxxx> wrote:

> This has worked surprisingly well considering the hiccups I've
> experienced with this half a year ago. The "h.url(...)" URL rewriting in
> the HTML templates works as expected.
>
>
Good to know, thanks!


> However, there are some resources that are referenced from the CSS
> files. These use a different notation: "url(...)" (not using the
> preceding "h."). These ones all fail. Therefore some images and other
> referenced CSS files do not translate correctly and can't be found. So
> far I've identified these resources that are suffering from this:
>
>
Ahh yes... the url() syntax is a part of CSS, not anything to do with the
templates at all. I can't think of a solution to this at the moment, but
I'm sure it's been solved, so I'll ask around online. In the mean time, if
you could post a bugreport against sloecode with this info that'd prompt me
to take action once I get back to Dunedin.


>
> When looking at the source of the Sloecode tree, I'm also somewhat
> surprised of the file system structure. I'm sure this is due to the
> organic growth of it during development, but it may ask for a little bit
> of cleaning up. The "public/" directory contains a whole bunch of images
> (PNGs) in its root. It may be cleaner to migrate these to the
> public/images/ subdirectory to keep things cleaner.
>
>
Yes - that's it exactly. It needs to be cleaned up. Thanks for reminding me.


 Cheers,


-- 
Thomi Richards

Follow ups

References