flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kessler CTR Mark J <mark.kessler....@usmc.mil>
Subject RE: Those @#*$^ Environment Variables
Date Mon, 16 Nov 2015 19:00:06 GMT
It was just based on someone else's comment about cleaning up and restructuring some.  I'm
sure it only really affects those of us who using synching.   Having a few thousand less files
per sdk to check/synch can make a speed difference.


-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Monday, November 16, 2015 1:45 PM
To: dev@flex.apache.org
Subject: Re: Those @#*$^ Environment Variables

On 11/16/15, 9:36 AM, "Kessler CTR Mark J" <mark.kessler.ctr@usmc.mil>

>    Well for one of my dev machines, we've removed all the source, build
>files, property files, samples, and templates out of the folders.
>Multiple SDK's stored in a shared parent folder.  The sdk folders are
>labeled things like "Flex 4.14.1" / "Flex 4.13.0" / "Flex 4.6.0".  I have
>them setup in FD so if I need to change the SDK used in a project I can
>simply select it out of a drop down in the project properties.

I think I’m still lost.  Is there a benefit to removing those files other
than saving disk space?  The Installer can install individual Flex
versions to a shared parent folder if you want, and at least in FB, I can
install each SDK version and switch between them.


View raw message