You can stop waiting, its been released.

I'm a bit late in releasing this news, but our "Flex 3 Training from the source book" was released last week, and is now available from our publisher, as well as the major online bookstores such as Amazon, and Barnes and Noble. Speaking of Amazon, we are currently the #843 best selling of all their books, #15 in the Computers and Internet / Software category, and #8 in Computers and Internet / Programming. Thanks to all of you who have bought our book, and pushed the sales ranks so high.

Anyhow, I know folks have been asking me for months when this book would finally be released, and the answer is, last week.

Enjoy.

CFUnited Europe, AJAXWorld, and more conference stuff...

Next week I'm off to London to speak at CFUnited Europe, and the following week, I'll be speaking at AJAX World East.  In both places, I'll be speaking about the joy that is Flex 3 in all its forms.  The CFUnited talk is more focused on how Flex can improve the lives of CF Developers, while the AJAX World one is more focused on how Flex can help RIA developers increase their real world Retursn On Investment from RIA's.  On another note, CFUnited has just released the session schedule for their Washington DC Conference in June, and rumor is that the session schedule for WebManiacs should be available shortly.

My Speaking Engagements for the first half of 2008

1/18 - Flex Camp Chicago

1/24 - Flex Camp Omaha

2/24-2/27 - Flex 360 Atlanta

3/12-3/13 - CFUnited Europe

5/1-5/4 - CF.Objective()

5/19-5/23 - WebManiacs

6/25-6/28 - CFUnited

H.264 Support in FlashPlayer

I missed it yesterday, when it was announced, but Adobe has now announced support for H.264 (also know as MPEG4) in an upcoming version of the flash player.  H.264 is the same standard which is used by BluRay and HD-DVD -- the ability to have this type of video in our web applications is absolutly huge.  Remember, not that long ago, Adobe announced plans for the Adobe Media Player (AMP), as a desktop application which was built with AIR and Flash -- now, AMP will be able to use H.264 as well as FLV for its video content.

 

 

Changing Flex Style Sheets at runtime

Sorry its been so long since the last blog entry, between the two kids, writing 3 books, and many clients, its been hard to find time to write new entries here.  Today, I wanted to give a quick example of the Flex 2.0.1 feature of loading CSS style sheets at runtime.

In most Flex applications, I had been creating a seperate CSS style sheet, and compiling it into the application through the use of the <mx:Script source="..." />.  One of the pains of this, is that applying changes to the styles requires re-compiling the application, and as you probably now, the styles are one of the most frequently changed aspects of any application.

To help solve this problem, Adobe implemented the ability to load Style Sheets at run time in the Flex 2.0.1 release.  To do this, you first need to compile the CSS into a swf.  You can do this in FlexBuilder by right clicking on the css file and choosing "Compile CSS to SWF" option, or using the comand line compiler (mxmlc).  Once the css is compiled into a swf, it can be loaded with the StyleManager.loadStyleDeclarations(...) method.  Consider this simple example:

TestLoadStyles.mxml 

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="vertical">
 <mx:Style>
  .text1{
   color:#0000ff;
  }
  .text2{
   color:#ffff00;
  }
 </mx:Style>
 <mx:Script>
  <![CDATA[
   private function changeCSS():void{
    StyleManager.loadStyleDeclarations("myCSS.swf");
    
   }
   private function undoStyle():void{
    StyleManager.unloadStyleDeclarations("myCSS.swf");
   }
  ]]>
 </mx:Script>
 <mx:Button label="change css" click="changeCSS()"/>
 <mx:Button label="revert css" click="undoStyle()"/>
 <mx:Label text="hi there"/>
 <mx:Label text="hi there" styleName="text1"/>
 <mx:Label text="hi there" styleName="text2"/>
</mx:Application>
 

myCSS.css

