First, I wanted to point out that Simon Horwith has written an Open Letter to the ColdFusion Server Team in which he outlines 25 features he would like to see implemented in ColdFusion 8 (Scorpio). I have to say that I agree with most of what Simon's asking for. In fact, if you take a look at My Blackstone Wishlist, which I put together back in 2004, you'll see many of the same feature requests (some of these made it into Blackstone, and some into Merimack).
This leads me to the question, what are the most important features Adobe customers would like to see in the next version of ColdFusion. Each new release brings with it a trade-off of cost vs. benefit. What's the biggest bang we can get for the buck in the next version of ColdFusion?
If I could have Adobe's ear to request a programatic feature it would be a line count for CFDocument. And a "position of last line" too. I need to limit PDF files to just 1 page but forcing a max character limit on users is unrealistic because they can add extra line breaks and more paragraphics which takes up more space and moves nearer towards the end of the page. And when they add a graphic it's even worse. So some feedback from CF on the page layout would be useful. Even cfdocument.unusedVerticalSpace would be an ideal indicator. Is this request too obscure? :-)
- the ability to read one line at a time from a large text file, without having to read the whole thing into memory.
- proper inheritance
- the ability to use named arguments when calling super.foo() functions
and many, many more - these are just the ones that spring to mind in a few seconds before mornign coffee :)
http://devnulled.com/content/2006/07/wishlist-11-t...
- Broader implementation of cfscript.
- XSD support
- <cfzip>, <cfword>, <cfexcel> (writing and parsing), (etc)
- URL support for <cfquery> (rather than needing a DSN defined).
- Mappings @ application level.
- some way of dealing with application- and session- scoped variables on a cluster.
- equivalent of OPTION EXPLICIT
- being able to declare VARs without INITing them (and not necessarily @ the top of the method)
- clone CFC instances
- sort out whitespace issues PROPERLY
- expose API behind <cfchart>
- QoQ enhancements: INNER and OUTER joins. More functions. MAKE IT TYPELESS.
- <cfimport> ONCE for a request, rather than on every template using the lib.