The reason is that the library and template functionality actually let you see in Dreamweaver what you are working on while you work on it. But not only that, if it worked correctly (which in this case it didn't), the resulting html only code will run on any server that can serve up html, regardless of application server or SSI functionality.
It does have its advantages, but of course has to work correctly to leverage those advantages. As an FYI, all of the library and template functionality is enabled with commands contained html comments on the target pages. - Calvin -----Original Message----- From: Will Tomlinson [mailto:[EMAIL PROTECTED] Sent: Sunday, March 13, 2005 1:35 PM To: CF-Talk Subject: Re: GRRRR Dreamweaver broke my client's web site I'll actually go one further. I'm no DW exeprt by any means, but why anyone would use templates and libraries makes no sense when you could just use SSI's. Not saying anything about Mike's judgement, just making a statement about DW here. Why would I use them when I can use a SSI, change it in one place and just upload *ONE* updated page? There's no scary "do you want to update all files blah blah"? THAT thing is worse than The Grudge! THEN you have to upload all the changed files? Screw that! My two cents, O-->Will<--O ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:198636 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
