List -- In my quest for maximum flexibility within my CGI::Applications, I've been considering the issue of images and resource paths in general.
Interchange (another web development system I like) provides a system that allows for configurable image paths, which really helps when moving from one server to another (or when you need to change where your images are stored.) In Interchange it happens automagicly whenever you use an <img /> tag, which is essentially the end goal for me, template designers shouldn't control (or worry about) the location the images are loaded from. In my practice applications I'm playing with this type of construct <img src="/<TMPL_VAR NAME="IMAGE_PATH">/button.gif" border="0" /> Currently, I substitute this 'IMAGE_PATH' by hand but I will move it to one of those 'automatic' substitutions discussed in '[cgiapp] Enhancement request' [1]. This seems like a good way to manage paths to resources ... anyone else agree? Thanks, Cory [1] http://www.mail-archive.com/cgiapp@lists.vm.com/msg00427.html --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/cgiapp@lists.vm.com/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
