Very interesting here. It appears in the full release version of AIR you
will be able to bundle the Adobe AIR with your app. So that headache will
not be a problem.
 
John
[EMAIL PROTECTED]
 

  _____  

From: Kevin Hoyt [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 23, 2007 5:09 PM
To: John Mason; [EMAIL PROTECTED]
Subject: Re: Some AIR questions from the Atl Flash/Flex user group


Hey John,

To clarify, in AIR 1.0 this will be possible.  Unless Mike knows better
(altogether likely), we haven't put this feature in AIR Beta 1.

Thanks,
Kevin


On 7/23/07 2:55 PM, "John Mason" <[EMAIL PROTECTED]> wrote:



Thanks, I forwarded this on to the group. I had one other question..

>Also note that developers can deploy the runtime with their application,
which is distinctly different from the >Flash Player
 
I didn't know this and been digging around eclipse trying to find how this
can be bundle. It didn't appear as an option in the export?
 
John
[EMAIL PROTECTED]
 


  _____  

From: Kevin Hoyt [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 23, 2007 1:55 PM
To: John Mason; [EMAIL PROTECTED]
Subject: Re: Some AIR questions from the Atl Flash/Flex user group

Hi John,



*       AIR  can use RSL's, but probably not the ones cached in the browser
(i.e. Flex 3).   I don't have any details just yet on how signing will
impact the  security model.   

*       First  is that Adobe is really good at distributing runtimes (i.e.
Flash, Acrobat).   It stands to reason that we'll use these techniques,
along with other  alliances to promote the distribution of the runtime.
That being said,  we're not prepared to disclose all those details just yet.
Also note  that developers can deploy the runtime with their application,
which is  distinctly different from the Flash Player.  Then there's the
lighting  installation experience you may have encountered on the samples
page on Labs.    

*       Yes,  remote objects will work in AIR.  There's already some
information about  this in third-party and Adobe blogs.  The main thing is
that the  application no longer has a server context, so the configuration
files on the  server for the remote objects needs to be more specific.   

*       Multiple versions of the runtime will be able to  co-exist on the
same machine.  AIR provides the hooks for the application  to be notified of
new versions of the runtime, and then defers to the  application developer
to chose what it is that they want to do next.  One  might assume that we'll
make this process as transparent as possible.    

*       Right  now the replace/repair dialog is controlled by AIR.  Managing
trials is  something that's not new to desktop software, though we don't
have a specific  answer at this time.  I think this really comes down to how
the software  is designed.  I could see a scenario as an example where the
application  checks the vendors server for a valid key/subscription when it
starts.   Other approaches might involve encrypting a key somewhere on the
file  system.   

*       We  chose WebKit in part for it's mobile footprint.  That's clearly
a market  for AIR post 1.0.  Outside of that we haven't announced anything
to the  public.



Hope this helps,
Kevin


On 7/19/07 6:28 PM, "John Mason" <[EMAIL PROTECTED]> wrote:



Hey  Guys,

Last night, at our  local Flash/Flex User group (www.affug.com) here in
Atlanta, I gave a  presentation on the new features in Flex 3 and AIR. I got
several questions on  AIR that I wanted to pass along so we get the official
word from the Adobe  crew. We have several people planning on attending the
AIR Bus tour when it  comes to the ATL. Here are some the that I can
remember from last  night.

-can AIR utilize the same shared RSLs like in Flex? Signed and  unsigned?

-How is Adobe planning to distribute AIR. Can it be bundle  with Adobe PDF
and/or Flash player installers (sort of like Google Tools are  in some
software) so we as AIR developers can know that over time people will  more
that likely have the Adobe Intregrated Runtime on their  computer.

-Will AIR support Remote Objects? We have a group of Java  developers that
wouldn't be using ColdFusion so any info on direct Java to AIR
communication would be helpful.

-How will AIR update? When AIR 2.0  comes will AIR know about it and advise
the use to upgrade? Or if the user  tries to run an AIR 2.0 version on AIR
1.0 when it advise them then. We had  several people asking about these "in
the future" type questions.

-If  you try to reinstall an AIR app. The dialog box gives you the option
for  Repair and Remove, is there any functionality that will exposed to us
as  developers or is this all on the AIR side? The idea here being if an AIR
app  has a 30-day trial period that someone removes and then reinstalls to
avoid  paying for the software.
 
-When AIR is  available for mobile devices will there be something like an
AIR Lite edition.  We figured that a lot of  the graphical features of a
full AIR app would  probably burn through a cell phone battery pretty darn
fast :)  
thanks in  advance,

John Mason
[EMAIL PROTECTED]  <mailto:[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]>  
Atlanta Flash/Flex User Group












-------------------------------------------------------------
To unsubscribe from this list, simply email the list with unsubscribe in the 
subject line

For more info, see http://www.affug.com
Archive @ http://www.mail-archive.com/discussion%40affug.com/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------

Reply via email to