> This experience has made me really dislike the fact that Adobe essentially > built an Eclipse Plug-in instead of a single app, but I also understand why > they did it
No, this is actually a Good Thing(tm). Eclipse is a mature environment with lots of people improving it regularly. And because of its plugin architecture, you can use it for all sorts of things. For example, my Eclipse install includes FlexBuilder, J2EE toolchain, CFEclipse, Oxygen, Aptana, etc. And there are lots of third-party tools to help manage Eclipse and plugin updates. > > If you're using the Flex Builder integrated install > > What does that mean? How would I know? Thanks. You can either install Flex Builder with Eclipse, or into an existing Eclipse install. The version of Eclipse that comes with Flex Builder is not the latest version - if I recall correctly, it's 3.2. To find out which you have, the integrated Flex Builder/Eclipse is installed in c:\program files\adobe, while if you installed Eclipse separately, it'd be wherever you put it - typically, c:\eclipse. Also, you get different splash screens. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