Application{
 color:#ff0000;
 font-size:40;
}
.text1{
 color:#00ff00;

Compile the css into a swf, and make sure it is in the same directory as the TestLoadStyles.swf. As you run the application, you can see the changes as the style sheet is loaded or unloaded.  One thing to notice, is that even when the styles are loaded, and styles initially defined, which are not overridden in the loaded style sheet still remain, therefore, the styles of .text2 (yellow text), remain yellow, even after the new style sheet is loaded, since the .text2 style does not appear in the load style sheet, while the style .text1 which is defined as red text in the initial application, is changed to green, as the same style name is defined in both, so when the new style sheet is loaded, the .text1 label changes its color from green to red, and when its unloaded, it reverts to green.

This offers great opportunities not only for greater separation of styles from the application, but also for the concepts of writing an application once and rebranding the same deployed application.

FlexManiacs 2007 - Getting Started with Apollo

As promised, here are the starting files from my "FlexManiacs 2007 - Getting Started with Apollo" session.  Thanks for attending my session, I hope you enjoyed it and the FlexManiacs Conference.

Overall, i thought this conference was a great success.  Many attendees of all levels.  Great networking, Great debates, and an all around good time.

A Great big pile of public beta's from Adobe

Today, Adobe has released 3 new public beta's on Adobe Labs:   The Adobe Integrated Runtime (formerly known as Apollo) beta, the Flex 3 Beta, and the Flash Player Updater were all publicly released on Labs today.  I've been recovering from a failed hard drive all day (remind me to post a blog about the wonders of SpinRite 6.0 when i get a minute), but I'll post more about all 3 of these, as well as the ColdFusion 8 (Scorpio) beta released 2 weeks ago, when i get a few minutes.

Java Swing (re-)enters RIA space

It seems Sun is interested in re-gaining some of the market share it one had in the Rich Application space.  The annual JavaOne conference is underway, and there seems to be quite a bit of buzz surrounding the upcoming annoucement of the JavaFX project.  It seems that JavaFX is looking to compete directly with Microsoft's Silverlight and Adobe's Flex/Apollo initiatives, as developers will be able to target Desktop, Web and Mobile applications from this single platform.  Ultimately, it seems that this is largely going to be done by vastly simplifying Swing development, with the use of JavaFX as a declaritive programming model, on top of the existing Swing framework.

Ultimately, its good for everyone, developers and consumers alike to have more competition in the Rich Applicaiton space.  This will surely lead to greater innovations for applications, and more choices for developers.

You can find more on this at infoworld and infoq.

CFUnited Scheduler released

While the blog was down last week, the CFUnited Scheduler was launched.  This is a cool little AJAX app, which lets you figure out which sessions you want to attend.  You can browse the sessions by time, by presenter, or by track.  If you are going to CFUnited this year ( a must for all ColdFusion Developers ), this is an invaluable tool! 

By the way, I'll be presenting my topic "Flex 2 for ColdFusion Developers" Thursday and Saturday, both days at 8:30 am.

 See you there. 

 

Open Source Flex 3 SDK

At midnight, Thursday April 26th at Midnight, Adobe officially announced that the Flex 3 SDK, will be released as an open source project under the Mozilla Public License.  The actual timeline for the release looks like this:

Summer 2007 - Daily builds of the Flex 3 SDK will be provided.  Online access to the bug base will be publicly available.

Fall 2007 - Flex 3 launches.

December 2007 - After the release of Flex 3,  adobe will be posting all software assets into a public Subversion repository for public access. 

More information on this can be found in the FAQ, the press release, and the discussion group

Many have asked the questions: "Why would Adobe do this?" and "how is Adobe is going to keep making money from Flex?"  While I dont have any inside information about either of these, i do have come conclusions I've drawn on these two...

Why would Adobe do this

The easy, marketing friendly answer to this question is "to grow the platform."  Of course, Adobe wants more and more people using the Flex Platform, as it enables them to sell more copies of Flex Builder, Flex Charting, Flex Data Services, etc.  Of course, I suspect this may be a bit of a defensive move as well, as it comes on the heels of Microsoft annoucing SilverLight.    As Ted Patric notes, Adobe is taking the gloves off in its battle against SilverLight.  I think its safe to assume that by open sourcing flex, more developers will adopt it, and it will set a much higher bar for MS.

How is Adobe is going to keep making money from an Open Source Flex 3?

The reality as far as product sales goes, is this is no different than flex 2.  In flex 2, there was already a free SDK, which included everything a developer would need  to build flex  apps.  This open source project will provide the same free SDK, just under a different license.  As I mentioned before, if Open Sourcing the project attracts new developers, then, additional sales of the commercial flex products (Builder, Charting , Data Services, etc) will likely follow.

 

 

More Entries

BlogCFC was created by Raymond Camden. This blog is running version 5.9.001.