Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Adding Flex Unit to installer
From: Justin Mclean <justin@classsoftware.com>
In-Reply-To: <D05CA601.1A1AC%aharui@adobe.com>
Date: Fri, 10 Oct 2014 17:43:36 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2730AD10-E4A0-4F14-81A5-2022EBA48ADC@classsoftware.com>
References: <E01711EE-0274-4132-B810-C3434BC6AEF3@me.com>
 <D05CA601.1A1AC%aharui@adobe.com>
To: dev@flex.apache.org

Hi,

> Are you suggesting that we change the install experience for 4.13.0 =
and
> older releases?

Yes I can see users wanting to install Flex Unit (or Tour De Flex) as an =
optional install while installing the SDK.

> One advantage of having all of the steps in the ant script is that our =
Linux users (and anybody else who doesn=B9t or can=B9t run
> AIR) get a rough command-line equivalent.

Which would have minimal impact on them, Flex Unit doesn't (as far a sI =
know) really have any install steps as such it just download, check md5, =
and unpack. For the stand alone install is doesn't need an install =
script, for the integrated into the SDK install it requires one. Linux =
users are not least out and can still use ant if they want.

> I think what you want to do is just chain a few installs together as =
in
> =B3Hey, you=B9ve installed A, would you be interested in installing B=B2=
 or do
> you envision something more tightly integrated?

More integrated as it would show up as an optional component in the =
installer for the SDK.

Thanks,
Justin