Flex 4 Release Party Preso Recap

Last night I spoke at the AZFPUG and AZCFUG Flex 4 Release party. I am thoroughly happy I did! What fun it is talking about something you’re passionate about and Flex 4 is definitely something I thoroughly enjoy working in and talking about. With that said, most of what I talked about was pulled directly from Flex 4 in Action. I had my fair share of plugs for the book throughout the meeting. 😉 Hey…it is a great book, biased or not. Technically something always happens and, according to @nathanstrutz, I didn’t have enough dongles. 😉 I was missing my display connector(s) but thankfully @simpulton saved the day by bringing a couple and one worked. Big props to Ron Haberle for buying one. It wasn’t the right one but the effort must be awarded some kudos. One example failed to work. It was about rotating an image around the center and the rotate not affecting the layout. Well…I ran the same exact code today…worked! BOGUS! To demonstrate, I put the code online for all to see how it works (view source is included). For simplicity, here is the mxml for the swf: <?xml version="1.0" encoding="utf-8"?> <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" viewSourceURL="srcview/index.html"> <s:layout> <s:VerticalLayout paddingLeft="100" paddingTop="100" /> </s:layout> <fx:Declarations> <s:Rotate id="effect" target="{image}" angleBy="45" applyChangesPostLayout="true" autoCenterTransform="true" /> </fx:Declarations> <s:BitmapImage id="image" source="@Embed('images/flex.jpg')" /> <s:Button id="mybutton" label="Click Me!" click="effect.play()" /> </s:Application> Other than that, everything was pretty smooth and I filled up 2 hours showing off Flex 4 and Flash Builder 4 goodies. What’s crazy is I had even MORE to talk about. Flex 4 is a beefy upgrade and solves so many problems. It...

Preso: Introduction to Mate

Introduction to Mate (PowerPoint | Code | Recording) Description: Mate is an amazing Flex framework. This presentation showcases the basics of Mate. There are MUCH deeper levels to go but the introductory talk is what was requested by the Great Lakes Developers user group. That’s from my Preso’s page. Basically I was asked to discuss Mate and I gladly accepted. The preso had a blip at the beginning and you can hear me pause every now and then because…well…here is what I said on Twitter: I don’t care what anyone says…sitting in a quiet room and talking to your laptop is borderline insanity! I stand by that tweet. I found myself wondering if anyone could still hear me. lol. Either way…the preso shows the basics. I did miss a few things (like dropping the swc into the project) but hopefully the details of how the events are handled as well as the injectors. Those are the two big pieces of Mate that stand by themselves, IMO. If you’re new to Mate, give it a look and see if it helps. Hopefully it...
Flex 3 Remoting: Server Technology option not needed

Flex 3 Remoting: Server Technology option not needed

Yesterday I was pinged on IM by John Farrar about an issue he was having connecting Flex to ColdFusion on his new system. He’d done this many times before but hit a bump so we jumped on Adobe Connect and looked into it. One of the issues he was having, which went unresolved, was in him setting his server location info. It asks for things like server root, etc (see below). The main problem is in his setup, it seemed. He is using Apache as his web server and server docs out of a separate folder on his system, not the standard c:\ColdFusion8\wwwroot (for standalone). Typing in the CF location expects your “Output folder” to be within the CF\wwwroot folder. The problem with that is he using a completely separate folder (c:\foo\whatever\localhost). Maybe there was a way around it but after fooling with it for a second I fell back to old faithful. From my first time playing with Flex 2 remoting I attempted to use this screen but didn’t want to use my localhost CF (I stopped doing that a while back; have come back to local dev though). I learned how to set my endpoint, destination, and source all on my mx:RemoteObject directly so I took that approach in helping Senor Farrar. Here is some simple code to point out the ease of writing Remoting code in mxml. 1 2 3 <mx:RemoteObject id="service" destination="ColdFusion" endpoint="http://localhost/flex2gateway" source="com.katapultmedia.test.SomeCFC" fault="trace(event.message.body)"> <mx:method name="lookMa" result="trace(event.result)" /> </mx:RemoteObject> That’s it. This would work for PHP or any other backend by simply setting the endpoint, destination, and source. In the case I’m pointing to...