I would rather ask IF it will be supported at all in 2012...

From what we know by waiting for the iPhone4 I would say it takes about three month - at least. This time it should be pretty easy to enable this, since they know everything from the 3gd to iPhone4 switch, but I think that the team is mostly working on Android devices and iOS is something they are doing in their sparetime...

It is so sad that it seems like there is only a very small team working on this project at Adobe, though this could really be something special and good, but I switched to Xcode to ensure that projects don't rely on a totally wierd upgrade timetable (for example look at the problems with the languages and how long it takes to fix this for Adobe, or how long it took to use Game Center etc.). I know of a lot of developers who switched to Xcode and just work with Air before developing to make quick sketches, though even this might chance since the new Xcode features. I really like working with Flash, but it is getting harder and harder with each new iOS or device update since the Air updates are out of synch and much to slow for new (and often small) new features and the last updates were always incorporating new bugs. So it is tough to use then instandly.

josholm wrote:

 

It is so sad that it seems like there is only a very small team working on this project at Adobe, though this could really be something special and good, but I switched to Xcode to ensure that projects don't rely on a totally wierd upgrade timetable (for example look at the problems with the languages and how long it takes to fix this for Adobe, or how long it took to use Game Center etc.). I know of a lot of developers who switched to Xcode and just work with Air before developing to make quick sketches, though even this might chance since the new Xcode features. I really like working with Flash, but it is getting harder and harder with each new iOS or device update since the Air updates are out of synch and much to slow for new (and often small) new features and the last updates were always incorporating new bugs. So it is tough to use then instandly.

That's exactly how i see it.
I saw one of the promo videos for making ios apps months ago and thought; "Wow! That would be awesome, work with Flash wich i've done the past 12 years and make cool ios apps!".

About 2,5 months down the app-road enthousiasm has been replaced with discouragement...

Hi Colin,

I do agree with you in terms of the fact that it seems that the last three month have been a bit better when it's coming to updates of possible features. However, as I said am am sad about how the general concept is presented to us users. Well, one can say it is good that we are able to use the iOS export at all, but to be honest, we are customers and a lot of people are using Flash/Flex/Flashbuilder just because of the fact that they can do those exports and therefore it would be good if someone would take care of those people and business. To clearify, I am not saying that anyone of the people is not doing great work in providing the tools, to me it is just hard to see the general concept. I know that – for a while – the development was stopped, but that has been quite a while ago and Adobe is one of the largest software companies and I a wondering (not just in this case) why aren't they pushing those things much more. This could be also become a big business for them, IF the software works, IF updates are rolled out faster AND with a better control of whats beeing send to the users.

When I read that even Adobe deploys their apps with wrong language-lists I just think that something is simply wrong. I mean, could you be able to deliver your work like this? Nevertheless, let's see how long it take and how it will be deployed. Maybe the next update will be great.

Riccardo, you wouldn't need a preview player that has the original size in real pixels, if you install Xcode you can see that the iPhone 3 and iPhone4 simlator has the same size and since the pixels are just closer together but the physical device has the same size too – it just implies the look. Also you can deploy it to the device and see it by yourself if it works out.

I think AIR will work the same way as on iPhone 3GS / iPhone4 where you can see high resolutions ) Not a problem.

Adobe Air runs on iOS platform. If you can run it on iPad 1 with 5.0.1 you can ease run in on iPad3 )

Hight resolution must works because it's compilied for iOS, not for exact device ')

If you can't add file to build - you can ease add it using command line to ipa package using exact filename that use device. So u will get everything working. But Adobe for Flash CS5.5 don not provided updated Air2_5.dll but if they make it update - this will help using new features )

but ... currenlty I use command line that can compile anything

ok so i guess its 50/50 so far. stretching to big screen works fine but native resolution does not seam to be supported. Meaning i see pixilization on side of the image. if vector is used it should not be a problem (i guess)

for testing i used high res images from here: http://www.zastavki.com/eng/Motocycles/Harley_Davidson/wallpaper-12206 -18.htm just to give proper credit to who ever did the image

So for 1st test i used regualr ipad resolution 1024*768 i used HIGH res setings and placed 1280x800 photo obviously it got cut off, some side of the modules pixelazied but oveall model is ok no big digtortion

Next i inputed resolution to be 2048*1536, image now fully fits in, so i would expect it to be rendered nicely on large canvas yet i have same ordrder pixilization (ani alising needed i guess) I may be a bit picky but i consider interface by Apple to be perfect and our image that seams to be well rendering (externally) gets dissorted

