How to Test AIR 1.5

<DIV><FONT face=Arial size=2>I am sure you are right about an AIR application <br />being able to use Loader and SWFLoader.  I hope I have more or less figured <br />out the right way to do that.  But, I guess my point is that none of the <br />documentation I have been able to find anywhere would answer the question about <br />what to do with the framework and/or rpc files.  What, as far as you <br />understand it, is the correct way to manage the use of the A</FONT><FONT <br />face=Arial size=2>dobe swz files in an AIR application?</FONT></DIV><br /><BLOCKQUOTE <br />style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"><br /> <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV><br /> <DIV <br /> style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> <br /> <A title=member@adobeforums.com href="mailto:member@adobeforums.com">Josh <br /> McDonald</A> </DIV><br /> <DIV style="FONT: 10pt arial"><B>To:</B> <A title=flexsdk-dev@adobeforums.com <br /> href="mailto:flexsdk-dev@adobeforums.com">flexsdk-dev@adobeforums.com</A> <br /> </DIV><br /> <DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, November 03, 2008 11:01 <br /> PM</DIV><br /> <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: How to Test AIR 1.5</DIV><br /> <DIV><BR></DIV>A new message was posted by Josh McDonald in <br /> <BR><BR><B>Developers</B> --<BR>  How to Test AIR 1.5<BR><BR>I'm <br /> sure there's nothing stopping you from loading SWFs and SWZs and SWCs and <br /> loading them in AIR? Just treat them as normal files, and use whatever you <br /> please to push out updates etc?<BR><BR>-Josh<BR><BR>On Tue, Nov 4, 2008 at <br /> 4:53 PM, Terry Corbet <SPAN dir=ltr>&lt;<A <br /> href="mailto:member@adobeforums.com">member@adobeforums.com</A>&gt;</SPAN> <br /> wrote:<BR><br /> <BLOCKQUOTE class=gmail_quote <br /> style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">A <br /> new message was posted by Terry Corbet in<BR><BR>Developers --<BR> How <br /> to Test AIR 1.5<BR><BR>01.  Thanks, I will continue testing with ADL <br /> and hopefully be able to move up to a web-base, remote installation/update <br /> scenario in a couple of weeks.<BR><BR>02.  I'm sorry you feel that my <br /> failure to accept what may be 'intuitively obvious to you' -- that I can <br /> design and test a 3D front end to FMS that works the same in a native window <br /> as in a browser window -- indicates any lack of faith in what will be <br /> delivered.  So far, I have found subtle, important differences, and I <br /> am sure there will be others that will just have to be patiently tested <br /> before I get it right.<BR><BR>03.  So, I'm glad you asked about swz in <br /> an AIR environment because that is a whole topic for which I have not been <br /> able to find any discussion on any of the many fine forums you have.  I <br /> understand product marketing and product development, but I can't say that I <br /> ever managed those activities in the environment you have in which several <br /> large projects co-exist with lingering dependencies and even 'cultures' as <br /> diverse as you have with the various acquisitions that come together in the <br /> suite of products you have today.<BR><BR>So, I will simply state that I <br /> think no one seems to have recognized that your paradigm for 'desktop' <br /> versus 'web-based' software -- the essential distinction which seems to <br /> describe Adobe's description of an AIR versus a Flex application -- does not <br /> always hold.  I understand the general dichotomy, but it does not hold <br /> for my user base.<BR><BR>You have lots of design papers and lots of software <br /> devoted to 'reducing the burden' of ever-growing executables in the Flex <br /> framework by caching of your or our rsls.  That's a good idea. <br />  Why do you think it is not just as good an idea for an AIR <br /> application?  Probably because you think that an AIR application will <br /> either be shipped on a CD, or sent over the Internet, but relatively <br /> infrequently, so who cares if you have to ship out 10MBs or 2MBs? My user <br /> cares.<BR><BR>My user will get frequent updates to an ever-growing body of <br /> software called an application, and he will get them over those same slow <br /> bandwidth network links that the Flex user sees.  What's "good for the <br /> goose is good for the gander".  There is simply no reason not to <br /> architect the library of code that we use to cobble together the application <br /> and use the same intelligent caching mechanism in both environments.  I <br /> looked for a month for a white paper or discussion of how to 'modularize' an <br /> AIR app but all that you wanted to publish were white papers on how to <br /> 'modularize' a Flex app.<BR><BR>I'm sure that you guys have a bunch of <br /> object diagrams and product architecture blueprints that you have memorized <br /> -- but that is not what we see 'outside the black box'.  What we see is <br /> a confusing distinction between the AIR efforts and the Flex efforts <br /> although the code base and efforts are substantially the same.  And if <br /> that is true from an internals point of view, put on your end-user hat and <br /> look at how we view a AIR/Flex app -- it is all one.<BR><BR>So, I develop <br /> the worlds greatest Juke Box and get it all going in Flex, then I move that <br /> into one Tab on one Screen in the AIR 'shell'.  Then some guys go off <br /> and mostly use AIR-unique code to add a Tab that allows Drag and Drop <br /> creation of Slide Shows accompanied by voice overs, and another set of my <br /> guys go off to add the 'Sudoku' module in just plain old Flex.  At some <br /> point in time in some ant task, we've got 10MB of code and X MBs of that is <br /> in one of our present [or future] swz files.  Where is the distinction <br /> that says I should just ask my users to download the whole shooting match, <br /> when what he really wants to do is just download whatever updated or new <br /> application modules [including any upgrades to your frameworks] when <br /> required.<BR><BR>So, it took some time, but today, my application is <br /> compiled with dynamic linking to the framework.swz, and when the user <br /> launches his AIR application on the desktop, the Flash Player, embedded in <br /> the AIR environment, is smart enough to find that it already has the <br /> necessary framework code and does not need to go back to the network to get <br /> it refreshed.  Actually, since I could never figure out how to use <br /> Module and ModuleManager, the method for solving the framework caching <br /> problem ended up just being an extension of what I developed for version <br /> management 'with continuous update' of my own swf files.  So, when the <br /> AIR shell starts up, it needs to test to see whether there is any updating <br /> to be done, or whether it already has locally available the 'latest and <br /> greatest' and that works the same for MyCute3DWizBang.swf or <br /> framework_3.1.0.2710.swz or framework_4.0.0.3988.swf.<BR><BR>If you take the <br /> point of view that a 'desktop application' doesn't need to do anything <br /> special to solve the problem of 'large file downloads', you end up thinking <br /> that there is no reason for an AIR application to take advantage of the <br /> frameworked cache when, in fact, almost all of that code is needed whether <br /> the execution thread starts in a 'WindowApplication' or just a plain old <br /> 'Application'.  At least thats the cockamaymee point of view that I <br /> came to in the absence of any 'best practice' discussion of these key topics <br /> --  so far, it seems to be working pretty well, but as you can guess, <br /> testing across a network to a remote host that may or may not have the right <br /> version of AIR, or the right version of framework, or the right version of <br /> MyCute3DWizBang  is really more important than just testing against <br /> ADL. <BR><BR><BR>----- Original Message ----- From: "Matt Chotin" &lt;<A <br /> href="mailto:member@adobeforums.com" <br /> target=_blank>member@adobeforums.com</A>&gt;<BR>To: &lt;<A <br /> href="mailto:flexsdk-dev@adobeforums.com" <br /> target=_blank>flexsdk-dev@adobeforums.com</A>&gt;<BR>Sent: Monday, November <br /> 03, 2008 8:39 PM<BR>Subject: Re: How to Test AIR 1.5<BR><BR><BR><br /> <BLOCKQUOTE class=gmail_quote <br /> style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">A <br /> new message was posted by Matt Chotin in<BR><BR>Developers --<BR> How <br /> to Test AIR 1.5<BR><BR>The badge install doesn't work with debug, you can <br /> only use adl.exe right now.  But this should show how the whole <br /> system would work and really allow you to evaluate.  You know how the <br /> AIR install works with Air 1.1 (if not, use Flex 3.1 to target 1.1), I <br /> don't think seeing it with AIR 1.5 is critical to evaluate the features of <br /> the runtime at this point.<BR><BR>Air and the Flash Player are runtimes, <br /> and we've made it clear that AIR 1.5 would include FP10 features.  So <br /> when we say Flex will enable FP10, it should be obvious that when AIR 1.5 <br /> comes out Flex will support it in the same way.<BR><BR>I don't really <br /> understand what you're doing with the SWZ and AIR, there's no real need to <br /> use a cached framework when the whole app is going to be <br /> installed.<BR><BR>In any case, Air 1.5 should be out in 2 weeks hopefully <br /> so you'll be set then.<BR><BR>Matt<BR><BR>On 11/3/08 8:07 PM, "Terry <br /> Corbet" &lt;<A href="mailto:member@adobeforums.com" <br /> target=_blank>member@adobeforums.com</A>&gt; wrote:<BR><BR>A new message <br /> was posted by Terry Corbet in<BR><BR>Developers --<BR> How to Test <br /> AIR 1.5<BR><BR>Thanks for the quick turnaround.  Pardon my ignorance, <br /> but exactly what .exe<BR>file will install Air 1.5 on a system?  I <br /> don't find it anywhere.  I guess I<BR>can try to tear the ADL source <br /> apart to see how it mimics that behavior, but<BR>that is, at best, just a <br /> local test.  I think testing the whole Badge<BR>install sequence is <br /> essential, and would like to give it a try.  The longer<BR>we put <br /> this off, the longer we all just sit here trying to decide whether <br /> to<BR>stay with Papervision, Away, Sandy, or to use the graphics support <br /> in the<BR>Player.<BR><BR>I am busy making the dynamic link to the <br /> framework.swz work for Flex modules<BR>running under an AIR shell, and I <br /> doubt that I am alone.  There must be many<BR>of us who really see no <br /> distinction between AIR and Flex -- they just<BR>provide us two different <br /> ways to slice a problem, that's why it is so<BR>disconcerting to try to <br /> follow the threads on rapid Flex advancement with FP<BR>10, but almost <br /> nothing pertaining the doing the very same things with the<BR>AIR <br /> toolkit.<BR><BR>I hope you can tell me where to get the standalone AIR 1.5 <br /> installer that<BR>will me keep making progress with the debugging output <br /> reasonably well<BR>handled by Allesandros' FireFox tracer.  Many <br /> thanks.<BR><BR><BR>----- Original Message -----<BR>From: "Matt Chotin" <br /> &lt;<A href="mailto:member@adobeforums.com" <br /> target=_blank>member@adobeforums.com</A>&gt;<BR>To: &lt;<A <br /> href="mailto:flexsdk-dev@adobeforums.com" <br /> target=_blank>flexsdk-dev@adobeforums.com</A>&gt;<BR>Sent: Monday, <br /> November 03, 2008 7:55 PM<BR>Subject: Re: How to Test AIR 1.5<BR><BR><BR><br /> <BLOCKQUOTE class=gmail_quote <br /> style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">A <br /> new message was posted by Matt Chotin in<BR><BR>Developers <br /> --<BR> How to Test AIR 1.5<BR><BR>Hi,<BR><BR>We're not doing a <br /> public beta of the release runtime for AIR 1.5.  You can<BR>use the <br /> debug runtimes that are part of the Flex nightly builds though<BR>(check <br /> the Flex 3 nightlies) to validate that AIR 1.5 will be right for<BR>you <br /> though.<BR><BR>Matt<BR><BR>On 11/3/08 7:38 PM, "Terry Corbet" &lt;<A <br /> href="mailto:member@adobeforums.com" <br /> target=_blank>member@adobeforums.com</A>&gt; wrote:<BR><BR>A new <br /> discussion was started by Terry Corbet in<BR><BR>Developers <br /> --<BR> How to Test AIR 1.5<BR><BR>Sorry if this seems slightly off <br /> center, but I blame Adobe, not myself.<BR>Trying to determine the true <br /> status and positioning of AIR amongst the<BR>various Flex forums and <br /> projects for an outsider is practically<BR>impossible.  So, I will <br /> be brief.  In September Mr. Chambers sent opened<BR>the flow by <br /> telling us that we could find FP10 integrated with Flex SDK <br /> in<BR>something you call 1.5 or Cosmo, or both.  He was properly <br /> circumspect, so<BR>I didn't rush into it -- there was not even an ADL <br /> binary when I checked.<BR>Now it is November, the Trunk is at 4005, and <br /> ostensibly, everything we<BR>need to start trying to take advantage of <br /> FP support of 3D operations is<BR>out there.  But where? <br />  Where do we get a version of AIR 1.5 that can be<BR>installed on a <br /> target desktop, so that we can try to run the ADT <br /> test<BR>cycle?<BR><BR>Call it Gumbo, call it Flex4, call it whatever, <br /> but can someone tell us<BR>how to start testing it for AIR application <br /> deployment?<BR><BR>Thank <br /> you.<BR><BR>________________________________<BR>View/reply at How to <br /> Test AIR 1.5<BR>&lt;<A <br /> href="http://www.adobeforums.com/webx?13@@.59b6ed86" <br /> target=_blank>http://www.adobeforums.com/webx?13@@.59b6ed86</A>&gt;<BR>Replies <br /> by email are OK.<BR>Use the unsubscribe<BR>&lt;<A <br /> href="http://www.adobeforums.com/webx?280@@.59b6ed86%21folder=.3c060fa3" <br /> target=_blank>http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3</A>&gt; <br />  form to<BR>cancel your email <br /> subscription.<BR><BR><BR><BR><BR>------------------------------------------------------<BR>View/reply <br /> at &lt;<A href="http://www.adobeforums.com/webx?13@@.59b6ed86/0" <br /> target=_blank>http://www.adobeforums.com/webx?13@@.59b6ed86/0</A>&gt;<BR>Replies <br /> by email are OK.<BR>Use the unsubscribe form at<BR>&lt;<A <br /> href="http://www.adobeforums.com/webx?280@@.59b6ed86%21folder=.3c060fa3" <br /> target=_blank>http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3</A>&gt; <br /> to<BR>cancel your email <br /> subscription.<BR></BLOCKQUOTE><BR><BR><BR>------------------------------------------------------<BR>View/reply <br /> at &lt;<A href="http://www.adobeforums.com/webx?13@@.59b6ed86/1" <br /> target=_blank>http://www.adobeforums.com/webx?13@@.59b6ed86/1</A>&gt;<BR>Replies <br /> by email are OK.<BR>Use the unsubscribe form at &lt;<A <br /> href="http://www.adobeforums.com/webx?280@@.59b6ed86%21folder=.3c060fa3" <br /> target=_blank>http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3</A>&gt; <br /> to cancel your email <br /> subscription.<BR><BR><BR><BR>------------------------------------------------------<BR>View/reply <br /> at &lt;<A href="http://www.adobeforums.com/webx?13@@.59b6ed86/2" <br /> target=_blank>http://www.adobeforums.com/webx?13@@.59b6ed86/2</A>&gt;<BR>Replies <br /> by email are OK.<BR>Use the unsubscribe form at &lt;<A <br /> href="http://www.adobeforums.com/webx?280@@.59b6ed86%21folder=.3c060fa3" <br /> target=_blank>http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3</A>&gt; <br /> to cancel your email subscription. <br /> <BR></BLOCKQUOTE><BR><BR><BR>------------------------------------------------------<BR>View/reply <br /> at &lt;<A href="http://www.adobeforums.com/webx?13@@.59b6ed86/3" <br /> target=_blank>http://www.adobeforums.com/webx?13@@.59b6ed86/3</A>&gt;<BR>Replies <br /> by email are OK.<BR>Use the unsubscribe form at &lt;<A <br /> href="http://www.adobeforums.com/webx?280@@.59b6ed86%21folder=.3c060fa3" <br /> target=_blank>http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3</A>&gt; <br /> to cancel your email subscription.<BR></BLOCKQUOTE><BR><BR clear=all><BR>-- <br /> <BR>"Therefore, send not to know For whom the bell tolls. It tolls for <br /> thee."<BR><BR>Like the cut of my jib? Check out my Flex blog!<BR><BR>:: Josh <br /> 'G-Funk' McDonald<BR>:: 0437 221 380 :: <A <br /> href="mailto:josh@gfunk007.com">josh@gfunk007.com</A><BR>:: <A <br /> href="http://flex.joshmcdonald.info/">http://flex.joshmcdonald.info/</A><BR>:: <br /> <A <br /> href="http://twitter.com/sophistifunk">http://twitter.com/sophistifunk</A><BR><BR><BR><br /> <HR align=left width=200><br /> View/reply at <A href="http://www.adobeforums.com/webx?13@@.59b6ed86/4">How to <br /> Test AIR 1.5</A><BR>Replies by email are OK.<BR>Use the <A <br /> href="http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3">unsubscribe</A> <br /> form to cancel your email subscription.<BR><BR></BLOCKQUOTE>

