If you patch the *.as files you can compile with MTASC with the -mx flag unselected. and you can use the components without problems.
These files should work only for MTASC.I suggest you that make a copy of the original classes. F:\MMclassespatched\ for example. and point to it in the -cp param.
Best.
On 9/20/06, Michael Stuhr <[EMAIL PROTECTED]> wrote:
aaron smith schrieb:
> it shouldn't be any different.
>
> check out these remoting classes that make remoting in as 2 easier..
> less code...
>
> http://www.5etdemi.com/blog/archives/2006/03/cinqetdemiremoting-a-tiny-but-useful-remoting-library/
>
thanks for the link, i think i'll have a look, when i get a "hello world" trace. but since
then i try to find out what i am doing wrong, since i can't even get any connection.
ok. so here's what i have done to simplify my code :
<CODE>
import mx.rpc.*;
import mx.remoting.*;
import mx.remoting.debug.NetDebug;
class Main
{
// content holder
var Application:MovieClip;
// application initialization
static var application:Main;
static var parent:MovieClip;
/**
* Content creation
*/
function Main()
{
// some debugging tests
NetDebug.initialize(); // initialize NCD
NetDebug.trace("Hello world");
}
/**
* Application entry point
*/
static function main(scope:MovieClip)
{
parent = scope;
// create the content
application = new Main();
}
}
</CODE>
my fd-project settings:
<?xml version="1.0" encoding="utf-8"?>
<project>
<!-- Other classes to be compiled into your SWF -->
<classpaths>
<class path="classes" />
</classpaths>
<!-- Output SWF options -->
<output>
<movie input="" />
<movie path="test.swf" />
<movie fps="31" />
<movie width="300" />
<movie height="300" />
<movie version="8" />
<movie background="" />
</output>
<!-- Build options -->
<build>
<option verbose="False" />
<option strict="False" />
<option infer="False" />
<option useMain="True" />
<option useMX="True" />
<option warnUnusedImports="False" />
<option traceMode="FlashOut" />
<option traceFunction="" />
<option libraryPrefix="" />
<option excludeFile="" />
<option groupClasses="False" />
<option frame="1" />
<option keep="True" />
</build>
<!-- Class files to compile (other referenced classes will automatically be included) -->
<compileTargets>
<compile path="classes\Main.as" />
</compileTargets>
<!-- Assets to embed into the output SWF -->
<library>
<!-- example: <asset path="..." id="..." update="..." glyphs="..." mode="..."
place="..." sharepoint="..." /> -->
</library>
<!-- Paths to exclude from the Project Explorer tree -->
<hiddenPaths>
<!-- example: <hidden path="..." /> -->
</hiddenPaths>
<!-- Executed before build -->
<preBuildCommand />
<!-- Executed after build -->
<postBuildCommand alwaysRun="False" />
<!-- Other project options -->
<options>
<option showHiddenPaths="True" />
<option testMovie="NewTab" />
</options>
</project>
so in my understanding it should give me an output to the NetDebugger.swf, right ?
but it does so only when i compile without the -mx flasg (<option useMX="False" />)
but i want to use a library swf with v2 components, so i'll have to use the -mx flag, right ?
what if i patch those files (like described here:
http://osflash.org/mx_v2_components_patch?s=mxpatch) can i use those files later, when i'm
developing in the Flash IDE, or would this be a one way ?
micha
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
--
l u c h y x
r i a e v o l u t i o n ®
[EMAIL PROTECTED]
http://www.riaevolution.com
Phone: +54 (11) 4931-7006
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
