flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From OmPrakash Muppirala <bigosma...@gmail.com>
Subject Re: [FALCON] Installer (was: Basic Tests pass)
Date Fri, 25 Oct 2013 21:06:37 GMT
On Fri, Oct 25, 2013 at 1:15 PM, Alex Harui <aharui@adobe.com> wrote:

> On 10/25/13 11:41 AM, "OmPrakash Muppirala" <bigosmallm@gmail.com> wrote:
> >
> >If you can post your thoughts on what it would take to get the Installer
> >to
> >support this, that would be good to know.
> Not only do we need to install Falcon, but someday, FlexJS, maybe other
> stuff as well.
> So I keep wondering:  In the Installer is code that:
> 1) offers a set of choice
> 2) displays licenses for those choices
> 3) based on selected choices:
>         A) downloads stuff
>         B) Copies stuff
>         C) Edits stuff
>         D) etc.
> What would it take to be able to script an entire install from an xml
> file?  It would be sort of like Ant commands, but simpler to start with.
> It seems like most of the changes we know are coming are just different
> combinations of the available functionality.  Even for the Flex SDK, we
> will eventually drop the BlazeDS jar and Embedded Font Jars from the list
> of choices.
> Doing this work might net out to be less work than customizing logic for
> the various things we have to install and voting for each change.
> Thoughts?
> -Alex
Yes, as I was building the Installer, I had something like this in mind.
Pretty much all the components have a source url, destination directory,
unzip or untar operations, MD5 check, etc.  We should be able to drive the
Installer off of an xml file.

I am thinking of possibly re-using the Ant xml schema and interpret them in
AS3, instead of inventing a new XML schema for our purposes.

It would be nice to have some help from the community to go in this


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message