Problem with CSS, JS, and IMG directory paths

[eluser]ryantxr[/eluser]
This one of the annoying things about CI. Creating links to CSS and other assets work differently at runtime than at design time. If you use tools like DreamWeaver and other similar tools, the links have to be different for the design tools than for runtime when actually running through CI.

Take this example:

At run time:

Code:

http://localhost/hookon/index.php/main

The view for this file on the development workstation would be located in hookon/system/application/views.
Assume that this file has a GIF included. If it was a simple html file, the tag would be as follows:

Code:

<img href="../images/nav.gif" />

For the tool's purposes, the images folder would have to be in hookon/system/application/images.

When this gets uploaded and run through CI, the images cannot be located at this spot. The resulting output will not find the file. On the deployment platform, the web server, the images folder would have to be located at hookon/images.

While it is not a huge deal to move the images folder, you can see how this could get more complex if the number of files increases. Additionally, tools like Dreamweaver are very intelligent about including other assets. Furthermore, files can be uploaded to web servers by Dreamweaver, and it maintains the folder structure. There is no way to tell it to automatically move certain files.

So I am wondering how any of you deal with this difference.