Hi Christoph,

the default command is xml2swf if you specify an xml source and a swf destination. But you surely want to use the simple command. You thus have to specify this with the command or cmd attribute. <swfmill src="${swfmill.dir}/application.xml" dest="${build.dir}/application.swf" cmd="simple"/>
This should do the trick and everything works fine. ;)

You can specify multiple classpath nodes and nest them as you please.

Greetings,
Simon
--
Simon Wacker
www.simonwacker.com
www.as2lib.org
www.hq-heilbronn.de
www.flik-flak.de

----- Original Message ----- From: "christoph atteneder [celumSOLUTIONS]" <[EMAIL PROTECTED]>
To: "Open Source Flash Mailing List" <[email protected]>
Sent: Wednesday, June 29, 2005 1:16 PM
Subject: AW: [[W3-SPAM]] - Re: [osflash] Using as2lib SWF Ant Tasks withEclipse? - E-Mail-Adresse wurde in Betreff-Zeile gefunden.


Hi,

I tried to build Aral´s application.xml with simons swfmill ant task, but got following error in eclipse console:

[swfmill] swfmill 0.2.7
 [swfmill] Reading from [PATH]\application.xml
 [swfmill] doesn't seem to be a swfml file
 [swfmill] Writing SWF to [PATH]\application.swf
 [swfmill] no SWF loaded to save

ant script:
<target name="build application swf" description="builds application swf">
<swfmill src="${swfmill.dir}/application.xml" dest="${build.dir}/application.swf" />
</target>

application.xml:

<?xml version="1.0" encoding="iso-8859-1"?>
<!--
////////////////////////////////////////////////////////////////////////////////
//
// Natural Entry Point Method Sample Application
// for Swfmill + MTASC
//
// Application SWFML-S file.
//
// Author: Aral Balkan
//
// Copyright:
// Copyright © 2004, 2005 Aral Balkan. All Rights Reserved.
// Copyright © 2004, 2005 Ariaware Limited.
// http://ariaware.com
//
// Flash Platform and RIA blog:
// http://flashant.org
//
// OSFlash - Open Source Flash:
// http://osflash.org
//
// Released under the open-source MIT license.
//
////////////////////////////////////////////////////////////////////////////////

-->
<movie width="320" height="240" framerate="30">
<background color="#ffffff"/>

<!-- The Application and Particle classes have been
   compiled into the classes.swf file, which we
   import as an asset. This makes the classes
   available for linking to our movie clips.
-->
<clip import="classes.swf" />

<frame>

<!-- The Library contains the Application form, linked
   to the Application class and the EclipseLogo
   sprite, linked to the Particle class.
-->
<library>
<clip id="Application" class="Application" />
<clip id="EclipseLogo" class="Particle" import="lib/eclipse32.png" />
</library>

<!-- Place an instance of the Application form on Stage
   to instantiate it and provide the Natural Entry Point.
-->
     <place id="Application" name="app" x="0" y="0" depth="1000" />

</frame>

</movie>

Any ideas what I´ve done wrong?

BTW:
Does someone know, how to add multiple classpaths in mtasc ant task? Mulitple classpath parameters can´t be set and following structure is also just for one src directory, isn´t it?

<mtasc classpath="${src.dir}" split="yes">
 <srcset dir="${src.dir}">
   <include name="**/*Queue.as"/>
   <include name="**/*Map.as"/>
 </srcset>
</mtasc>

thx

Christoph

-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Sascha Balkau
Gesendet: Mittwoch, 29. Juni 2005 12:10
An: Open Source Flash Mailing List
Betreff: [[W3-SPAM]] - Re: [osflash] Using as2lib SWF Ant Tasks with Eclipse? - E-Mail-Adresse wurde in Betreff-Zeile gefunden.

Verbose option didn't brought anything to light. Thanks alot anyway for the help!
-sascha


----- Original Message ----- From: "Mike Shaw" <[EMAIL PROTECTED]>
To: "'Open Source Flash Mailing List'" <[email protected]>
Sent: Wednesday, June 29, 2005 3:57 PM
Subject: RE: [osflash] Using as2lib SWF Ant Tasks with Eclipse?


Sascha,

Try adding verbose="true" to the swf tag see if that outputs anything
else.

I'm running out of ideas, you could hack the task java file to remove the
exception handling and see what the actual complaint is.

Sorry,

Mike.



_______________________________________________
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


_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to