External Interface using global javascript scope

[vulkanosaure]

Hello,

I was trying to call a function from OpenFL to the wrapping HTML.

I could do it, but it seems that the name i pass in ExternalInterface.call("") is the name of the function in the global javascript scope.

It doesn’t seem right, it can bring issues in case of multiple openFL integration. I was expected to see a lime function that would make the link between the function name that External.call is calling, and the actual javascript function that will be associated with it.

something like
lime.exposeFunction(“function name”, my_function);

where my_function is the implemented function

Cheers

[david_is_neato]

In my case, I set up something like your exposeFunction example in the page javascript and used a generic ‘SendExternalMessage’ ExternalInterface function to call those mapped functions

ExternalInterface.call("SendExternalMessage", 
  {
    fn: FUNCTION_NAME_STRING,
    params : { }
  });

[vulkanosaure]

Good idea ! that’s a lot better already, this way, only one variable polute the global scope which is not so bad

[singmajesty]

You can also use untyped __js__ or extern classes when building to HTML5

HTML5 -minify flag and anticache in Assets

Interesting, thanks for the sample. This sounds like its worth looking into. In the meantime, you could do something like the following: #if html5 untyped js ("alert ('foobarstring')"); #end …or #if html5 import js.Browser; #end … #if html5 Browser.alert ("Hello!"); #end …or stage.window.alert ("Hello!"); There’s a lot of ways to access and write JavaScript directly when you’re publishing to the HTML5 target EDIT: …and in this exact case, the Lime window.alert API …

HTML5 -minify flag and anticache in Assets

You can even do something like: package my.custom.code; @:native("MyCustomCode") extern class MyCode { public static function alert (message:String):Void; public static function otherMethod ():Void; } then import my.custom.code.MyCode; … MyCode.alert ("Hello"); turns into MyCode.alert ("Hello"); in the final output. The @:native meta is optional – use it if your package + class name is different than what the JavaScript object reference is. This is a type-safe way of us…

[vulkanosaure]

js or extern classes

thanks, but if i understand well,
that doesn’t adress my problem, that will make a direct relation between my compiled haxe code and the window global js scope, which is not really a good practice.