Flash Player 10 comes with a nifty new method for the flash.net.FileReference class called “save“. What’s dope is that you can send it a ByteArray, and it’ll write it verbatim. This means, saving images out of your Flash & Flex Applications is wicked fast now AND gets around that lamesauce security restriction that plagued a lot of older Flash Player 9 code. In the past, you had to either upload the image, ask the server to convert/save a ByteArray/Base64 encoded string for you somewhere, which you would then download via FileReference.download. That code would fail in Flash Player 10 because you cannot initiate a download unless it’s via a mouse click.
Category: Flex
-
Making a Cooler Cursor in Flex
Preface
Creating custom cursors in Flex is pretty straightforward.  You call the CursorManager’s setCursor method, passing in your cursor as the first parameter, and you’re good to go.  It can be an image, a SWF, or a custom class; as long as it’s a DisplayObject, it’ll work.  However, some cursors are more dynamic than just animating to indicate a state, or showing some text to let the user know what’s happening.  Some can show some minor status of what is going on.  I say the word “minor” here to indicate that you can still operate the app, and the cursor should still imply you can click around the app, or indicate the type of interaction you can do.
-
Agile Chronicles #8: Demo, Burnout, and Feature Juggling
The Agile Chronicles is a set of articles documenting my experiences using an Agile process (Scrum) in software development on my current Flex project.
- Part 1 – Stressful
- Part 2 – Code Refactoring
- Part 3 – Branch Workflow
- Part 4 – POC, Strategy, and Design Challenges
- Part 5 – Acceptance Criteria & Punting
- Part 6 – Tools, Extra Merge Day, and Postponed Transitions
- Part 7 – Bugs, Unit Testing, and Throughput
- Part 8 – Demo, Burnout, and Feature Juggling
- Part 9 – Scope Creep
- Part 10 – Conclusions
In this article, I discuss how you fit (or don’t fit) a demo of your software into a Scrum process, the how burnout can skew your burn down, and the variety of ways of features can be cut, re-assigned, or re-designed.
-
Agile Chronicles #7: Bugs, Unit Testing, and Throughput
The Agile Chronicles is a set of articles documenting my experiences using an Agile process (Scrum) in software development on my current Flex project.
- Part 1 – Stressful
- Part 2 – Code Refactoring
- Part 3 – Branch Workflow
- Part 4 – POC, Strategy, and Design Challenges
- Part 5 – Acceptance Criteria & Punting
- Part 6 – Tools, Extra Merge Day, and Postponed Transitions
- Part 7 – Bugs, Unit Testing, and Throughput
- Part 8 – Demo, Burnout, and Feature Juggling
- Part 9 – Scope Creep
- Part 10 – Conclusions
This entry is about the ugly truth of bugs, how you apparently reduce this problem via unit testing, and how we’ve attempted to improve throughput.