Quick answer is:

Listen for the applicationComplete event and add the menu item:

ViewSource.addMenuItem(this, “www.LinkToYourSource.org/srcview”)

The long answer is that I spent the better part of an afternoon looking for an easy way to have Flash Builder do what it used to do (generate and show my source code). I was seeing Flash Builder to crazy stuff like rip out the “viewSourceURL” tag from my WindowedApplication. I figure there’s some sort of setting in the project properties that is set to kill stuff like this when doing a production release but I couldn’t seem to find it. Is my hair falling out?

Oh, and yes, I’m talking about Adobe Air here. I see everything seem to be in order when doing a Flex browser application.

To generate the view source files I fired up an old version of Flex 3 and when I went to the export wizard it had that old familiar “Enable view source”. I pulled in a more modern compiler but Flex Builder didn’t seem to get the build right. But it did generate the viewable source code. So I took that code and posted it online. Then I switched back to Flex 4.6 and made the actionscript call to add that source menu:

protected function applicationCompleteHandler(event:FlexEvent):void
{
ViewSource.addMenuItem(this, “http://SAMPLE_WEBSITE.ORG/srcview/index.html”);
}

So while this solution works, I’m sure there’s some really simple way to get my old familiar wizard back.

What am I doing wrong here?

You can watch for the length to change like this:
ChangeWatcher.watch(mainNavigator,’length’, mainNavigator_lengthChangeHandler, false, true);
Take note that we’re using weak reference here.

Another option that I’m leaning towards is responding to the view navigator’s elementAdd and elementRemove events.
ViewNavigator id=”mainNavigator”
firstView=”view.homeScreen.HomeScreenView”
elementAdd=”mainNavigator_elementAddHandler(event)”
elementRemove=”mainNavigator_elementAddHandler(event)”

Some of these blog posts are just so I can find the answer to the same problem later. But I hope they help someone else also

Best of luck,
Matt

Maybe a user rotates the device and the view changes from landscape to portrait view and you have a popup that needs to be re-centered. So what to do . . .

Well, I’m glad you asked. Basically, you need to listen for the Stage to dispatch a StageOrientationEvent.ORIENTATION_CHANGE event. When the orientation does change, you’ll need to wait for the view to update (or whatever magic you’re doing), give Flex a second to redraw the view by waiting a frame then center the popup. (PopUpManager.centerPopUp)

Additionally you could set a flag and wait for the updateDisplaylist method to be called before centering your popup.

Ok if that wasn’t clear, maybe a little code would help:

protected function addedToStageHandler(event:Event):void
{

}

protected function showSettingsPopup():void
{

}

protected function stageOrientation_eventHandler(event:StageOrientationEvent):void
{

}

protected function centerPopup():void
{

}

So in this code we’re using a popup called ‘settingsPopup’. You’ll need to make your own popup and have a reference to it in order to center it.

Best of luck,
Matt

Whoops, for some reason the TextArea that I was using had text that was disappearing. It was really odd. I’d push a view and the textarea text would show for a second and then disappear.

Then oddly come back when clicking on stuff. What is this? Black magic? Is this the work of the devil?

Nope, this is the work of new Stage Text feature in Flex 4.6.

Stage Text is super helpful because it allows for the native application to display the text and do cool things like use the native OSs text auto-complete but it’s tricky.

Stage Text has many limitations. For example, It’s not going to work well in items that scroll.

Solution

If you don’t want to play around with Stage Text or you’re experiencing blinking / disappearing oddness don’t stress. You can just change the skinClass:

skinClass=”spark.skins.spark.TextAreaSkin”

Best of luck and hope this helps!

It took me a second to find out how to get rid of this Adobe Welcome screen popup up each time I started Flash Builder. Just so you know it’s under Preference -> Flash Builder -> ‘Show welcome screen on launch’

Here’s a screenshot:

Yeah, I’m mostly posting this so that I can personally find it the next time I forget.

Here is their wording:

We will no longer continue to develop Flash Player in the browser to work with new mobile device configurations (chipset, browser, OS version, etc.) following the upcoming release of Flash Player 11.1 for Android and BlackBerry PlayBook

link

This follows, what I would describe as, 2 years of the worst PR given to any software or platform that I can remember.

My question to Adobe is:
How would you think this little announcement would be received by the already bitter tech community?

Here’s a few headlines:
– Apple’s Steve Jobs vindicated as Adobe kills mobile Flash‎
– Adobe kills Flash on mobile devices
– Adobe kills Flash Player for mobile browsers
– Why Adobe Failed and Where Startups Can Swoop In

When Adobe makes strategic decisions like this, I’m guessing they do it for the following reasons:
1. Reassure their investors and
2. Increase share prices

It is my opinion that Adobe’s PR ninjas failed at both of these tasks today.

Flash Player 11

AIR 3

There are tons of new feature in each but I’d like to highlight one on each runtime.

Adobe Flash Player 11 has a new API called Stage 3D. Now Flash has had 3D for a while. Projects like Away 3D and Papervision 3D having been doing 3D within the Flash player for years. However these projects relied on computer’s CPU to do the 100% of the 3D rendering.

With Flash Player 11 projects like these can now take advantage the GPU’s 3D rendering capabilities. This allows for 3D performance on the flash platform with an order of magnitude greater performance and complexity.

OK, here’s a fun multitouch demo:

Adobe AIR 3 has added a fun new feature called ANE. ANE stands for Adobe Native Extensions and allows users to used the Adobe Air runtime in conjunction with natively executing code. This allows Adobe AIR to do fun things like integrate with phones that have NFC capabilities or view compass data (these aren’t available by default to Adobe AIR)

Here’s a round up of helpful links to follow up with up with:

List of features
Stage 3D devnet article
Developing native extensions for Adobe AIR
Extensions for AIR
Press Release About Flash 11 and AIR 3
You’ll also need the new AIR 3 SDK

I’m a Flex developer. I get paid to use the Flex SDK to build rich internet applications. I woke up feeling guilty about how much our community complains about the Flex framework.

Yes there are issues with Flex and we complain because we love it and want it to be perfect. And I don’t think we focus on that last part nearly as much as we should. Many of us love the Flex framework.

I’m posting a picture of my family below because the Flex team should know that their work has directly affected my ability to provide for them.

Flex work has paid for a lot of trips to the grocery store. Flex has paid for a lot of diapers. Adobe Flex has paid for a number of amazing vacations. Flex has enabled me to meet some of the most amazing developers and friends that I have in my life.

We’re finally looking for a home and we’ve been able to save up a sizable down payment, mostly, from working on Adobe Flex projects. When I say I owe the Adobe Flex team a big thanks you, I’m not being sarcastic or exaggerating.

My little family on our summer vacation:

Now I know that the Flex team gets paid, but I’ve noticed many of them going above and beyond their 9-5. I’ve seen team members hanging out online responding to FlexCoder mailing list in the middle of the night. I’ve seen team members showing up at user group meetings to ‘learn’ about some Flex 101 topic. Just generally being supportive of the Flex community.

I simply want to reminding the Flex team that their work makes a direct difference in many families like mine. Thanks and keep up the good work!

The title of my talk is named “Multitouch. Small, Medium and Large”.

In Seattle, I will be going over the basics of developing multitouch applications and as the title suggests, we are going to look at using that multitouch development skill set across a large variety of screen sizes. I plan to have multiple examples running on a variety of devices.

Lastly, we are going to look at a few valuable tools, frameworks and components that will speed up your multitouch application development.

The Seattle Flex user group is fantastic. I’ve spoken in Seattle before and this is a really fun group to hang out with. If you are in the area I highly recommend you become a regular SeaFlex user group attendee. Here is a link to their website: http://seaflex.groups.adobe.com/

If you are interested in multitouch development (from mobile to kiosk), please make sure to earmark some time to join us.

Thanks!

(wallpaper of presentation title image)
Multitouch. Small, Medium and Large (1080p or 1024×768)

Today my video has been posted. So take the hop, skip and a jump over to their site to check it out:
Multitouch – Small, Medium and Large on Zaa.tv

Personally I love to learn via video tutorials. And there’s tons of great presentations on this site. So grab some popcorn and be sure to explore all of the great content on Zaa.tv. You will not be disappointed.

Here’s a link to my slides from the presentation:
HTML slides
PDF slides

All of the code and more demonstration code can be found at GitHub:
Demo Code on GitHub

And a link to the wallpaper of presentation title image:
Multitouch. Small, Medium and Large (1080p or 1024×768)

If you have constructive feedback on the presentation feel free to drop me a comment below.

Thanks!