I know I'm just getting started with Flash and open-source Flash, but I have experience working with a team on some large Java projects. I don't think Flashout is currently in good condition for teams to work on Flash based projects. There's too much setup cost involved. If I could specify paths to swfs and the .as files that contain the main method as being relative to my project, rather than as absolute file system paths, then that would really help. Then all developers could use the same .flashout file. Of course, this would mean that the prefs for the .flashout file would actually need to be stored in the flashout file, rather than having all the prefs for all the flashoutfiles in a workspace being stored in one file that's next to impossible to share with people.
Also, as far as I can tell there is only one person developing Flashout and he doesn't seem to be overly responsive to email.
So, yeah. Those are my initial thoughts after having used Flashout for a week or so. I'm sure it will get better over time, or someone will start working on an OSS Flashout replacement.
Thanks for everyone's help. Feel free to comment on my Flashout rant.
On 8/16/05, The Chris Method <[EMAIL PROTECTED]
> wrote:
-I'm using 0.2.1.6 now. I've been copying Flashout.as to my workspace instead. My reasoning behind this is as follows: If other developers are going to work on this project, I want to make setting up a Flash environment in their Eclipse as easy as possible. Checking out a project from our source control system is and having the necessary classes already in the project (Flashout.as is in a util folder, and other classes that need it just import util.Flashout) is one less step than having to get the Flashout.as file and copying it to the Flash Classes folder. Does that seem odd? Which Flash Classes folder do you put it in?
-I get this, but I'm not really trying to use the ASDT logger:
Error 2005-08-16 07:40:56.487 Error while stopping "org.asdt.logger_0.0.8.build2".
org.osgi.framework.BundleException: Exception in org.asdt.logger.ASLoggerPlugin.stop() of bundle org.asdt.logger.
On 8/16/05, Olivier <[EMAIL PROTECTED] > wrote:A couple of thoughts based on my experience and previous answers.
-You need FO 0.2.1.6 if you're using asdt 0.0.8 . Don't forget to copy
the Flashout.as to the Flash Classes folder.
-Check your Eclipse logs to see if everything got loaded properly.
-You don't need to import the FO in any class to make it work.
-If you use the -keep switch, then simply add one Flashout.info ()
statement in your code, compile it and the class will from now on be
included in the swf. You can then replace Flashout.info() with the
generic TRACE method and it will always work.
-The argument to add to the trace panel in FO is Flashout.traceReplacer
I hope some of this will be useful...
Olivier
_______________________________________________
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
