Jun
11

Ultrashock.com interviewed Ben Forta at CF_Europe 2003 asking questions about the past, present, and future of Macromedia, ColdFusion, and Flash. Click here to check out the interview.

Jun
10

Long Live CF Studio (HomeSite+)

Posted by Aaron West at 10:47 AM in ColdFusion

I'll admit it, I'm still using ColdFusion Studio. That is, until today. The ColdFusion community is riddled with disgruntled programmers who miss their editor of choice, CF Studio. While it is true that Macromedia has abandoned CF Studio as a product, there is actually a replacement that is not widely publicized. HomeSite+ IS the new ColdFusion Studio. If you're one of those developers that is still not happy with Dreamweaver MX (and you're wanting an editor that is both newer than ColdFusion Studio but still includes all the Studio functionality we've come to love) then HomeSite+ is probably for you.

WHERE DO YOU GET HOMESITE+?

If you have purchased Dreamweaver MX, Studio MX, or Studio MX Plus, then you have HomeSite+. While you can't install HomeSite+ from the menu that launches automatically when you insert the CD into your CD-ROM, you can browse the CD and install HomeSite+ from the HomeSite+ directory.

WHAT ELSE IS IMPORTANT TO KNOW?

I'm glad you asked! You'll want to head on over to Macromedia after installing HomeSite+. An update was released that fixes many issues.

Here's the update:

http://www.macromedia.com/cfusion/resourcecenter/rc_driver.cfm?pageName=hsp%5Fupdater

You'll also want to grab the VTM's so you can get tag support/completion for all the CFMX tags.

ColdFusion MX Tag Updater:

http://www.macromedia.com/software/coldfusionstudio/productinfo/resources/tag_updaters/

ColdFusion MX Reference Panel:

http://download.macromedia.com/pub/homesite/updates/cfml_ref.zip

If you are interested in customizing the HomeSite+ interface, Todd Rafferty has a nice blog entry that deals with this. Click here to view the entry.

So there you have it. ColdFusion Studio is not dead it's just been renamed! Happy coding!

Jun
3

Recently, I had the need to take the journey into building Web applications for multiple languages. Internationalization - i18n for short (there are 18 letters between the "i" and the "n" in "internationalization") - is the process of building Web applications for multiple languages and/or locales. The W3C defines internationalization as "proposing and coordinating any techniques, conventions, guidelines and activities within the W3C and together with other organizations that allow and make it easy to use W3C technology worldwide, with different languages, scripts, and cultures."

While this definition is good and comprehensive I needed to only focus on a specific level of internationalization. This article describes the application I was working with, the pitfalls that I ran into, and the solutions that I found to make my application work.

Continue Reading