Make sure you have all the properties as below:

<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://ns.adobe.com/air/application/2.0">
    <id>com.example.HelloWorld</id>
    <filename>MobileDesigner</filename>
    <name>Hello World</name>
    <version>v1</version>
    <initialWindow>
        <renderMode>gpu</renderMode>
        <content>HelloWorld.swf</content>
        <fullScreen>true</fullScreen>
        <aspectRatio>portrait</aspectRatio>
        <autoOrients>true</autoOrients>
        <visible>true</visible>
    </initialWindow>
    <supportedProfiles>mobileDevice</supportedProfiles>
    <icon>
<!--        <image29x29>icons/icon29.png</image29x29> -->
        <image57x57>Icon_57.png</image57x57>
<!--        <image512x512>icons/icon512.png</image512x512> -->
    </icon>
    <iPhone>
        <InfoAdditions>
            <![CDATA[
                <key>UIStatusBarStyle</key>
                <string>UIStatusBarStyleBlackOpaque</string>
                <key>UIRequiresPersistentWiFi</key>
                <string>NO</string>
            ]]>
        </InfoAdditions>
    </iPhone>
</application>

Another tip is to not draw any graphics or UI in your main Sprite’s constructor. Instead create another method and do any drawing there.

package
{
	import flash.display.Sprite;
	import flash.display.StageAlign;
	import flash.display.StageScaleMode;

	[SWF(width="320", height="480", frameRate="12", backgroundColor="#FFFFFF")]
	public class HelloWorld extends Sprite
	{
		public function HelloWorld()
		{
			super();

			this.stage.scaleMode = StageScaleMode.NO_SCALE;
			this.stage.align = StageAlign.TOP_LEFT;

			init();
		}

		private function init():void
		{
			var funk:Sprite = new Sprite();
			this.addChild( funk );
			funk.graphics.beginFill( 0xFF0000 );
			funk.graphics.drawRect( 0, 0, 360, 480 );
			funk.graphics.endFill();
		}
	}
}

Hope that helps!

The latest version of ELIPS Studio has just been released. It brings the ability for developers to create native mobile apps in ActionScript and Flex for mobile devices running Google’s Android platform.

With this new release, developers can now address all major smartphone platforms (iPhone, Android, Symbian, Windows Mobile) from a single code base using powerful web 2.0 languages and technologies from Adobe.

The next version of ELIPS Studio will bring the support of MacOSX as desktop development platform.

If I were Adobe I’d buy French OpenPlug toute suite and turn ELIPSE studio into AIR Mobile (or Mobile AIR).

Some of the more interesting sessions:

Extending Web to the Desktop with AIR
Monday, March 24, 2008
9:00 AM – 10:00 AM US/Pacific

Getting Started with Flash Lite 3 and CS3
Monday, March 24, 2008
11:00 AM – 12:00 PM US/Pacific

Building Rich Internet Applications with Flex 3
Monday, March 24, 2008
4:00 PM – 5:00 PM US/Pacific

Introduction to Adobe Blaze DS
Tuesday, March 25, 2008
9:00 AM – 10:00 AM US/Pacific

Integrating Salesforce.com and Flex
Tuesday, March 25, 2008
11:00 AM – 12:00 PM US/Pacific

Building AIR Applications with Flash CS3
Tuesday, March 25, 2008
1:00 PM – 2:00 PM US/Pacific

Adobe AIR Local Data Storage Options With Emphasis on Using Embedded SQL Databases
Wednesday, March 26, 2008
9:00 AM – 10:00 AM US/Pacific

Flex and Java – Tying the Knot!
Wednesday, March 26, 2008
4:00 PM – 5:00 PM US/Pacific

Flex Data Services
Thursday, March 27, 2008
9:00 AM – 10:00 AM US/Pacific

Blood from a Stone: Flash Game Optimization on Low-end mobile devices
Thursday, March 27, 2008
1:00 PM – 2:00 PM US/Pacific

Flex Visual Data & Charting
Thursday, March 27, 2008
4:00 PM – 5:00 PM US/Pacific

AIR Native Drag and Drop
Friday, March 28, 2008
1:00 PM – 2:00 PM US/Pacific

Flex Architecture
Friday, March 28, 2008
4:00 PM – 5:00 PM US/Pacific

