So I tried a few things and it seems a little better now.
1. I combined a couple projects, so now I have one main project, and 25 library
projects.
2. I removed as many unneeded Flex Library SWCs from the SDK entry in the
Library Path tab of each project. This included all the automation
Yes, there are AIR and Flex projects in the same workspace, but at the moment,
the AIR projects are closed.
I'm not sure what you mean by the second response. Could you give me an
example?
--- In flexcoders@yahoogroups.com, Peter Farland pfarl...@... wrote:
Are you mixing AIR and Flex
I probably don't REALLY need all these projects, but that's the way it was
originally set up. It's a very large project. Hundreds of thousands of lines
of code. So that's how it evolved into the beast it is today.
We use Maven to build our production builds, but all the developers build via
Of Geoffrey
Sent: Thursday, April 30, 2009 4:33 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Eclipse Crashing
Yes, there are AIR and Flex projects in the same workspace, but at the moment,
the AIR projects are closed.
I'm not sure what you mean by the second response. Could you
minimum to save memory.
Pete
-Original Message-
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
Behalf Of Geoffrey
Sent: Thursday, April 30, 2009 4:33 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Eclipse Crashing
Yes, there are AIR and Flex
I'll certainly try everyone's suggestions when I get back from vacation. :D
Thanks for everyone's help/advise.
--- In flexcoders@yahoogroups.com, Kevin F. Benz kb...@... wrote:
Oh. I thought you can get past the module dependency by linking the SWC and
binding the source to the swc in the
6 matches
Mail list logo
