The Largest Repository of ColdFusion Knowledge in The World for More Than 12 Years

ColdFusion on Ulitzer

Subscribe to ColdFusion on Ulitzer: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get ColdFusion on Ulitzer: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

CFDJ Authors: AppDynamics Blog, Michael Kopp, Tad Anderson, Bob Gourley, Jayaram Krishnaswamy

Related Topics: RIA Developer's Journal, ColdFusion on Ulitzer

RIA & Ajax: Article

John Farrar on COOP

COOP seems to rely on a CFC in the same folder as the calling file and with the same name extension

Steve Bryant's Blog

Yesterday John Farrar presented to the Online ColdFusion Meetup Group on his forms custom tag set, COOP. Actually, he describes it as a framework to separate page markup from processing logic.

Most of what I saw solves a problem in the same space as a custom tag set that I have been using for a few years (and hoping to put into beta soon). So, I am likely somewhat biased about what I saw.

That being said, I was really impressed with what I saw. It was interesting to see where John and I took similar approaches and where our solutions differed.

COOP seems to rely on a CFC in the same folder as the calling file and with the same name (except the .cfc) extension. John called this a "coprocessor". It looked a lot like a page controller to me. I have mixed feelings about this. On one hand, I was unsure of how I felt about introducing a requirement for an external file for each page. On the other hand, I generally like the use of a page controller.

He has several different kinds of form fields available. One thing that I noticed is that he has a "RadioButtonList" and "CheckboxList" where I named mine "radio" and "checkbox" for similar functionality. His name here is a much better description of the functionality and I wish I had thought of it.

His approach did seam to write table tags instead of providing an option for a more semantic style as well. He also used a separate tag for a label than for a form field. In one way, I didn't like this difference in approach as it made the code longer and required tables. The advantage of this option, however, is that it makes it easy to have multiple fields on one row with one label - something difficult with my approach.

This made for some nice-looking forms that seemed very "tight" in their presentation (which I liked).

He also allows pass-through attributes in his tag. This means that any attribute not directly used by the tag, will be written as an attribute in the HTML element. For example, you could add a "style" attribute to any tag. This is something we have in common, though I think I may have a list of pass-through attributes, which isn't as flexible an approach as John seems to have in COOP.

COOP allows you to specify a validation method from the coprocessor as well as using the coprocessor for other settings and data. This does provide a bit of an external dependency, but makes for a very nice separation of display and logic. John explained that his goal was that a non-programmer could handle the display code for the form.

The form is self-posting by default, but you can specify an action attribute if you prefer. This does circumvent the built-in validation, but John said that given the separation between the logic and display it should be easy to allow for validation even if the form isn't self-posting.

He is working on adding AJAX support and has complete documentation almost complete.

Overall, this looks like a very good offering. Indeed, Sean Corfield said "COOP looks very nice and cleanly architected".

If you are looking for a good form custom tag set, this is definitely worth a look. In the meantime, check out his recording.

More Stories By Steve Bryant

Steve Bryant is the founder and CEO of Bryant Web Consulting LLC ( and teaches ColdFusion at Breakaway Interactive ( He got his BA in philosophy at Oklahoma State University. Steve, one of the top ColdFusion developers in the country, still has no idea how that led to a career in Web development. Steve blogs at as one of CFDJ's published bloggers.

Comments (1)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.