I'm sure there's nothing stopping you from loading SWFs and SWZs and SWCs and loading them in AIR? Just treat them as normal files, and use whatever you please to push out updates etc?

-Josh




--
"Therefore, send not to know For whom the bell tolls. It tolls for thee."

Like the cut of my jib? Check out my Flex blog!

:: Josh 'G-Funk' McDonald

:: 0437 221 380 :: josh@gfunk007.com
:: http://flex.joshmcdonald.info/
:: http://twitter.com/sophistifunk

01. Thanks, I will continue testing with ADL and hopefully be able to move <br />up to a web-base, remote installation/update scenario in a couple of weeks.<br /><br />02. I'm sorry you feel that my failure to accept what may be 'intuitively <br />obvious to you' -- that I can design and test a 3D front end to FMS that <br />works the same in a native window as in a browser window -- indicates any <br />lack of faith in what will be delivered. So far, I have found subtle, <br />important differences, and I am sure there will be others that will just <br />have to be patiently tested before I get it right.<br /><br />03. So, I'm glad you asked about swz in an AIR environment because that is <br />a whole topic for which I have not been able to find any discussion on any <br />of the many fine forums you have. I understand product marketing and <br />product development, but I can't say that I ever managed those activities in <br />the environment you have in which several large projects co-exist with <br />lingering dependencies and even 'cultures' as diverse as you have with the <br />various acquisitions that come together in the suite of products you have <br />today.<br /><br />So, I will simply state that I think no one seems to have recognized that <br />your paradigm for 'desktop' versus 'web-based' software -- the essential <br />distinction which seems to describe Adobe's description of an AIR versus a <br />Flex application -- does not always hold. I understand the general <br />dichotomy, but it does not hold for my user base.<br /><br />You have lots of design papers and lots of software devoted to 'reducing the <br />burden' of ever-growing executables in the Flex framework by caching of your <br />or our rsls. That's a good idea. Why do you think it is not just as good <br />an idea for an AIR application? Probably because you think that an AIR <br />application will either be shipped on a CD, or sent over the Internet, but <br />relatively infrequently, so who cares if you have to ship out 10MBs or 2MBs? <br />My user cares.<br /><br />My user will get frequent updates to an ever-growing body of software called <br />an application, and he will get them over those same slow bandwidth network <br />links that the Flex user sees. What's "good for the goose is good for the <br />gander". There is simply no reason not to architect the library of code <br />that we use to cobble together the application and use the same intelligent <br />caching mechanism in both environments. I looked for a month for a white <br />paper or discussion of how to 'modularize' an AIR app but all that you <br />wanted to publish were white papers on how to 'modularize' a Flex app.<br /><br />I'm sure that you guys have a bunch of object diagrams and product <br />architecture blueprints that you have memorized -- but that is not what we <br />see 'outside the black box'. What we see is a confusing distinction between <br />the AIR efforts and the Flex efforts although the code base and efforts are <br />substantially the same. And if that is true from an internals point of <br />view, put on your end-user hat and look at how we view a AIR/Flex app -- it <br />is all one.<br /><br />So, I develop the worlds greatest Juke Box and get it all going in Flex, <br />then I move that into one Tab on one Screen in the AIR 'shell'. Then some <br />guys go off and mostly use AIR-unique code to add a Tab that allows Drag and <br />Drop creation of Slide Shows accompanied by voice overs, and another set of <br />my guys go off to add the 'Sudoku' module in just plain old Flex. At some <br />point in time in some ant task, we've got 10MB of code and X MBs of that is <br />in one of our present [or future] swz files. Where is the distinction that <br />says I should just ask my users to download the whole shooting match, when <br />what he really wants to do is just download whatever updated or new <br />application modules [including any upgrades to your frameworks] when <br />required.<br /><br />So, it took some time, but today, my application is compiled with dynamic <br />linking to the framework.swz, and when the user launches his AIR application <br />on the desktop, the Flash Player, embedded in the AIR environment, is smart <br />enough to find that it already has the necessary framework code and does not <br />need to go back to the network to get it refreshed. Actually, since I could <br />never figure out how to use Module and ModuleManager, the method for solving <br />the framework caching problem ended up just being an extension of what I <br />developed for version management 'with continuous update' of my own swf <br />files. So, when the AIR shell starts up, it needs to test to see whether <br />there is any updating to be done, or whether it already has locally <br />available the 'latest and greatest' and that works the same for <br />MyCute3DWizBang.swf or framework_3.1.0.2710.swz or framework_4.0.0.3988.swf.<br /><br />If you take the point of view that a 'desktop application' doesn't need to <br />do anything special to solve the problem of 'large file downloads', you end <br />up thinking that there is no reason for an AIR application to take advantage <br />of the frameworked cache when, in fact, almost all of that code is needed <br />whether the execution thread starts in a 'WindowApplication' or just a plain <br />old 'Application'. At least thats the cockamaymee point of view that I came <br />to in the absence of any 'best practice' discussion of these key topics -- <br />so far, it seems to be working pretty well, but as you can guess, testing <br />across a network to a remote host that may or may not have the right version <br />of AIR, or the right version of framework, or the right version of <br />MyCute3DWizBang is really more important than just testing against ADL.<br /><br /><br />----- Original Message ----- <br />From: "Matt Chotin" <member@adobeforums.com><br />To: <flexsdk-dev@adobeforums.com><br />Sent: Monday, November 03, 2008 8:39 PM<br />Subject: Re: How to Test AIR 1.5<br /><br /><br />>A new message was posted by Matt Chotin in<br />><br />> Developers --<br />> How to Test AIR 1.5<br />><br />> The badge install doesn't work with debug, you can only use adl.exe right <br />> now. But this should show how the whole system would work and really <br />> allow you to evaluate. You know how the AIR install works with Air 1.1 <br />> (if not, use Flex 3.1 to target 1.1), I don't think seeing it with AIR 1.5 <br />> is critical to evaluate the features of the runtime at this point.<br />><br />> Air and the Flash Player are runtimes, and we've made it clear that AIR <br />> 1.5 would include FP10 features. So when we say Flex will enable FP10, it <br />> should be obvious that when AIR 1.5 comes out Flex will support it in the <br />> same way.<br />><br />> I don't really understand what you're doing with the SWZ and AIR, there's <br />> no real need to use a cached framework when the whole app is going to be <br />> installed.<br />><br />> In any case, Air 1.5 should be out in 2 weeks hopefully so you'll be set <br />> then.<br />><br />> Matt<br />><br />> On 11/3/08 8:07 PM, "Terry Corbet" <member@adobeforums.com> wrote:<br />><br />> A new message was posted by Terry Corbet in<br />><br />> Developers --<br />> How to Test AIR 1.5<br />><br />> Thanks for the quick turnaround. Pardon my ignorance, but exactly what <br />> .exe<br />> file will install Air 1.5 on a system? I don't find it anywhere. I guess <br />> I<br />> can try to tear the ADL source apart to see how it mimics that behavior, <br />> but<br />> that is, at best, just a local test. I think testing the whole Badge<br />> install sequence is essential, and would like to give it a try. The <br />> longer<br />> we put this off, the longer we all just sit here trying to decide whether <br />> to<br />> stay with Papervision, Away, Sandy, or to use the graphics support in the<br />> Player.<br />><br />> I am busy making the dynamic link to the framework.swz work for Flex <br />> modules<br />> running under an AIR shell, and I doubt that I am alone. There must be <br />> many<br />> of us who really see no distinction between AIR and Flex -- they just<br />> provide us two different ways to slice a problem, that's why it is so<br />> disconcerting to try to follow the threads on rapid Flex advancement with <br />> FP<br />> 10, but almost nothing pertaining the doing the very same things with the<br />> AIR toolkit.<br />><br />> I hope you can tell me where to get the standalone AIR 1.5 installer that<br />> will me keep making progress with the debugging output reasonably well<br />> handled by Allesandros' FireFox tracer. Many thanks.<br />><br />><br />> ----- Original Message -----<br />> From: "Matt Chotin" <member@adobeforums.com><br />> To: <flexsdk-dev@adobeforums.com><br />> Sent: Monday, November 03, 2008 7:55 PM<br />> Subject: Re: How to Test AIR 1.5<br />><br />><br />>>A new message was posted by Matt Chotin in<br />>><br />>> Developers --<br />>> How to Test AIR 1.5<br />>><br />>> Hi,<br />>><br />>> We're not doing a public beta of the release runtime for AIR 1.5. You <br />>> can<br />>> use the debug runtimes that are part of the Flex nightly builds though<br />>> (check the Flex 3 nightlies) to validate that AIR 1.5 will be right for<br />>> you though.<br />>><br />>> Matt<br />>><br />>> On 11/3/08 7:38 PM, "Terry Corbet" <member@adobeforums.com> wrote:<br />>><br />>> A new discussion was started by Terry Corbet in<br />>><br />>> Developers --<br />>> How to Test AIR 1.5<br />>><br />>> Sorry if this seems slightly off center, but I blame Adobe, not myself.<br />>> Trying to determine the true status and positioning of AIR amongst the<br />>> various Flex forums and projects for an outsider is practically<br />>> impossible. So, I will be brief. In September Mr. Chambers sent opened<br />>> the flow by telling us that we could find FP10 integrated with Flex SDK <br />>> in<br />>> something you call 1.5 or Cosmo, or both. He was properly circumspect, <br />>> so<br />>> I didn't rush into it -- there was not even an ADL binary when I checked.<br />>> Now it is November, the Trunk is at 4005, and ostensibly, everything we<br />>> need to start trying to take advantage of FP support of 3D operations is<br />>> out there. But where? Where do we get a version of AIR 1.5 that can be<br />>> installed on a target desktop, so that we can try to run the ADT test<br />>> cycle?<br />>><br />>> Call it Gumbo, call it Flex4, call it whatever, but can someone tell us<br />>> how to start testing it for AIR application deployment?<br />>><br />>> Thank you.<br />>><br />>> ________________________________<br />>> View/reply at How to Test AIR 1.5<br />>> <a href=http://www.adobeforums.com/webx?13@@.59b6ed86><br />>> Replies by email are OK.<br />>> Use the unsubscribe<br />>> <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> form <br />>> to<br />>> cancel your email subscription.<br />>><br />>><br />>><br />>><br />>> ------------------------------------------------------<br />>> View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b6ed86/0><br />>> Replies by email are OK.<br />>> Use the unsubscribe form at<br />>> <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> to<br />>> cancel your email subscription.<br />><br />><br />><br />> ------------------------------------------------------<br />> View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b6ed86/1><br />> Replies by email are OK.<br />> Use the unsubscribe form at <br />> <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> to <br />> cancel your email subscription.<br />><br />><br />><br />> ------------------------------------------------------<br />> View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b6ed86/2><br />> Replies by email are OK.<br />> Use the unsubscribe form at <br />> <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> to <br />> cancel your email subscription.