Anyway here is snapshot

Now, lets play with bigger resolution  image... i used 1920x1200 resolution source image and HD canvas. Got image to be displayed almost full screen but sides of the images are not that perfect again.

Now i figure that print screens may not shto artifacts of renderings so i took some photos

As you can see around (5) has sitortion even though there is no on original image. This is photo of last test in HD mode full screen large image.

Here is another one

So my conclusion so far, is that 1024*768 and 2048*1536 have sa,e result in both case there is some sort of stratching and smoothing applied by player. Logically higher resolution images should look better on "new ipad" but i did not see that in my test.

Maybe i did something wrong but taht what I have so far! Any comments ideas? Lets get this thing to have perefect output... maybe you have other test assets?

and one more test that killled me

atathed is vector shapes drawn in flash i thought vector obkects should scale perfectly but they are not, i have perfectly scalable object on my desctop and terrible output on iPad 3 (although gradient came out pretty good)

Hope we find way to fix this

To avoid breaking apps that are not designed for the iPad's new retina display, apple only enable the full retina resolution on apps built with the iOS 5.1 SDK or later. So, to enable the higher resolution on your air app, you have to use this version of the SDK when compiling your app. You can only so this on a Mac with Air 3.1 or later. Use the -platformsdk compiler setting to point to the iOS 5.1 SDK and set the requestedDisplayResolution to high. Then you'll get the higher resolution.

I will overlay to 3.1 /3.2 SDK for windows and see results, if nothing good will do the same for mac.

To other posts, if you have your sample project then send me the file i will compile it or compile file and give me provisioning profile so we know you di it righ and dont relay on my curently 2.6 SDK system

and resolution was 2048*1536, and i use Flash 5.5

ok me back in here

I updated (overlayed AIR SDK to 3.1 v14 I hope? dont know how to confirm that but XML file changed) I seted HIGH settings for quolity and rebuild the test vector screen and still getting crappy results.

XML:

  <iPhone>

    <InfoAdditions>

            <![CDATA[<key>UIDeviceFamily</key><array><string>2</string></array>]] >

    </InfoAdditions>

    <requestedDisplayResolution>high</requestedDisplayResolution>

  </iPhone>

Canvas Size: 2048*1536

Can some one get something better?

phillipkerman - I only built the project I am currently working on. The difference when compiling against iOS 5.1 was distinct with vector graphics clearly rendered at a higher resolution than when compiling against iOS 5.0 or when running on an iPad2. I didn't have time to do more and the iPad is at work so can't investigate further today.

RichardLord; I'd like to hear your exact process as I will go try this week on a mac.  For whatever reason acrowne doesn't seem to have it working--so maybe there are more details.  Do you use the SWF directive like: [SWF(width="1024", height="768")]?

Also--and this is probably a different topic--but wouldn't you get the best performance if you took your vector graphics and make bitmaps (scaled properly for the target)?  Maybe that's just not worth the pain--but I'd think it'd improve performance.

Yes, I think we're stuck on the icon sizes.  Hopefully Adobe can come up with a patch soon.  The fact RichardLord can make it work makes me believe it's possible for adobe to update the magic stuff that makes it possible to deliver in the first place.

I confirmed my test this morning. Specifying the iOS 5.1. sdk in the platformsdk setting works. I wrote a blog post with details of the test - http://www.richardlord.net/blog/using-the-ipad-retina-display-with-ado be-air

acrowne - Don't know why yours doesn't work. All I can think is perhaps Flash Builder ignores the platform sdk if you don't have any native extensions that need it.

"Apparently, we're not yet in a situation in which we can say that AIR is "device-independent" since a new device is described  differently by two different versions of AIR."

Not exactly. The two different versions of Air describe the stageWidth and stageHeight differently for ALL devices. It seems to take Air a while to get the correct stageWidth and stageHeight. With Air 3.2 it's available after one frame, with Air 3.1 it takes longer (in the comments on my blog post, Richard Leggett says three frames is usually enough). And both versions give correct values for Capabilities.screenResolutionX/Y and for stage.fullScreenWidth/Height, which are the more reliable values.

The place where device independence does fail is that Capabilities.ScreenDPI is incorrect for the new iPad. I use this to adjust the size of user interface elements to be the same actual size on all displays. Because Air reports the wrong values for the new iPad, I have to treat this as a special case.