OK you macromedia peeps, please take this suggestion back to MM HQ. Anyone on here who uses a framework/fusebox will agree.
DWMX sux when it comes to developing an app that isn't built with stand alone pages. Such as if your using a framework where pages are cfmoduled or included. None of your CSS will work, none of your image paths will work etc. DWMX needs the option to specify virtual root paths, default relative or absolute image paths, default stylesheets to apply to documents without linking or embedding them, and all these similar settings that will allow included/nmoduled files to display correctly in dreamweaver. Otherwise you just end up with templates with broken images, no styles, broken links etc cozz DWMX cannot work it out. Russ Michaels Macromedia/Allaire Certified ColdFusion Developer CFDeveloper The free resource and community for ColdFusion developer. http://www.cfdeveloper.co.uk Join the CFDeveloper discussion lists. To subscribe send an e-mail to [EMAIL PROTECTED] -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