The badge install doesn't work with debug, you can only use adl.exe right now. But this should show how the whole system would work and really allow you to evaluate. You know how the AIR install works with Air 1.1 (if not, use Flex 3.1 to target 1.1), I don't think seeing it with AIR 1.5 is critical to evaluate the features of the runtime at this point.<br /><br />Air and the Flash Player are runtimes, and we've made it clear that AIR 1.5 would include FP10 features. So when we say Flex will enable FP10, it should be obvious that when AIR 1.5 comes out Flex will support it in the same way.<br /><br />I don't really understand what you're doing with the SWZ and AIR, there's no real need to use a cached framework when the whole app is going to be installed.<br /><br />In any case, Air 1.5 should be out in 2 weeks hopefully so you'll be set then.<br /><br />Matt<br /><br />On 11/3/08 8:07 PM, "Terry Corbet" <member@adobeforums.com> wrote:<br /><br />A new message was posted by Terry Corbet in<br /><br />Developers --<br /> How to Test AIR 1.5<br /><br />Thanks for the quick turnaround. Pardon my ignorance, but exactly what .exe<br />file will install Air 1.5 on a system? I don't find it anywhere. I guess I<br />can try to tear the ADL source apart to see how it mimics that behavior, but<br />that is, at best, just a local test. I think testing the whole Badge<br />install sequence is essential, and would like to give it a try. The longer<br />we put this off, the longer we all just sit here trying to decide whether to<br />stay with Papervision, Away, Sandy, or to use the graphics support in the<br />Player.<br /><br />I am busy making the dynamic link to the framework.swz work for Flex modules<br />running under an AIR shell, and I doubt that I am alone. There must be many<br />of us who really see no distinction between AIR and Flex -- they just<br />provide us two different ways to slice a problem, that's why it is so<br />disconcerting to try to follow the threads on rapid Flex advancement with FP<br />10, but almost nothing pertaining the doing the very same things with the<br />AIR toolkit.<br /><br />I hope you can tell me where to get the standalone AIR 1.5 installer that<br />will me keep making progress with the debugging output reasonably well<br />handled by Allesandros' FireFox tracer. Many thanks.<br /><br /><br />----- Original Message -----<br />From: "Matt Chotin" <member@adobeforums.com><br />To: <flexsdk-dev@adobeforums.com><br />Sent: Monday, November 03, 2008 7:55 PM<br />Subject: Re: How to Test AIR 1.5<br /><br /><br />>A new message was posted by Matt Chotin in<br />><br />> Developers --<br />> How to Test AIR 1.5<br />><br />> Hi,<br />><br />> We're not doing a public beta of the release runtime for AIR 1.5. You can<br />> use the debug runtimes that are part of the Flex nightly builds though<br />> (check the Flex 3 nightlies) to validate that AIR 1.5 will be right for<br />> you though.<br />><br />> Matt<br />><br />> On 11/3/08 7:38 PM, "Terry Corbet" <member@adobeforums.com> wrote:<br />><br />> A new discussion was started by Terry Corbet in<br />><br />> Developers --<br />> How to Test AIR 1.5<br />><br />> Sorry if this seems slightly off center, but I blame Adobe, not myself.<br />> Trying to determine the true status and positioning of AIR amongst the<br />> various Flex forums and projects for an outsider is practically<br />> impossible. So, I will be brief. In September Mr. Chambers sent opened<br />> the flow by telling us that we could find FP10 integrated with Flex SDK in<br />> something you call 1.5 or Cosmo, or both. He was properly circumspect, so<br />> I didn't rush into it -- there was not even an ADL binary when I checked.<br />> Now it is November, the Trunk is at 4005, and ostensibly, everything we<br />> need to start trying to take advantage of FP support of 3D operations is<br />> out there. But where? Where do we get a version of AIR 1.5 that can be<br />> installed on a target desktop, so that we can try to run the ADT test<br />> cycle?<br />><br />> Call it Gumbo, call it Flex4, call it whatever, but can someone tell us<br />> how to start testing it for AIR application deployment?<br />><br />> Thank you.<br />><br />> ________________________________<br />> View/reply at How to Test AIR 1.5<br />> <a href=http://www.adobeforums.com/webx?13@@.59b6ed86><br />> Replies by email are OK.<br />> Use the unsubscribe<br />> <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> form to<br />> cancel your email subscription.<br />><br />><br />><br />><br />> ------------------------------------------------------<br />> View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b6ed86/0><br />> Replies by email are OK.<br />> Use the unsubscribe form at<br />> <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> to<br />> cancel your email subscription.<br /><br /><br /><br />------------------------------------------------------<br />View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b6ed86/1><br />Replies by email are OK.<br />Use the unsubscribe form at <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> to cancel your email subscription.

