I'm far from an expert on CF frameworks but I think I have to at least partially agree with Matt's point here. I did write a primitive "scripting language" back in my video game days and looking back now, the script file I built then was nothing more than a data file - name/value pairs and not a whole lot else (there are a bazillion variations of these in video game development).
And later on other projects, the teams really were building true scripting languages into the app's engine. My name/value pair-style config files were replaced by things with if() statements, for() loops, etc. (there are a bazillion variations of these too in game code.) Maybe it's because of my particular background (as opposed to whatever Patrick's is, or anyone else here for that matter), but the XML "controller" files in Mach II always reminded me more of these custom scripting languages than just a data file. So yes, I can definitely see how both camps are right: xml data files have their place, as do the fancier versions of them we see in Mach II, et al. </de-lurking> </babbling> Nolan Erck Web Developer/Programmer Schools Financial Credit Union (916) 569-5409 Office (916) 569-2024 Fax www.schools.org -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Woodward Sent: Friday, October 28, 2005 7:40 AM To: [email protected] Subject: Re: [CFCDev] CFSQLTool debate On 10/28/05, Patrick McElhaney <[EMAIL PROTECTED]> wrote: > I must jump to Joseph's defense here. I think ColdFusion framework > developers became infatuated with XML a few years ago -- starting with > XML fusedocs -- and it's gotten out of hand. Sure, let's ignore all the benefits that going the XML route provides. It's just a fad. > I don't understand what was wrong with simpler text-based formats, > such as the java properties file and windows ini file. I thought that > a config file should only specify details; it should not implement > business logic. And I thought that's why config file formats tended to > be so constrained. The idea of an eXtensible format for config files > seems backwards to me. If we were dealing with simple properties files I'd agree with you, but we're not. In the case of Mach-II the XML file is a controller file (as it is with numerous other frameworks even outside the CF world), it isn't just simple name/value pairs, and using XML is perfect for this purpose. Now you may disagree with using XML for this purpose but I'd have to hear a better argument than "it's wrong" or "it's gotten out of hand" to understand what you think the DOWNside is to using XML in this way. -- Matt Woodward [EMAIL PROTECTED] http://www.mattwoodward.com ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected] The information contained in this e-mail is confidential and may contain privileged information exempt from disclosure under applicable law. The information is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, employee, or agent responsible to deliver it to the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please delete the message from your computer and immediately notify the sender by telephone (you may call collect) at 916-569-5400 or by e-mail to [EMAIL PROTECTED] Thank you. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
