10 jul 2011 kl. 19.15 Rustom Mody wrote:
On Sun, Jul 10, 2011 at 10:03 PM, MiB <[email protected]>
wrote:
10 jul 2011 kl. 16.44 Rustom Mody wrote:
So any tips on figuring out paths in html/css/js?
Always acknowledge from where the path starts, ie where the document
is in relation to the path targets.
Acknowledge? I dont understand...
Hmm, not the correct word perhaps. I meant note where you are in order
to know from where you want to fetch anything.
Graphics that are meant for CSS decorations are IMHO better placed
within the same folder as your css file, wherever that is. If so
"images/" in the path will work just fine.
Well... In my current state of wisdom about html/css its usually not
very clear where things should go. Eg a logo should probably go
into the html whereas border designs etc should probably be in css.
In other words Content goes into HTML. Graphical design elements go
into CSS.
If I need to get a graphic from somewhere else, I tend to go from
the server root, ie starting with "/" and then [full-path-to-file].
Server root only works when files are served from the web server, it
doesn't work locally from the HD.
But then that's a pain to debug/try out first locally before
uploading. [Or am I missing something?]
Why aren't you running a server on your machine — set up more or less
exactly like the one you plan to serve from — when you develop? That's
what you're missing. Are you going to serve files on server to server
local browsers. I think not. So why complicate things with having 2
differing environments for you site?
/MiB
--
--
You received this because you are subscribed to the "Design the Web with CSS"
at Google groups.
To post: [email protected]
To unsubscribe: [email protected]
