This is a big deal, and it is likely going to hit the blogs all day. Adobe has officially announced that most of the Flex SDK is going open source using the Mozilla Public License.
What is being open sourced:
- MXML Compiler
- AS3 Compiler
- Flex Command Line Debugger
- View Source Utilities
- Web Tier Compiler Modules
- Automated Testing
This is awesome news. With Flex going open source Adobe is displaying how serious they are about capturing the RIA space and how strongly they believe in the community. The future looks bright for the Flash platform!
Other posts (Thanks Ryan for the links):
Finally getting around to posting my notes from my session on communicating with .NET web application from Flex that I gave at Adobe’s MAX in Las Vegas this year. I enjoyed giving this session as I truly believe Flex and .NET work well together and there are many methods for communication between both technologies, but currently there aren’t’ many resources covering it. In this session I talk mainly about 3 methods. Using HTTPServer/xml, WebServices, and AMF, as well as briefly touch upon Binary Sockets. I’m hoping in the future to have more detailed cover on each method.
You can download the slides and source code from here
Adobe has just posted a press release about the highly anticipated availability of Flex Builder for the Mac. Not much else to say other than it’s here as a public beta, works really well and I’m happy to see Mac developers gain access to the same tools available for Windows users.
Download it from Adobe Labs
Just finished cleaning up my session notes for my session at FlashForward Austin on Component Development In The Flex World. I had a lot of fun giving this session, as many know I have a big interest in component based development and component development, and Flex has a solid platform for both. There are two main concepts that are important to walk away with. The concept of developing Application Component to help promote Component Based Development and developing Custom Components. Both are explained in the slides and an example component is provided for each.
Download Presentation
Next week FlashForward will be held in Austin, TX and I’ll be there giving a session on Component Development in the Flex World on Tuesday, September 12, 2006 3:00-4:15 in Salons D/E.
The FlashForward crew have been working hard with every event to grow, making great changes, and listening to suggestions. One thing that I’m especially looking forward to (other than visiting Austin for the first time and hanging out with friends) is that the length of the sessions have been extended by 15 minutes. I know in the past I’ve found it difficult to finish on time when trying to dig into more details on a topic. I’m sure I wasn’t the only one that asked for this and am looking forward to seeing how it works out.
My session will be an introductory session on developing components in Flex. I will cover when you might want to build an MXML vs Pure ActionScript component, setting up the structure of a component, implementing styles, events, databinding, and packaging a component. There’s no way I could cover everything about components even with the extra 15 minutes but this session should help Flash and Flex Developers get a good understanding of component development in the Flex world.
One thing to note, this session won’t be focused purely on advanced component development like previous sessions that I have given. I will also touch upon Component Based Development principals, as Flex Framework and MXML are an ideal platform for such a development process which has many benefits to UI programming.
See you all in Austin, and if you will be there pass by and say hi!
Probably no secret right now, but just thought I’d officially announce it here finally that Joey Lott and I are working on a book covering Flex 2 for O’Reilly publishing titled “Programming Flex 2“. This is my first book and I have to say this writing stuff isn’t easy although I’m enjoying it. I hope this book helps spread the word on how truely excellent of a job Macromedia (Yeah I know, now Adobe) have done with this platform.
Ted posted FXT, a project he’s been working on and I couldn’t help but feel think when he first shared this.. Wait, Flash/Flex being used for things that usually I see HTML used for. I’m a pragmatists when it comes to Flash usage so I cringe when I see people wanting to go that far (like building a house out of Flash).
In our products we use Flash a good deal, but we also use traditional HTML application and dare I say some AJAX too. I love Flash and Flex, but don’t see it replacing HTML anytime soon. One of the benefits though of Flex over Flash has been its development process is much closer to how traditional development shops work. There are more things I would consider Flex for than I would have considered using Flash just purely based on the economics of rapid development and maintaining code base vs the richness of Flash. So with Flex 2, I am expecting more and more applications that developers only considered HTML as the proper technology to use to give Flex a try.
Back to Ted’s announcement of FXT. This looks like an interesting project towards seeing Flex moving even closed to replacing more places where HTML is better. It allows you to take the power of Flash/Flex and bring it to more traditional web applications. It also should be attractive to some developer who don’t even like the Flex data exchange model, and want it to behave even more like traditional HTML applications. The programming model has built in organization via our favorite pattern MVC. Definitely worth a look, especially the implementation details of how data is provided and how templating works.
Worth mentioning here are things that have progressed in the past over how the Flash Player integrates within the browser. We now have hacks to get bookmarking working, browser history, content scrolling, and some other things I’ve probably forgot.. but it’s still not truly part of the browser like HTML is. I’m sure if it were up to Adobe the player would be a first class citizen in all browsers out there (we would get benefits like being able to open links in a new tab and hitting ctrl+a to select the entire page’s content be it Flash or HTML), until then I bet the will keep try to find ways to improving the integration of Flash and the browser as much as possible with the limitations of the browser plug-in API’s. Which brings me to Apollo:
Apollo is the code name for a cross-operating system runtime being developed by Adobe that allows developers to leverage their existing web development skills (Flash, Flex, HTML, JavaScript, Ajax) to build and deploy Rich Internet Applications (RIAs) to the desktop.
I can’t help but think that Apollo was inspired by the inability to take Flash to the next level without being able to have complete control over the entire runtime. HTML isn’t going away, but all this can only lead to more usage of Flash everywhere..
My session titled “Intro to Flex 2.0″ at FITC 2006 went pretty well. Included is the presentation as well as all the code seen during the session. You will need MXMLC at least to build the different samples, or FlexBuilder.
Download Presentation
Christophe Coenraets posted an entry on his blog demonstrating four different techniques to write a simple temperature converter application.
The purpose of the entry was specifically to demonstrate four different ways to accomplish the same thing–showing how flexible Flex really is. The goal for this application was to separate the ActionScript out of the MXML files.
I’d like to follow up on this entry and demonstrate a fifth approach. This is something one of the Flex engineers proposed earlier and in my opinion is the cleanest method. Instead of using an <mx:Script> tag and including functions that get dropped into the current class, we can create a Controller class and link it through tags. This keeps tags in MXML, ActionScript in external files, promotes OOP programming, and simplifies reuse.
Continue reading ‘Separating ActionScript from MXML: Approach 5′
Our employer, B-Line Express, will have a booth at MAX to showcase our B-Line Charting Components. We’ll be demonstrating both the currently available 2.5 set and the in-development 3.0 version. This latter version is a complete re-architecture around the v2 framework and supports both Macromedia Flash MX 2004 and Macromedia Flex. If you’re at MAX, come by our booth to check out how our components can be easily integrated into a Macromedia Flex application with code such as follows.
<bl:LineChart
id="chart"
x="0"
y="0"
width="500"
height="400"
title="SampleLine Chart"
pointType="circle"
dataProvider="{dataStore.sales}"
marginRight="100"
xmlns:bl="com.blinex.charts">
<bl:xAxis field="Month"/>
<bl:yAxis minValue="0" maxValue="10" majorUnit="1"/>
<bl:series title="Tom" field="tomSales"/>
<bl:series title="Dick" field="dickSales"/>
<bl:series title="Harry" field="harrySales"/>
</bl:LineChart>
