Personal & Professional Blog of T. Scot Clausing // Adobe Flex Consultant in Nashville, TN
“Adobe’s Cairngorm MVC framework is used by Flex develpers to deliver scalable and maintainable rich internet applications. Universal Mind has created extensions to that framework to address implementation issues that can impede developers.”
Read more at:
http://code.google.com/p/flexcairngorm/
I’m excited to see this! I haven’t had time to try out the new extensions, but I’m looking forward to it. Thanks to all the good people at UM.
Update: New updated example in “Text on a curved path in Flex - Resurrected” - please see instead of this entry.
There was some discussion in the 615Flex Google group earlier about how to warp text in a Flex application. (If you have any valuable input or resources please leave them in the comments). I thought it would be fun to mess around with the idea, so I put together this really weak example of a text warp component.
Read on to see a little example …
(Go to ‘Cairngorm Series‘ to view all titles)
This is the third post in a series on Cairngorm fundamentals. We will be binding data from the ModelLocator (created in the previous video) to a new View component. There are countless ways to achieve similar results, so do some research and come up with a method that meets your requirements. I establish some goals to strive for when creating views but the focus of this series is on Cairngorm. Feel free to post links to additional resources on the subject. Continue reading for the video and example with source …
Continue reading ‘Create a View and bind to application data’
(Go to ‘Cairngorm Series‘ to view all titles)
This is the second post in a series on Cairngorm fundamentals. We will be covering the concept of the ModelLocator, the Model in MVC. In short, the ModelLocator is a Singleton which implements a marker interface (no method definitions) from the Cairngorm framework called com.adobe.cairngorm.model.IModelLocator. The ModelLocator class defines properties that hold all application data. From now on we’ll just call this class the Model.
(Go to ‘Cairngorm Series‘ to view all titles)
This is the first post in a new series on Cairngorm fundamentals. I begin the series with three steps towards a Model View Controller implementation using familiar concepts and no framework. Future posts will build on these concepts using the Cairngorm framework until we have built a working application.
I’ve been searching for a way to write view code in my Flex & AIR projects that is completely reusable, scalable and simple yet powerful. I’ve read about and used the questionably named ‘code-behind‘ techniques that Ted and Adobe promote. I’ve tried the ‘script src‘ technique that Tink is passionate about. I’ve used ‘view helpers‘ and I’ve even tried the rarely discussed ‘code-in-front‘ technique that Marc has written about. However, I’ve recently been creating my views with a technique I call the ’simple’ method which is in the same school of thought as Marc’s idea. Here’s a table that describes the five methods mentioned above for creating views in Flex:
Continue to try out each technique in a Flex application with source and find out why I especially like the all MXML ’simple’ method …
Continue reading ‘Flex View Component Techniques in MXML & AS’
I have started a series of posts on Flex from a ‘ground up’ perspective. View the series by clicking the ‘Flex Series‘ tab above. The URL’s to these articles won’t change, but the titles, text and examples will evolve (so be careful linking and quoting). The goal of the series is to establish a resource of Flex best practices specifically related to application structure and coding practices ((specifically not dealing with server side technologies nor GUI design)).
If you have suggestions for topics or feel that something could use another perspective or elaboration, please leave comments. I really appreciate involvement from the Flex & AS community. Continue reading for a list of assumptions that this series will make …
This post is an extension of an earlier post entitled “Flex Part 02: Value Objects & Model Objects“.
Recap: Model Objects are similar to Value Objects in that they hold the same data, except that the Model Object is responsible for making sure that no ‘bad’ data gets into the VO. The Model Object enforces business rules like, “phone must be at least ten digits long” which a VO cannot do on its own. A Model Object may even include methods for easily manipulating properties.
In the earlier post I presented some example code for a Model Object. It turns out that what I provided is a pain to maintain over time. There’s just too much duplication and poor use of public properties. Continue reading for my attempt at a better, easier Model Object …
To view the connect presentation, click here (1 hour 20 min).
Ben Stucki delivered a great presentation last night to the Nashville (615) Flex user group. The topics were Degrafa, an open source declarative graphics framework for Flex and OpenFlux, a component model based on MVC (Model View Controller).
The presentation covers MXML syntax as well as complex CSS component skinning with Degrafa. Some of the examples are available on the Degrafa website at http://samples.degrafa.com.
Ben also shows off some of his work on OpenFlux - which looks very cool. If you are interested, skip to around 55:00 in the presentation. Also, check out Doug’s post titled “We’re not waiting for Flex 4” for even more cool info.
Sometimes it is necessary to display a formatted value such as currency or a percentage in a NumericStepper component, but that is not a default behavior. I need something extremely simple that can be written as:
My internet searches turned up this similar attempt, but it seemed overly complicated (just my opinion). Continue reading to view my attempt at a simple formatted numeric stepper with source. I've also included an example of a custom formatter as well as an item renderer / item editor in a DataGrid.
Hi. I'm Scot, an enterprise RIA architect specializing in Flex and AIR, ActionScript, and Java. I work as a consultant and designer in Nashville, TN and contribute to the Nashville Flex User Group, 615 Flex. To get in touch with me, please email tsclausing[at]gmail[dot]com.
