Frameworks without the XML
I'm so glad someone other than me said this. This is the Steve Nelson is quoted in the latest Teratech Interview:
In my opinion, using XML files to create a new framework programming language has more drawbacks than benefits. The biggest drawback is that the developer needs to learn yet another series of tags and syntax and keywords in order to use a framework
I agree whole-heartedly. I've always been uncomfortable with the fact that I need to learn a new XML dialect to program with the most common CF based frameworks.
Steve says he created a version of the Fusebox framework without any core files or XML configuration. It's entirely based on CFCs.
Unfortunately, I can't find a link to the interview.
Update: Steve's interview was was posted to the webapper blog




However, the post notes that nothing was recorded and no files were available yet. On the upside, he did mention that he will present this at the Frameworks conference which is just around the corner (on the downside perhaps, if you are like me, you cannot make it).
Thanks for the additional link. Yes, i wish I could see Steve's presentation at the conference, but I won't be there.
Matt,
I'm sure that there is more depth to the quote I grabbed. To work with Model-Glue you need to learn the XML dialect. I thought Mach-II and Fusebox used similar approaches.
Are you saying that writing that XML file to define controller logic is not programming? If so, I'm not certain if I agree.
Although even though I dislike them passionately, there are still plenty of good reasons to use XMl files:
Good reasons to use XML:
http://www.pbell.com/index.cfm/2006/10/4/The-Benef...
And some thoughts on why you might prefer scripting instead:
http://www.pbell.com/index.cfm/2006/10/14/Beyond-t...
As programmers we have to learn new things all the time (and should be!) so I don't see why having to deal with a little XML is such a huge deal. It's a powerful, flexible way to solve the problem of configuration files in frameworks.
In the "others," application logic is never declared in XML. In ColdSpring, dependencies are arranged. In Mach-II and Model-Glue, UI gestures are related to controller-tier functions. In Transfer and Reactor, relationships between model objects and database tables are declared.
For all of these tasks, CFML would be a very wordy way to go. It'd certainly be possible, but it would obfuscate the meaning of the text (imagine all the extra <cfset /> statements used to configure a MG app by hand!).
Secondly, XML allows the framework developers to write their own "jargon" that's task specific - which is probably easier to learn than a custom CFC-based API that'd be needed to build an all-CFC framework.
I hope you all don't think i'm against any of the current frameworks. I think they're great. At the same time I think healthy arguments about how we write applications is a good thing. So please bring a healthy dose of skepticism and find holes in my ideas.
http://www.webapper.net/index.cfm/2007/1/26/Steve-...