Its true! Go get it now at http://labs.adobe.com/flexproductline/ and check out the changes as they relate to coldfusion over at Damon Cooper's Blog! What are you still doing reading this?!

I just found this because of Ted over at onFlex.org pointed out an Awesome keyboard shortcut for eclipse, alt+up and alt+down. Select a line and try it, its great. So I thought, if there is something this cool, there has to be more, so a quick google search brought me to this site: http://eclipse-tools.sourceforge.net/shortcuts.html with pdfs of some more great eclipse shortcuts. Very much worth checking out!

Dear All, I want to start out by sincerely apologizing for the lack of development or action lately. I am truly sorry for this, and it is something I hope to remedy soon. With that said, here is an update on the current state of affairs. As you know, the vision of COAL is really two fold. First, the idea was to create a library full or components, reusable, lightweight and extensable, to keep us as coldfusion developers from reinventing the wheel (or even rewriting the wheel they had already reinvented!) every time they needed to do something. It would also serve as a way to standardize some of the code that we all do, but all do differently. If someone was having trouble working with some of the components, other developers using COAL would instantly be on the same page and would be able to help. Documentation would be importaint and testing as well. It would also be a good way for others to learn some of the more advanced ideas behind object oriented programming and coldfusion. Secondly, there was the framework itself. It was my goal for this to become a great representation of the service factory pattern, and that it would be able to be used for component organization inside of applications, irregardless of the component libraries. It was my hope that it would be a strong, lightweight framework that would allow us to organize the COAL library efficiently (and maybe even move things around as they matured) and have that completely seperated from they way they were used in the applications themselves. It was this second part that I have spent the majority of time on when working with the framework so far. I put a lot of work into it, and it worked quite well. But it always felt like there was something more that could be, and should be done with it. So, lately, I have been hearing a lot about ColdSpring. I admit, I have not had a good chance to sit and get into it yet, but from the things I have been hearing, it has a lot in common with the framework I built for COAL. Basically, all COAL needs is a solid framework to offer up the components in the library, from wherever they may be. But some of the other features of ColdSpring sound enticing as well such as AOP (although I haven't fully gotten my head around that one yet...). So here is the question. Those of you that have worked with ColdSpring and understand it, does it sound like it could replace the COAL framework? That would free up development time to work on the actual components for COAL themselves and to work on documentation and commissioning (read bribing) other developers to author components for the framework as well. So those of you that are in the know, what do you think? Im sure there are Pros and Cons, but from what I understand, ColdSpring is designed to fix this problem.