>>Just pick a version and stick with it. You don't have to upgrade >>Eclipse.
Right, except in a case like this memory problem, you did say when we were trying to troubleshoot my problems: >>1. Use a different (newer) version of Eclipse. >>2. Use a different JVM with Eclipse. Another part of the problem, is that its open sourced (security risk, unknown and unfamiliar vendors). Also its essentially two applications working together for a single user experience. Trying to explain that to the people doing the review and packaging was difficult to say the least, especially when I didn't really understand how it works - we eventually got it approved, but because of those two reasons, it took a lot longer than if it was just say, Photoshop CS4. Plain and simple, it would have made our lives a lot better if Adobe had developed 100% of the application themselved and packaged it as a single piece of software. Also understanding how the two apps work together makes it hard to troubleshoot problems. OK, I don't know why I'm still defending myself and talking about it. :) It was a royal pain, and despite your points, I still wish Adobe had taken a different strategy. Perhaps if I worked for a very small company, I would feel differently. Jason Merrill Bank of America Global Learning Shared Services Solutions Development Monthly meetings on the Adobe Flash platform for rich media experiences - join the Bank of America Flash Platform Community _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