When Microsoft released Silverlight the one feature that got a lot of people excited was that you could use the language you were most familiar with to build a RIA. Apparently Adobe has an internal project which allows any C or C++ code to run in the Flash Player or on AIR. This means that any language built on C/C++ will also run which means that Java, Python, and my beloved Ruby could also run. Schwing!

Ted is a Python guy so he talks about IronPython and JPython but of course Ruby has JRuby and IronRuby so I’m sure the behavior would be similar.

Like many organizations Adobe has lots of legacy C/C++ code ranging from PhotoShop filters, to PDF renderers, to readers and writers of every file format in existence, font libraries, to very complex vector renderers, and text layout code. Beyond Adobe there are many open source libraries that could be leveraged as components as well. The big thing for me is that these are not ports of these libraries, they run identical to the original source code down. For example the behavior of Python in Flash Player is identical to C-Python vs the ported behavior under the IronPython and Jython projects. The goal here is to bring lots of these legacy assets, code libraries, and languages into Flash Player and Adobe AIR perfectly so that any developer can leverage them cross-platform to build software. It would not shock me to see some of these components added into the Flash Player component cache so that they essentially are built into the player on first use.

InfoWorld has more.

• Ted (on Flex) has his AIRchat running on Python Twisted.
• Derek Wischusen has his messages moving atop Rails, Apache ActiveMQ, ActiveMessaging, and STOMP (post 1, post 2)
• Alex McCaw is the creator of Juggernaut which can use Flex or Ajax to push messages on Rails (using a Flash socket)
• Renaun Erickson has an example using Flex and Red 5 the open source Flash server.
• The new Yahoo! Messenger for the web runs on Flex.

Fire up those Flex chat apps and talk amongst yourselves, I’ll give you a topic:

Buzzword is the most wondrous invention since the printing press and will kill off both MS Word and Ajax in one fell swoop, discuss

Here are my notes from the LA stop of the tour.

[Getting There]
The large orange juice before the drive up from OC might have been a mistake. Finding a rest stop in East LA is a potentially a pant wetting experience with an empty bladder, so having an Austin Powers’ cryogenic pee on deck makes it doubly dangerous.

If you’ve never tried to get in the LA Center Studios it’s an experience akin to infiltrating the Green Zone in Baghdad.

[Morning Session]
Mike Chambers introduces Mike Downey for the keynote, MC Chambers deserves a raise, he will spend about 3hrs total on stage over a 12hr+ day. Downey gives an overview of AIR and then shows off some AIR apps including Pownce, Finetune, and Buzzword.

Chambers runs through an introduction to AIR and a HelloWorld app. He asks for a show of hands of Flex and JavaScript developers, it’s a 50/50 split.

After Alan Lewis of eBay shows off their San Dimas project I overhear an investor on the phone: “Buy more Abobe stock”.

Kevin Hoyt introduces AIR to the JavaScript folks. While not my area of focus building AIR apps with JavaScript is remarkably similar/easy as building them with Flex. Part of the session uses the Aptana IDE, there’s also an Aptana RadRails environment.

[Afternoon Session]
Kevin Hoyt also deserves a raise as he is back again talking about occasionally connected applications.

The salesforce.com dude then runs into a perfect storm for audience ADD, dry subject matter, non functioning slides, and the onset of the post-lunch food coma. The problems were unfortunate as the salesforce.com Flex API looks pretty rich (and could also make you rich).

Adobe should have scheduled Lee Brimelow right after lunch as his presentation was a) Hilarious and b) inspiring and informative. Lee showed off a series of AIR apps built sans Flex Builder with Grant Skinner’s AIR plugin for Flash CS3.

[Cocktail Hour]
I managed to find the Rails folk out on the patio and got a preview of a cool music based app (not sure the details are public so I’ll keep it on the DL, but it’s a different angle than last.fm, finetune et al).

[Night Session]
After being schooled by Kevin Hoyt at Wii Tennis I headed back for the night session (I have an excuse for my Wiifutility, Kevin towers over me and I’m 6′2″, I had visions of an errant swing lodging a Wiimote permanently in my noggin).

My notes are a bit sparse as the free as in beer beers were setting in. Tom Bray of Search Coders showed their Dashboard app which is one of the most fully realized AIR apps out in the wild. Tom’s partner Robert Cedana showed me the Search Coders Dashboard app earlier in the day and it can handle some pretty amazing amounts of a data. Check out the app if you’re looking for work as the ads are targeted at Flex developers.

At the end of the night there were still over 50 people in the audience, maybe I should buy some Adobe stock.