Thanks for the quick turnaround. Pardon my ignorance, but exactly what .exe <br />file will install Air 1.5 on a system? I don't find it anywhere. I guess I <br />can try to tear the ADL source apart to see how it mimics that behavior, but <br />that is, at best, just a local test. I think testing the whole Badge <br />install sequence is essential, and would like to give it a try. The longer <br />we put this off, the longer we all just sit here trying to decide whether to <br />stay with Papervision, Away, Sandy, or to use the graphics support in the <br />Player.<br /><br />I am busy making the dynamic link to the framework.swz work for Flex modules <br />running under an AIR shell, and I doubt that I am alone. There must be many <br />of us who really see no distinction between AIR and Flex -- they just <br />provide us two different ways to slice a problem, that's why it is so <br />disconcerting to try to follow the threads on rapid Flex advancement with FP <br />10, but almost nothing pertaining the doing the very same things with the <br />AIR toolkit.<br /><br />I hope you can tell me where to get the standalone AIR 1.5 installer that <br />will me keep making progress with the debugging output reasonably well <br />handled by Allesandros' FireFox tracer. Many thanks.<br /><br /><br />----- Original Message ----- <br />From: "Matt Chotin" <member@adobeforums.com><br />To: <flexsdk-dev@adobeforums.com><br />Sent: Monday, November 03, 2008 7:55 PM<br />Subject: Re: How to Test AIR 1.5<br /><br /><br />>A new message was posted by Matt Chotin in<br />><br />> Developers --<br />> How to Test AIR 1.5<br />><br />> Hi,<br />><br />> We're not doing a public beta of the release runtime for AIR 1.5. You can <br />> use the debug runtimes that are part of the Flex nightly builds though <br />> (check the Flex 3 nightlies) to validate that AIR 1.5 will be right for <br />> you though.<br />><br />> Matt<br />><br />> On 11/3/08 7:38 PM, "Terry Corbet" <member@adobeforums.com> wrote:<br />><br />> A new discussion was started by Terry Corbet in<br />><br />> Developers --<br />> How to Test AIR 1.5<br />><br />> Sorry if this seems slightly off center, but I blame Adobe, not myself. <br />> Trying to determine the true status and positioning of AIR amongst the <br />> various Flex forums and projects for an outsider is practically <br />> impossible. So, I will be brief. In September Mr. Chambers sent opened <br />> the flow by telling us that we could find FP10 integrated with Flex SDK in <br />> something you call 1.5 or Cosmo, or both. He was properly circumspect, so <br />> I didn't rush into it -- there was not even an ADL binary when I checked. <br />> Now it is November, the Trunk is at 4005, and ostensibly, everything we <br />> need to start trying to take advantage of FP support of 3D operations is <br />> out there. But where? Where do we get a version of AIR 1.5 that can be <br />> installed on a target desktop, so that we can try to run the ADT test <br />> cycle?<br />><br />> Call it Gumbo, call it Flex4, call it whatever, but can someone tell us <br />> how to start testing it for AIR application deployment?<br />><br />> Thank you.<br />><br />> ________________________________<br />> View/reply at How to Test AIR 1.5 <br />> <a href=http://www.adobeforums.com/webx?13@@.59b6ed86><br />> Replies by email are OK.<br />> Use the unsubscribe <br />> <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> form to <br />> cancel your email subscription.<br />><br />><br />><br />><br />> ------------------------------------------------------<br />> View/reply at <a href=http://www.adobeforums.com/webx?13@@.59b6ed86/0><br />> Replies by email are OK.<br />> Use the unsubscribe form at <br />> <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> to <br />> cancel your email subscription.

