Re: {Disarmed} [flexcoders] AIR update framework only works to update AIR file
Hi KFB,
Thank you for your great input.
So basically for my need, I need to have a customized update system
since I am dealing not just AIR file but other files as well.
There are a number of references about determining whether it's the
first-run or not so adaptation of those techniques is probably worth
looking at.
Could you please let me know where I can get these references?
Thanks!
--- In flexcoders@yahoogroups.com, Kevin Benz kb...@... wrote:
You need to be aware of the two paths to update Air applications.
The UI
approach, one where you configure the UI of the update process
through a
XML file and an API approach where you take programmatic control of
the
update. Ultimately the goal of the UpdaterUI was to update the Air
file
alone (and then start it)so if you need to move files around, update
SQLite or something like that, you are going to have to do what you
need
in Actionscript. The update framework in no-way has the
capabilities of
commercial installers. Can't call external processes, directly move
files around, etc
Since the updater mechanisms are running in the old code, not the
new
Air file, it can't know what needs to updated, meaning you are going
to
end up writing code in your app's normal bootstrap process that
determines that an update has occurred and makes the necessary
changes.
There are a number of references about determining whether it's the
first-run or not so adaptation of those techniques is probably worth
looking at.
In our apps, we have the current client version in the SQLite
database.
If the running client does not match that version number, we call
whatever update process we need and on completion update SQLite to
the
current running client version id.
KFB
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com]
On
Behalf Of handitan
Sent: Friday, February 13, 2009 1:02 PM
To: flexcoders@yahoogroups.com
Subject: {Disarmed} [flexcoders] AIR update framework only works
to
update AIR file?
Hi all,
I have been reading articles about using AIR update framework.
To my understanding this only works to update AIR file??
I hope I am wrong...
Since my AIR app is using Flex-only swcs and is loading Flex-only
modules.
Anybody can shed a light on this?
--
This message has been scanned for viruses and
dangerous content by MailScanner http://www.mailscanner.info/ ,
and is
believed to be clean.
RE: {Disarmed} [flexcoders] AIR update framework only works to update AIR file
Mike Chambers blog should be a starting point.
http://www.mikechambers.com/blog/2007/11/07/detecting-whether-an-air-app
lication-has-run-before/
KFB
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
Behalf Of handitan
Sent: Monday, February 16, 2009 8:04 AM
To: flexcoders@yahoogroups.com
Subject: Re: {Disarmed} [flexcoders] AIR update framework only works
to update AIR file
Hi KFB,
Thank you for your great input.
So basically for my need, I need to have a customized update system
since I am dealing not just AIR file but other files as well.
There are a number of references about determining whether it's the
first-run or not so adaptation of those techniques is probably worth
looking at.
Could you please let me know where I can get these references?
Thanks!
--- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com
, Kevin Benz kb...@... wrote:
You need to be aware of the two paths to update Air applications.
The UI
approach, one where you configure the UI of the update process
through a
XML file and an API approach where you take programmatic control of
the
update. Ultimately the goal of the UpdaterUI was to update the Air
file
alone (and then start it)so if you need to move files around, update
SQLite or something like that, you are going to have to do what you
need
in Actionscript. The update framework in no-way has the
capabilities of
commercial installers. Can't call external processes, directly move
files around, etc
Since the updater mechanisms are running in the old code, not the
new
Air file, it can't know what needs to updated, meaning you are going
to
end up writing code in your app's normal bootstrap process that
determines that an update has occurred and makes the necessary
changes.
There are a number of references about determining whether it's the
first-run or not so adaptation of those techniques is probably worth
looking at.
In our apps, we have the current client version in the SQLite
database.
If the running client does not match that version number, we call
whatever update process we need and on completion update SQLite to
the
current running client version id.
KFB
From: flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com
[mailto:flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com
]
On
Behalf Of handitan
Sent: Friday, February 13, 2009 1:02 PM
To: flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com
Subject: {Disarmed} [flexcoders] AIR update framework only works
to
update AIR file?
Hi all,
I have been reading articles about using AIR update framework.
To my understanding this only works to update AIR file??
I hope I am wrong...
Since my AIR app is using Flex-only swcs and is loading Flex-only
modules.
Anybody can shed a light on this?
--
This message has been scanned for viruses and
dangerous content by MailScanner http://www.mailscanner.info/ ,
and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner http://www.mailscanner.info/ , and is
believed to be clean.
image001.jpgimage002.jpg
RE: {Disarmed} [flexcoders] AIR update framework only works to update AIR file?
You need to be aware of the two paths to update Air applications. The UI
approach, one where you configure the UI of the update process through a
XML file and an API approach where you take programmatic control of the
update. Ultimately the goal of the UpdaterUI was to update the Air file
alone (and then start it)so if you need to move files around, update
SQLite or something like that, you are going to have to do what you need
in Actionscript. The update framework in no-way has the capabilities of
commercial installers. Can't call external processes, directly move
files around, etc
Since the updater mechanisms are running in the old code, not the new
Air file, it can't know what needs to updated, meaning you are going to
end up writing code in your app's normal bootstrap process that
determines that an update has occurred and makes the necessary changes.
There are a number of references about determining whether it's the
first-run or not so adaptation of those techniques is probably worth
looking at.
In our apps, we have the current client version in the SQLite database.
If the running client does not match that version number, we call
whatever update process we need and on completion update SQLite to the
current running client version id.
KFB
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
Behalf Of handitan
Sent: Friday, February 13, 2009 1:02 PM
To: flexcoders@yahoogroups.com
Subject: {Disarmed} [flexcoders] AIR update framework only works to
update AIR file?
Hi all,
I have been reading articles about using AIR update framework.
To my understanding this only works to update AIR file??
I hope I am wrong...
Since my AIR app is using Flex-only swcs and is loading Flex-only
modules.
Anybody can shed a light on this?
--
This message has been scanned for viruses and
dangerous content by MailScanner http://www.mailscanner.info/ , and is
believed to be clean.
image001.jpgimage002.jpg
