Comments on: JSFLInterface

By: AS3 JSFL Lib complete « xJSFL

AS3 JSFL Lib complete « xJSFL — Sun, 22 May 2011 23:59:50 +0000

[...] Serialize and deserialize native AS3 / JavaScript objects using the library from Exanimo [...]

By: Dave Stewart

Dave Stewart — Mon, 13 Sep 2010 08:45:41 +0000

Hi Matthew,

I'm developing a rather comprehensive JSFL library at the moment, and as you said, your class has come in rather handy! I've made a few alterations to allow it to function as a library rather than the executing class, as well as a few other functional tweaks.

Maybe you'd like to email me directly to discuss what sort off attribution you'd like, and (also as you said above) if you'd like to include any of the changes in your original code.

Cheers,
Dave

By: David

David — Wed, 22 Apr 2009 15:02:38 +0000

Ahh, didn't think about calling eval, which I think is cleaner than running MMExecute directly. While it may complicate it a little I like the idea of the interface handling properties and methods. But I certainly see your point too. You're call. Either way it's helped me immensely and I appreciate what you've done here.

By: matthew

matthew — Wed, 22 Apr 2009 14:00:23 +0000

@David The Flash JS environment defines a real eval function, so you can run any arbitrary JavaScript, and JSFLInterface will return the result. In your case, try something like JSFLInterface.call("eval", "fl.configURI"). Do you think there's a need to add a "getProperty"-type method? IMO, there's no need to complicate the interface, and if you're looking for something shorter, you can always do MMExecute("fl.configURI"). Let me know if you disagree.

@George This same technique can be used to create variables. However, it seems to me that when you're doing that, it's usually a better idea to externalize the script.

As for the History Panel, I don't know if it's possible to manipulate that or not. If you find something on the subject, please let me know and I'll update the class.

By: David

David — Tue, 21 Apr 2009 05:41:58 +0000

Really nice! Works like a charm.

One thing I would add is the ability to get properties. Like fl.configURI and so on. You've already done the hard work and this would make it a more complete JSFL interface. Regardless, thanks for sharing. This is a huge time saver!

By: George Profenza

George Profenza — Sat, 11 Apr 2009 19:55:02 +0000

Hi,

I gave jsflInterface a try. Calling functions is no problem. Does the same apply when you create variables ? Also, when I call a jsfl method from a WindowSWF, nothing gets recorded in the History Panel, so no UNDO :(

Any way to get around that ?

By: matthew

matthew — Wed, 18 Feb 2009 04:59:09 +0000

Seems like we're doing some similar work (: But what happens if you want to execute one of the built-in methods, like fl.fileExists in the example above?

By: Aaron Smith

Aaron Smith — Fri, 13 Feb 2009 21:51:56 +0000

Nice work man. I've got a similar interface here: http://codeendeavor.com/gsdocs/net/guttershark/util/JSFLProxy.html