I'm using both. I use Flashout to test my code locally, and when I have to deploy to my local server to test the java another dev is working on, I use Ant to build the SWF into the war, and it deploys it to Tomcat.
Apparently, MTASC does shoot out errors the Console window because as my Ant task runs, I can see it spitting out the typical import not used stuff. I don't know how to get the problems to be clickable, but if you launch the SWF, it'll open in the Flash Player, not in Eclipse, though. ----- Original Message ----- From: "Collin Peters" <[EMAIL PROTECTED]> To: "Open Source Flash Mailing List" <[email protected]> Sent: Friday, August 12, 2005 12:14 PM Subject: [osflash] Compiling: Ant vs ASDT/Flashout Are most people here using ASDT/Flashout or ANT to compile? I didn't find the compile options with ASDT/Flashout to really work well with a larger, module-based project. But I *really* would like to A) have errors show up in the problems window (and be able to double-click them) and B) launch a SWF inside Eclipse (and also launch a logger such as the LuminicBox logger) I don't see a way do to either of these things with Ant Collin _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