PS: If you can’t make it to a tour stop each event is being streamed live.

This is one of the things that Merb was written for. Rails doesn‘t allow multiple concurrent file uploads at once without blocking an entire rails backend for each file upload. Merb allows multiple file uploads at once.

I’ve built ‘multiple’ file uploaders for Rails sites but they always involved some slight of hand, the files appeared to be uploading all at once but they where actually queued up by Flex then handled one by one by the app (which also had the unhappy side effect of blocking any other requests to that process). I’ve been wanting to try out Adobe AIR’s file system drag and drop for a while so this is a two-fer example. You’ll need the beta version of Flex Builder 3 or the Flex 3 SDK beta if you don’t mind getting down with the command line.

In a hurry? Here’s one I made earlier (flex source in ‘dist/app/fx‘).

If you haven’t before install Merb

$ sudo gem install merb

Then create a new Merb app

$ merb -g merb_air_upload

and dive on in

$ cd merb_air_upload

We’ll need two folders not in a Merb skeleton, one for Flex, and one for our uploads

$ mkdir dist/app/fx
$ mkdir dist/public/uploads

Create a local database called ‘merb_air_upload’ and edit dist/conf/merb_init.rb so that the database definition matches your setup

# set your db info here
ActiveRecord::Base.establish_connection(
  :adapter => 'mysql',
  :username => 'root',
  :password => '',
  :database => 'merb_air_upload'
)

Our model will be called ‘UserFile’ as ‘Upload’ and ‘File’ are reserved words, create a migration

$ ./script/new_migration CreateUserFiles

and edit it (dist/schema/migrations/002_create_user_files.rb) to look like so

class CreateUserFiles < ActiveRecord::Migration
  def self.up
    create_table :user_files do |t|
      t.column :filename, :string, :null => false
    end
  end

  def self.down
    drop_table :user_files
  end
end

rake your db

$ rake db:migrate

Then create a UserFile model (dist/app/models/user_file.rb)

class UserFile < ActiveRecord::Base
end

and an upload controller (dist/controllers/upload.rb)

class Upload < Application

  def index
    # for testing check jer terminal
    puts params.inspect
    # new user file object
    @upload = UserFile.new
    @upload.filename = params[:Filename]
    # save
    if @upload.save
      # create directories
      dist_root = Merb::Server.config[:dist_root]
      FileUtils.mkdir dist_root + "/public/uploads/#{@upload.id}"
      # move
      destination = dist_root + "/public/uploads/#{@upload.id}/#{params[:Filename]}"
      FileUtils.mv params[:Filedata][:tempfile].path, destination
    else
      false
    end
    #render_no_layout
  end

end

That’s it for the Merb side of thing on to our AIR app, fire up Flex Builder and create a new AIR project

I like to keep my flex files in my Rails/Merb app directory

The AIR app is three files; the main MXML file (dist/app/fx/merb_air_upload.mxml), a code behind class (dist/app/fx/com/vixiom/merb_air_upload/App.as), and an upload progress component that gets repeated for each file (dist/app/fx/com/vixiom/merb_air_upload/UploadProgressComponent.mxml). Here’s the main MXML file:

<?xml version="1.0" encoding="utf-8"?>
<app:App
    xmlns:mx="http://www.adobe.com/2006/mxml"
    xmlns:app="com.vixiom.merb_air_upload.*"
    layout="vertical"
    width="300" height="375"
    backgroundGradientAlphas="[1.0, 1.0]"
    backgroundGradientColors="[#F4F4F4, #E0E0E0]"
    paddingBottom="10" paddingLeft="10" paddingRight="10" paddingTop="10"
    verticalScrollPolicy="off" horizontalScrollPolicy="off">

    <mx:VBox id="files_vb"
        width="100%" height="300"
        backgroundColor="#FFFFFF"
        horizontalScrollPolicy="off"
        paddingBottom="5" paddingLeft="5" paddingRight="5" paddingTop="5" borderColor="#ABABAB" borderStyle="inset">
    </mx:VBox>

    <mx:Button id="upload_btn" label="Upload Files"/>

</app:App>

It’s hooked up to it’s code behind ‘App.as’ class by the xmlns tag (xmlns:app=“com.vixiom.merb_air_upload.*“) App.as extends WindowedApplication which is the base of all AIR apps:

package com.vixiom.merb_air_upload
{
    import com.vixiom.merb_air_upload.UploadProgressComponent

    import mx.core.WindowedApplication;
    import mx.containers.VBox;
    import mx.controls.Button;

    import mx.events.FlexEvent;
    import flash.events.*;

    import flash.desktop.*;
    import flash.filesystem.File;
    import flash.net.*;

    public class App extends WindowedApplication
    {
        private var filesToUpload :Array
        private var UploadProgressComponents :Array;
        public var files_vb:VBox;
        public var upload_btn:Button;
        private var uploadURL:URLRequest;

        /*
         * Constructor
         */
        public function App() :void
        {
            addEventListener( FlexEvent.CREATION_COMPLETE, creationCompleteHandler );
        }

        /*
         * creationComplete
         *
         * called when the AIR has finishe loading, sets up drag/drop event listeners reference objects
         *
         */
        private function creationCompleteHandler( event:FlexEvent ) :void
        {
            addEventListener( NativeDragEvent.NATIVE_DRAG_ENTER,    onDragEnter );
            addEventListener( NativeDragEvent.NATIVE_DRAG_DROP,     onDragDrop );
            upload_btn.enabled = false;
            upload_btn.addEventListener( MouseEvent.CLICK, upload );

            uploadURL = new URLRequest();
            uploadURL.url = "http://localhost:4000/upload";
            uploadURL.method=URLRequestMethod.POST;

            filesToUpload = new Array();
            UploadProgressComponents = new Array();
        }

        /*
         * onDragEnter
         *
         * files have been dragged into the app
         */
        private function onDragEnter( event:NativeDragEvent ) :void
        {
           DragManager.acceptDragDrop(this);
        }

        /*
         * onDragDrop
         *
         * when files are dropped...
         */
        private function onDragDrop( event:NativeDragEvent ) :void
        {
            DragManager.dropAction = DragActions.COPY;
            var files:Array = event.transferable.dataForFormat( TransferableFormats.FILE_LIST_FORMAT ) as Array;
            for each (var f:File in files)
            {
               addFile( FileReference( f ) );
            }

            upload_btn.enabled = true;
        }

        /*
         * addFile
         *
         * ...add then to filesToUpload array, and the file upload listeners,
         * and create a progress component for each file
         */
        private function addFile( f:FileReference ) :void
        {
            filesToUpload.push( f );

            var upv:UploadProgressComponent = new UploadProgressComponent();
            UploadProgressComponents.push( upv );
            files_vb.addChild( upv );
            upv.file_lb.text = f.name;
            upv.pb.source = f;

            f.addEventListener( Event.COMPLETE, completeHandler );
            f.addEventListener( IOErrorEvent.IO_ERROR, ioErrorHandler );
        }

        /*
         * completeHandler
         *
         * a file upload is complete, remove it from filesToUpload
         * and remove the upload component
         */
        private function completeHandler( e:Event ) :void
        {
            var f:FileReference = FileReference(e.target);
            for( var i:uint; i < filesToUpload.length; i++ )
            {
                if( f.name == filesToUpload[i].name )
                {
                    files_vb.removeChild( UploadProgressComponents[i] );
                    filesToUpload.splice(i, 1);
                    UploadProgressComponents.splice(i, 1);
                }
            }
        }

        /*
         * trace any errors
         */
        private function ioErrorHandler( event:IOErrorEvent ) :void
        {
            trace("ioErrorHandler: " + event);
        }

        /*
         * upload!
         */
        private function upload( e:MouseEvent ) :void
        {
            for each (var f:File in filesToUpload)
            {
               f.upload( uploadURL );
            }
        }
    }
}

The last file is the upload progress component, it’s progress bar listens for events from each file (upv.pb.source = f; above in the addFile method)

<?xml version="1.0" encoding="utf-8"?>
<mx:VBox
    xmlns:mx="http://www.adobe.com/2006/mxml"
    paddingBottom="5" paddingLeft="5" paddingRight="5" paddingTop="5"
    borderColor="#BABABA" borderStyle="solid" borderThickness="2"
    width="100%"
    backgroundColor="#F7F7F7">

    <mx:Label id="file_lb" text="Label" fontWeight="bold" color="#000000"/>
    <mx:ProgressBar id="pb" labelPlacement="right" label="" width="100%"/>

</mx:VBox>

That’s it! test your AIR app by dragging some files from the file system, once you drop them the upload progress components show a visual representation of the files, click ‘upload files’ and the files are upload all at once (for real real not for play play this time).

drag!

drop!

upload!