Categories > TinyButStrong general >

Relative vs. fixed path for images

The forum is closed. Please use Stack Overflow for submitting new questions. Use tags: tinybutstrong , opentbs
By: howman
Date: 2005-09-27
Time: 22:28

Relative vs. fixed path for images

Hi,

I use Dreamweaver to design my templates.  Under my Templates folder I have an Images folder.  Dreamweaver uses a relative link to point to the image.  When I view the page in my browser, the images are not found.  Should I create a fixed path for all of the images?

Thanks,
H
By: Skrol29
Date: 2005-09-27
Time: 22:39

Re: Relative vs. fixed path for images

Yes, because the image path will be relative to the script, not the template. Which is normal. You can also prefixe the image path with a variable but the image won't be viewable in Dreamweaver. 
By: neverpanic
Date: 2005-10-09
Time: 17:18

Re: Relative vs. fixed path for images

Dreamweaver allows you to use a path relative to the site root when inserting an image. If you set up your site correctly this will work and is the better solution.
By: howman
Date: 2005-10-10
Time: 16:14

Re: Relative vs. fixed path for images

Hey neverpanic,

Thanks for the advice.  I will look into it today.

H
By: RwD
Date: 2005-10-12
Time: 16:57

Re: Relative vs. fixed path for images

Of course the even better solution would be using textpad/notepad and a local web server. Then there are no mixed points of view but you can still see what you will get easily.
By: howman
Date: 2005-10-12
Time: 17:26

Re: Relative vs. fixed path for images

RwD, you're such a purist. ;-)

H
By: RwD
Date: 2005-10-13
Time: 07:29

Re: Relative vs. fixed path for images

Really?

Last time I used dreamweaver it was deprecated element frenzy. I also ended up with "<font><b><font><b></b></font> <font><b>&nbsp;</b></font></b></font>" insidt the html.

I made templates for a website and a woman looked at them, changed a thing and suddenly the whole page had changed and the changed part didn't validate. You can probably tell it not to use deprecated elements but I think using propper css methods with dreamweaver is hard?

So it is more because dreamweaver isn't good enough and it gives these problems about the representation anyway (like in topic start)
By: howman
Date: 2005-10-13
Time: 16:04

Re: Relative vs. fixed path for images

Good point RwD.

I think Macromedia is aware of their shortcomings.  Dreamweaver 8 just came out and supposedly addresses your issues.  I am getting a copy at work soon and will let you know.

H
By: neverpanic
Date: 2005-10-13
Time: 17:19

Re: Relative vs. fixed path for images

I am using Dreamweaver and I'm producing xhtml 1.1 valid code without deprecated tags and with perfect shorthand css in there... just depends on what your preferences are.

Dreamweaver 8 even supports validation inside Dreamweaver!
By: howman
Date: 2005-10-14
Time: 05:12

Re: Relative vs. fixed path for images

Hey neverpanic.  Please tell me what the settings are for ver. MX and 8.

Thanks!
H
By: neverpanic
Date: 2005-10-14
Time: 21:10

Re: Relative vs. fixed path for images

Don't use MX (2004) anymore, but the settings are quite similar to version 8.

General > Use <strong> and <em>...
General > Use CSS instead of HTML tags (removes font tags)
CSS Styles > Use shorthand > everywhere
CSS Styles > shorthand when editing > above
New Document > xhtml 1.1 (not availiable in MX or MX 2004, choose 1.0 instead)
New Document > Default encoding > Unicode (UTF-8)
Validator > XHTML 1.0 strict checked
By: howman
Date: 2005-10-14
Time: 21:26

Re: Relative vs. fixed path for images

Got it!  Thanks!

H
By: neverpanic
Date: 2005-10-14
Time: 21:27

Re: Relative vs. fixed path for images

You're welcome.