Thank you Kevin! I will try to do this during the next FB update. I had a gut feeling that having just an Eclipse & FB plugin is much better due to wider support (Java freaks :)
PS I have submitted a bug re. FlexBuilder.ini. https://bugs.adobe.com/jira/browse/FB-16668 Seems like it ignores standard location and get the params from some .configuration dir instead. Cheers, Dmitri. --- In flexcoders@yahoogroups.com, "Kevin Benz" <kb...@...> wrote: > > On Vista, I would search for other copies of that file in weird places. > A synchronization folder for example. I have no experience running > FlexBuilder(FB) on Vista as I prefer to avoid painful challenges where I > can. > > > > Here is an idea for you.... (although a little off topic). > > > > We don't install the full FB IDE but rather do the follow.. It also > makes FB a lot faster and reduces the memory overhead.. This may seem > really strange. > > > > All of our developers install the C++ version of Eclipse 3.3.2 and then > disable the C++ plug-in. Then install the FB plug-in. There is just so > much goo that comes in with standard FB from Java and JDT that when you > will be surprised how quickly it boots. Downside is that those who do > both Java and FB end up with two installs but we try to isolate Flex > developers from IDE pain so I don't let them install many plug-ins > anyway. > > > > The way the MXML preview component leaks memory, you have to take > whatever shortcuts you can. > > > > KFB > > > > From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On > Behalf Of Dmitri Girski > Sent: Monday, January 19, 2009 2:56 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: Flex Builder 3 crashes (Vista) > > > > Hi Kevin, > > Thank you very much for such detailed instructions. > > First, I looked into the log - the exception I can see there is the > following: > !MESSAGE Error creating actionscript project for ui_login > !STACK 1 > org.eclipse.core.runtime.CoreException: Error Loading Project > > Then, I just recreated the new workspace and so far (2 days yet) have > not got any crashes. Who-hoo! > > PS Do you have any idea why FlexBuilder.ini is ignored under Vista? > > Cheers, > Dmitri. > > --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> > , "Kevin Benz" <kbenz@> wrote: > > > > Been there, done that. > > > > > > > > OK.. > > > > > > > > There are two paths for you. > > > > > > > > Eclipse Errors: Eclipse makes mountains of log entries so you need to > > isolate Flex issues from Eclipse Issues. Go through the eclipse logs > > looking for errant components and Null Pointer Exceptions. Although > the > > openness of eclipse encourages the addition of all kinds of great and > > not so great components (Java, Maven, Data Tools, JDT), I believe > > strongly that the Flex development environment should be sandboxed and > > kept single purpose. Yes, I have two eclipse installs. > > > > > > > > Flex: Flex issues like this, we have found to be resultant to the > > operation of Flex and the operation of SCM and SDK upgrades. I see you > > are using 3.0.2 which tells me your recently updated to the 3.2 SDK. I > > am convinced that Flex cannot handle an SDK upgrade well. Let me > > explain. We have a very large project that started during SDK 3.0 with > > the project files being checked into Subversion as 3.0 files. Now > there > > are lots of argument regarding checking in project files as in most > > cases they can become platform and developer specific, after going to > > the 3.1 SDK we lost the ability to use the compiler options tab in the > > project properties window with Flex complaining about the SDK string > > value. After a few minutes the IDE becomes unstable and crashes. No > > matter what we did, we could not recover (copy files around between > > developers, manually fixup the SDK and locale strings). If you checked > > out your project again, you have project files built for a different > > SDK. > > > > > > > > In over for us to overcome this, here is what we do. > > > > > > > > 1. BACKUP EVERYTHING > > > > 2. Turn off automatic build > > > > 3. Find all instances of files with the .cache extension within > > the Flex plug-in directories THAT START WITH YOUR PROJECT NAME (for > > example myproject.cache) and remove them. They automatically come back > > when the compiler runs. > > > > 4. Use FlexBuilder to create a new Empty Workspace. Leave the old > > one alone if we need to get back to it. WE DO NOT MAKE ANY CHANGES TO > > THE OLD WORKSPACE > > > > 5. In FlexBuilder, create new copies of the project(s) in the new > > workspace USING THE EXACT NAMES OF THE PRESENT PROJECTS. Leaving these > > projects empty, in their initial state. This will create new project > > files with the correct SDK string, locale, etc etc. > > > > 6. Backup these new projects from the new workspace and put them > > aside. > > > > 7. If using SCM, checkout the project(s) into the new workspace OR > > if not using SCM, copy OLD project(s) into the new workspace > directory. > > THIS IS IMPORTANT AS YOU CANNOT RELIABLY MOVE A FOLDER UNDER SCM AND > > HAVE IT WORK. IT SHOULD BE CHECKED OUT AGAIN. > > > > 8. From your new workspace, recently checked out or copied, remove > > the following files ".project .actionSciptProperties .flexProperties > > /.settings/org.eclipse.core.resources.prefs" > > > > 9. Copy the empty versions of these files (that were put aside) > > into the new workspace. > > > > 10. Start FlexBuilder and on each project's properties, enter the > > Library Build Path, on the classes tab and uncheck /src and save/close > > that form. THEN go back in and check that checkbox, close (this forces > > Flexbuilder to walk the filesystem and update its catalog of local > > classes) and save that form. You are basically faking an import > > > > 11. Back in Library Build Path, the project may need any swc's or > > referenced projects that were in the old project configuration. > > > > 12. Turn back on automatic build. > > > > > > > > KFB > > > > > > > > From: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> > [mailto:flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> > ] On > > Behalf Of Dmitri Girski > > Sent: Saturday, January 17, 2009 6:38 AM > > To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> > > Subject: [flexcoders] Flex Builder 3 crashes (Vista) > > > > > > > > Hi everybody, > > > > After some absolutely painless 6 months run, my Flex Builder 3 (3.0.2) > > > started to crash every 10-15 minutes under Vista (I know, I know, this > > > is beyond my control, I have to live with this). > > > > The only one thing which actually changed is Flash CS4 - all > > components have been recompiled using Flash CS4 for FP9. There is some > > > difference as these components now visible all the time in the Design > > View. SWCs compiled with Flash CS3 were very freaky in Design View. > > > > Here is the Java Screen Of Death: > > http://mitek.id.au/flex/builder_crash.jpg > > > > A couple of questions: > > 1. Why Xmx & Xms parameters are repeated twice (see the screenshot)? > > > > 2. Why Flex Builder simply ignores C:\Program Files\Adobe\Flex Builder > > > 3\FlexBuilder.ini file? I can place any values and parameters there > > and it just ignores them. > > > > 3. Why does it happen and who is responsible? (this question is > > rhetorical) > > > > If anyone had this problem before please share your experience. > > > > Thanks in advance. > > > > Cheers, > > Dmitri. > > >