Hi,<br /><br />We're not doing a public beta of the release runtime for AIR 1.5. You can use the debug runtimes that are part of the Flex nightly builds though (check the Flex 3 nightlies) to validate that AIR 1.5 will be right for you though.<br /><br />Matt<br /><br />On 11/3/08 7:38 PM, "Terry Corbet" <member@adobeforums.com> wrote:<br /><br />A new discussion was started by Terry Corbet in<br /><br />Developers --<br /> How to Test AIR 1.5<br /><br />Sorry if this seems slightly off center, but I blame Adobe, not myself. Trying to determine the true status and positioning of AIR amongst the various Flex forums and projects for an outsider is practically impossible. So, I will be brief. In September Mr. Chambers sent opened the flow by telling us that we could find FP10 integrated with Flex SDK in something you call 1.5 or Cosmo, or both. He was properly circumspect, so I didn't rush into it -- there was not even an ADL binary when I checked. Now it is November, the Trunk is at 4005, and ostensibly, everything we need to start trying to take advantage of FP support of 3D operations is out there. But where? Where do we get a version of AIR 1.5 that can be installed on a target desktop, so that we can try to run the ADT test cycle?<br /><br />Call it Gumbo, call it Flex4, call it whatever, but can someone tell us how to start testing it for AIR application deployment?<br /><br />Thank you.<br /><br />________________________________<br />View/reply at How to Test AIR 1.5 <a href=http://www.adobeforums.com/webx?13@@.59b6ed86><br />Replies by email are OK.<br />Use the unsubscribe <a href=http://www.adobeforums.com/webx?280@@.59b6ed86!folder=.3c060fa3> form to cancel your email subscription.