Hey Rick, AIR apps can be converted to run on iOS. I'm pretty sure that is using a tool in CS 5. Apple tried to kill that, but eventually allowed for "converted" code instead of natively written Ojective C.
They can also be exported to run on Android (which is why we are using it). .....and as an added bonus...if you learn AIR, you're learninga whole lot about FLEX at the same time (AIR essentially adds functionality on top of FLEX.....things like local file system access and other things a standard web app can't do). As with any other decision.....best tool for the job. The way we see it here is it is one tool for multiple platforms...and that "should" save time (and no time wasted getting that pixel perfect cross-browser user experience....which I LOVE). Cheers On Mon, 2011-06-27 at 12:08 -0400, Rick Faircloth wrote: > Ok, Bryan... time for some questions about AIR. > > (I'm reading over the Adobe site concerning AIR, but > wanted to ask an "advocate", as well...) > > First question is, how can AIR apps run on iOS? > Isn't the output Flash based, which won't play on iOS? > > Rick > > -----Original Message----- > From: Bryan Stevenson [mailto:br...@electricedgesystems.com] > Sent: Sunday, June 26, 2011 6:17 PM > To: cf-talk > Subject: RE: Need some perspective... > > > Well Rick...one browser if you will...AIR ;-) > > On Sat, 2011-06-25 at 09:46 -0400, Rick Faircloth wrote: > > > Thanks for the feedback, Maureen. > > > > I know how you feel. I wish we could just > > have one browser to rule them all. I don't > > even want to think about how good that would be... > > > > > > -----Original Message----- > > From: Maureen [mailto:mamamaur...@gmail.com] > > Sent: Saturday, June 25, 2011 2:56 AM > > To: cf-talk > > Subject: Re: Need some perspective... > > > > > > Exactly my findings. There are still enough desktop users with > > non-compliant browsers that HTML/CSS3 are problematic. I'm currently > > refactoring all my sites for new technologies, attempting to make them > > both fully assessable for screen reader/text browsers and for mobile > > browsers. I'm doing a lot of detection and loading code and style > > sheets based on what browser is being used, but it's a steady pain to > > keep up with what works and what doesn't. When I get really grumpy, > > my urge is to just feed a text based site to anyone using IE with a > > note at the top that says if "you want to see the pretty stuff, get a > > real browser". > > > > On Fri, Jun 24, 2011 at 10:24 PM, Sean Corfield <seancorfi...@gmail.com> > > wrote: > > > > > > On Fri, Jun 24, 2011 at 8:05 PM, Rick Faircloth > > > <r...@whitestonemedia.com> wrote: > > >> "To us or not to use HTML5 and CSS3" in desktop > > >> and mobile development. > > > > > > This came up in a few sessions at JAXconf this week. The general > > > consensus seemed to be that HTML5 / CSS3 is a solid bet for mobile - > > > because mobile browsers offer solid support already. The same is not > > > true on the desktop, unless you're prepared to "encourage" your users > > > to upgrade / switch browsers. > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:345772 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
