Flashbuilder 4.6 to 4.7 HTML Wrapper – playerProductInstall vs expressInstall

April 8, 2014

We had created a custom template file called ${application}${build_suffix}.template.php (instead of html template) which we used to autogenerate our output webpage.

When I upgraded from Flashbuilder 4.6 to Flashbuilder 4.7. I noticed that the xiSwfUrlStr substitution value changed from playerProductInstall to expressInstall.

Template line was:
var xiSwfUrlStr = “${expressInstallSwf}”;

Output from 4.6
php file contained line:
var xiSwfUrlStr = “playerProductInstall.swf”;
Flashbuilder also output to bin directory:

Output from 4.7
php file contained line:
var xiSwfUrlStr = “expressInstallSwf”;
Flashbuilder also output to bin directory:

Flashbuilder 4.6 has a page on html templates which discusses the substitution

Here is mention of the change on the apache flex developement site:

Here is swfobject google code location:

Otherwise I could not find a reference to this change on the adobe site.

Android Mobile Issue – Display local html/xml pages via StageWebView

May 14, 2012

When working on the pocketnotes to go mobile app, I ran into a problem viewing local xml files via the StageWebView component on an Android device. It turns out that special handling is involved which I found out after reading Air on Android: Displaying local web pages in StageWebView.

In essence, you have to copy your read only xml/html files from the installed .apk file on your device, which is located in the application directory, to the application storage directory.

The post has a brief explanation on how to accomplish this with a few lines of code. To make it consistent across android and ios devices, I found a blog discussing Local File Access/Editing for Android and ios.

Download NIM Tool Applications from the Website

April 26, 2012

Now that I have created the Pocket Notes on the Go Tool for:

  • Web
  • Desktop – Windows
  • Desktop – Mac
  • iPhone/iPad device (waiting developer approval via UNC)
  • android device
  • Online demo

I need to allow the user to either

  1. go to the marketplace to download the apps(iTunes or google play)
  2. or allow the user to download the software from the site.

Since Apple only allows you to install from the iTunes store, the website will be setup to only allow us to provide downloads for the desktop applications. The Apple and Android device apps will send the user to the respective marketplaces.

Continue reading

Using XML to display text in Flash Page and/or HTML

September 2, 2009

We have summary content which we use at the end of nutritional instruction. The nutritional instruction is initially rendered in a flash page at the end of a course(The course content is contained in a series of flash based pages). This information also needs to be made available for printing and for possible look up at a later time from an HTML web based page. We call this section our pocket notes and have placed this text info into an xml file.

We decided that with the use of xml we could centralize the information which needs to be displayed and massage it for display in two different contexts. The first view would be within a flash based page and the second within an html based page.

Pocket Notes Text Instructions for xml file:
The pocket notes text (which is to be displayed in both a flash page template and an html browser page) is provided a layout structure with the use of an xml file.

  • This xml file is dynamically loaded into the flash page for display.
  • The xml file is also displayed appropriately in a browser page with the use of an xsl stylesheet.

The xml file was structured using the following format:
Continue reading

Flex 3 Toggle Button Skinning Example

July 31, 2009

I am in the process of migrating our Flash based buttons to Flex. Our sound on/off button is perfect example to use the toggle button features of the Flex component.

The mxml code should look like the following with the toggle feature set to true:

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" 
	<mx:Style source="PlayerButtonSkins.css" />
		styleName="soundToggle" />

The styleName attribute can reference a css class which can be used to provide a visual skinning of the button when it is on and when it is off.
The PlayerButtonSkins.css file which is used by this mxml, has an example entry for the sound button using the stylename soundToggle:

Button.soundToggle {
	upSkin: Embed(source="/../assets/ButtonBar.swf", symbol="Sound_up");
	overSkin: Embed(source="/../assets/ButtonBar.swf", symbol="Sound_over");
	downSkin: Embed(source="/../assets/ButtonBar.swf", symbol="Sound_up");
	disabledSkin: Embed(source="/../assets/ButtonBar.swf", symbol="SoundOff_up");
	selectedUpSkin: Embed(source="/../assets/ButtonBar.swf", symbol="SoundOff_up");
	selectedOverSkin: Embed(source="/../assets/ButtonBar.swf", symbol="SoundOff_over");
	selectedDownSkin: Embed(source="/../assets/ButtonBar.swf", symbol="SoundOff_up");


The ButtonBar.swf file contains static skins/vector images of the sound button in various states of toggleness. Note: The styleName can be applied to button components whose styleName is set to “soundToggle”. This CSS styleName/component class context lets you uniquely skin many different buttons within the same mxml.

The images below illustrate the button states:
initial state of upSkin,overSkin and downSkin

The up state of the sound  on button

The up state of the sound on button

The over state of the sound button

The over state of the sound button

The selected states used when button has been toggled (selectedUpSkin, selectedOverSkin, selectedDownSkin)

The up state of the sound off button

The up state of the sound off button

The image used to represent the over state of the sound off button

The image used to represent the over state of the sound off button

Protected: Transfer site to Modwest

June 2, 2009

This content is password protected. To view it please enter your password below: