line any of the millions of >developers who don't use Dreamweaver.
Irvin, are you actually familiar with how DW templates and library items
work? They're not at all like Front Page or other proprietary tags or
objects. They're just regular HTML code surrounded by comments like:
<!-- #BeginLibraryItem "/Library/Footer.lbi" -->
Bunch of code here
<!-- #EndLibraryItem -->
When DW sees the comments, it knows what to do with the wrapped code. Other
software (editors and browsers) safely ignore the comments. If you want DW
to no longer recognize templates or library items, all you need do is strip
out those two comment tags.
Assuming one doesn't have access to server side scripting, this type of
functionality does make life much easier for the developer. It's a lot
easier to change one library item and have DW update 100 html pages, than to
manually update the 100 pages individually, or (as you pointed out yourself
earlier) risking a botched site-wide regex operation.
I think you've made your points well about choosing some form of includes
whenever possible, but that's not to say templates/library items don't
provide some benefit when includes are not possible. And then sometimes,
includes may be possible not be practical -- for instance, in a hosted
environment, where you can't control the server configuration and you don't
want to change all your pages from .html to .shtml (resulting in 404's) in
order to use SSI. And before you say it, I know...that's time to change
hosts!
-------------
Regards,
Bob Haroche
O n P o i n t S o l u t i o n s
www.OnPointSolutions.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
