The Official Flex Team Blog. Flash Builder Plug-in for SAP NetWeaver Gateway going away in April A little over a year ago the Flash Builder 4.5 plug-in for SAP NetWeaver Gateway was published as a beta on Adobe Labs (at As a research beta, the plug-in only works with older versions of Flash Builder (4.5 and 4.6).
The plug-in was never shipped as an official product, and isn’t going to be developed further – we’ve discussed open-sourcing the project with the code owners but this is unfortunately not going to be possible. If you still rely on this research project, please grab the bits now – as part of routine cleanup it will be disappearing off of Labs in April 2013. Apache Flex 4.9.0 Released! Alex’s Flex Closet. Matt Chotin. Flex PM Updates Over the last few months we’ve announced some exciting new members of the Flex PM team: Andrew focusing on Flash Builder and Deepa focusing on the Flex SDK.
With Doug focusing on Flash Catalyst and folks like Vera and Bill helping across our ecosystem, the Flex PM team is in better shape than ever. This means that I’ve been given an opportunity to take a new role that will allow to me focus on broader efforts across the Platform Business Unit. Daniel Koestler. Last week, Adobe announced the public betas of Flex “Hero” and Flash Builder “Burrito.”
You can use these tools to begin creating your own mobile applications that run Flash, AIR, and Flex content, and I recommend you check them out here and here. If you’re looking for the next step in getting started with a real-world Flex app, however, you may be interested in the following: I created an open-source application called SurveyApe, which should help you get started in the process of creating robust, real-world Flex mobile applications. It’s available on Adobe Labs: New URL: 05/16/2011 SurveyApe utilizes SQLite, the database framework that’s available in Adobe AIR. Ostensibly, SurveyApe conducts a survey consisting of a predetermined set of questions, allowing multiple users to use your mobile device and answer the questions that are provided in a sample database. Pete's Blog. Advanced CSS Selector With the Flex SDK Gumbo alpha release almost ready, I wanted to blog about the new advanced CSS selector capabilities.
We’ve added support for descendant selectors, class conditions for type selectors (previously class conditions were only registerd by themselves at the top level, i.e. “globally” instead of on a type by type basis), and id conditions for both type selectors as well as globally. These selectors were chosen as they were seen as the most requested by the community. A few known issues that will be fixed shortly after alpha include allowing combinations of conditions at the top level (e.g. a top level id and class selector together in a selector chain, “.specialButton#button12″); Targeting XMLSchema subtypes for anonymous ActionScript Objects For strongly typed objects, you can implement the mx.rpc.xml.IXMLSchemaInstance interface to provide a QName for the xsiType property to target the subclass to be used during encoding.
Continue reading… Download file. Home - Adobe Flex.org. Flexreport. There has been some recent discussion over how to get tics and labels on Spark Sliders.
Halo Sliders contained built in support for tics and labels, however, this feature does not yet exist for Spark Sliders. While built in support may be added in the future, for the time being the way to get tics and labels for a Spark Slider is to implement a custom skin. With the new Spark skinning architecture, this is relatively easy to do. For example, to get labels for an HSlider, you could simply copy, rename, and then modify the HSliderSkin.mxml file. Peter deHaan. New Adobe ColdFusion blog — I started another new blog (cfexamples.com) the other month, but have been holding off on posting the URL until I got some more content posted.
So far just a random collection of ColdFusion things that I could remember from my ColdFusion days and some new stuff from ColdFusion 8 and 9. As always, you can follow my sad little Twitter account (@pdehaan) to see the latest aggregated posts from my mini example blog empire (as well as other random tweets). Flexophile. Last June we announced that with the release of Flex 3, the Flex SDK would move to an open-source development model.
In the meantime we rolled out our Jira-based open bugbase at But we’ve also been busy on a lot of other open-source infrastructure. Fortunately, you don’t have to wait much longer to see it! Differences between Flex 3 and Flex 4. One of the major themes in the Flex 4 SDK is "Design in Mind".
This goal involves creating a smoother workflow between designers and developers. To help achieve this, the framework provides a clear separation of the visuals for a component and the rest of its behavior. In Flex 3, an individual component's code included logic around its behavior, layout, and visual changes. In Flex 4, the components are factored out into different classes, each handling specific pieces of behavior.
As specified in the Gumbo Architecture Document: "The main component class, the one whose class name matches the component's MXML tag name, encapsulates the core behavior of the component. Coupled with that component class is a skin class which manages everything related to the visual appearance of the component, including graphics, layout, representing data, changing appearance in different states, and transitioning from state to state.