after an entire year spent meeting with and speaking to thousands of coldfusion developers, the cf team at macromedia are unleashing this month the feature-rich new release, cfmx 7.
its been three years since we released macromedia coldfusion mx, the most dramatic and ambitious coldfusion update ever. coldfusion mx marked an important milestone in the coldfusion story. it was a chance for the team to take a big step back and rebuild coldfusion from the ground up, taking into account everything we had learned about web applications and how they are built.
coldfusion mx was primarily an architectural release. it featured things like the following: a brand-new, java-based engine a true compiler deployment on top of industry standard j2ee servers better support for xml, soap, and other standards access to the world of java of course, coldfusion mx (and coldfusion mx 6.1) also boasted important new features, language enhancements, improved performance, as well as greater scalability and reliability. but at its core, coldfusion mx was all about architecture, an incredible investment in the inner workings of coldfusion so as to facilitate a world of new functionality. coldfusion mx has been an incredibly successful product, and a large portion of the coldfusion user base is already taking advantage of all it has to offer. and so with coldfusions new engine proving its mettle and developers busily exploring the opportunities it presents, the coldfusion team was able to spend time building new features and functionality that were not possible in the past.
for over a year we met with and spoke to thousands of coldfusion developers. we presented ideas and previews to hundreds of user groups worldwide, brainstormed with countless partners and customers, waded through mountains of wish-list feedback, and chatted with numerous users (both current and potential). when the dust settled, a series of goals emerged:
make new users far more successful. coldfusion has always appealed to new developers. there is no other language or product as well suited to their needs as coldfusion. new users (primarily those with a background in building web pages and static sites) are an important part of the coldfusion user base, and coldfusion must remain dedicated to making successful development easier for these users. this involves the creation of dreamweaver extensions and configuration screens, providing better out-of-the-box education, delivering more usable value, and more.
provide existing users with feature and functionality that they can use immediately. developers are never shy about what they want. we need to deliver the features and functionality they ask for.
help developers (our users) make their users happier. consumers of coldfusion applications have common requests - things theyd like to see in the applications created for them. many of these requests revolve around how the application captures and presents data. you said that coldfusion must provide powerful new capabilities for forms, reporting, and p... 下一页