[osflash] Using components in FAME development

[Carlos Rovira]

Hi Justin,

I run into the same problem with "-out" and other options. Simon show
me the link with the lastest release:

http://sourceforge.net/project/showfiles.php?group_id=94206&package_id=164902



2005/11/2, Justin Clarke <justin.clarke at dcinteract.com>:
> Thanks Carlos. I didn't notice that the new version of ASDT actually incorporates a SWFViewer - nice.
>
> I tried using the build.xml script with Simon Wacker's AS2ant but there is a problem - his mtasc.java does not support the -out argument, and what I want to do is compile using a source swf (created by the MM IDE), and deploy a MTASC-modified swf to my build directory. Something like:
>
> <target name="compile" description="builds swf">
>        <mtasc srcdir="${src.dir}" classpath="${src.dir}" swf="${src.dir}/${ant.project.name}.swf"
>                   main="true" out="${build.dir}/${ant.project.name}.swf"/>
> </target>
>
> The reason I want to do this is as mentioned earlier - as soon as I add an MM component to a swf and start recompiling using MTASC it goes haywire after the first compile. I don't know why this happens hence the reliance on using -out to create a new swf every time.
>
> Has anyone run into problems using MM components and recompiling using MTASC - or am I doing something wrong?
>
> thanks for any pointers,
> justin.
>
> -----------------------
> Carlos Rovira wrote:
>
> Nowadays,I recommend you to avoid using Flashout and use instead ASDT
> SWFViewer and AS Logger. To automatize the compilation process I
> recommend you to use an ANT script, in order to separate the build
> process from the Eclipse IDE.
>
> See this article as a possible guide:
>
> http://osflash.org/asdt/logging?s=logger
>
> Hope that helps.
> -------------------------
>
>
>
> _______________________________________________
> osflash mailing list
> osflash at osflash.org
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>


--
::| Carlos Rovira
::| http://www.carlosrovira.com